Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
15
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.2.193.0
OL-31336-01
Important Notes for Controllers and Non-Mesh Access Points
Note
An access point with the LWAPP recovery image (an access point converted from autonomous mode or
an out-of-the-box access point) uses only LWAPP to try to join a controller before downloading the
CAPWAP image from the controller.
an out-of-the-box access point) uses only LWAPP to try to join a controller before downloading the
CAPWAP image from the controller.
Messages Appearing Upon Controller Bootup
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:
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
Web Authentication Redirects
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.
support web authentication redirects to HTTPS (HTTP over SSL) servers.
PLM Location Commands
The config, show, and debug location plm path loss measurement location commands are not supported
in controller software release 5.2.193.0, even though they appear in the CLI code.
in controller software release 5.2.193.0, even though they appear in the CLI code.
Cisco 1250 Series Access Points and Cisco 7920 IP Phones
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.
however, be used with the Cisco 7921 and 7925 IP phones.
Crash Files for 1250 Series Access Points
The 1250 series access points may contain either an old bootloader or a new bootloader. Those with an
old bootloader 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. Those with a new bootloader generate a crash log if the access
point is running controller software release 4.2.112.0 or later.
old bootloader 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. Those with a new bootloader generate a crash log if the access
point is running controller software release 4.2.112.0 or later.
New 1250 series access points shipped from the factory contain the new bootloader image, 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.
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.