Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller

Several messages might flood the message logs when the controller boots up. These messages appear 
because of a failure to read or delete several different configuration files. These are low-severity 
messages that can safely be ignored. They do not affect controller functionality. These are some 
examples:

Mar 18 16:05:56.753 osapi_file.c:274 OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : 

sshpmInitParms.cfg. file removal failed.

-Process: Name:fp_main_task, Id:11ca7618

Mar 18 16:05:56.753 osapi_file.c:274 OSAPI-5-FILE_DEL_FAILED: Failed to delete the file : 

bcastInitParms.cfg. file removal failed.

-Process: Name:fp_main_task, Id:11ca7618

The controller supports web authentication redirects only to HTTP (HTTP over TCP) servers. It does not 
support web authentication redirects to HTTPS (HTTP over SSL) servers.

For 5500 series controllers, 2100 series controllers, and controller network modules, you must configure 
a preauthentication access control list (ACL) on the WLAN for the external web server and then choose 
this ACL as the WLAN preauthentication ACL under Security Policies > Web Policy on the WLANs > 
Edit page.

Cisco 1250 series access points are not supported for use with the Cisco 7920 IP phone. They can, 
however, be used with the Cisco 7921 and 7925 IP phones.

The 1250 series access points may contain a bootloader older than version 12.4(10b)JA. Units with old 
bootloaders do not generate a crash log when a crash occurs. The crash log is disabled so that a crash 
does not corrupt the flash file system. Units with bootloader versions 12.4(10b)JA or later generate a 
crash log if the access point is associated to a controller running software release 4.2.112.0 or later. 

New 1250 series access points shipped from the factory contain new bootloader images, which fixes the 
flash file system after it is corrupted during a crash (without losing files). This new bootloader 
automatically sets a new CRASH_LOG environment variable to "yes," which enables a crash log to be 
generated following a crash but only on controllers running software release 4.2.112.0 or later. 
Therefore, no user configuration is needed to enable a crash log on new 1250 series access points shipped 
from the factory.

These examples show the output from the CLI commands (in bold) that you use to check the bootloader 
version on lightweight and autonomous 1250 series access points: 

Commands entered on the controller CLI:

debug ap enable AP001b.d513.1754

debug ap command "show version | include BOOTLDR" AP001b.d513.1754

Thu Apr 23 09:31:38 2009: AP001b.d513.1754: BOOTLDR: C1250 Boot Loader