Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
57
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.1.151.0
OL-31336-01
Caveats
•
CSCsr32354—If a 1250 series access point is connected to the 6548 blade in a Cisco Catalyst switch
using a power injector or external power supply, the access point’s Ethernet port sometimes comes
up in the Down state.
using a power injector or external power supply, the access point’s Ethernet port sometimes comes
up in the Down state.
Workaround: None.
•
CSCsr39536—An error message appears if you make any changes on the AP Details page on the
controller GUI and do not re-enter the access point credentials.
controller GUI and do not re-enter the access point credentials.
Workaround: None. Re-enter the access point credentials.
•
CSCsr43364—The controller sometimes reboots after you click the WLANs tab on the controller
GUI.
GUI.
Workaround: None.
•
CSCsr46256—If an association request contains TSPEC and SFA information elements (IEs), the
access point sends an association response with only a TSPEC IE. The SFA IE is missing.
access point sends an association response with only a TSPEC IE. The SFA IE is missing.
Workaround: None.
•
CSCsr48006—A 1250 series access point might crash during Layer 2 roaming with 50 clients.
Workaround: None.
•
CSCsr49229—During very frequent upgrades between two controllers where the access points
repeatedly join a controller and download code and then join another controller and download
another version of code in a continuous cycle, the Cisco WiSM can lock up, making even the console
port inaccessible.
repeatedly join a controller and download code and then join another controller and download
another version of code in a continuous cycle, the Cisco WiSM can lock up, making even the console
port inaccessible.
Workaround: Power cycle the controller or reset the Cisco WiSM blade.
Resolved Caveats
These caveats are resolved in controller software release 5.1.151.0.
•
CSCsb85113—When you download the software image to the controller using the CLI, access
points are sometimes disconnected.
points are sometimes disconnected.
•
CSCsc33206—The current software for wireless controllers does not allow you to save debug
messages in the controller log or on a syslog server. This issue creates serviceability problems when
trying to enable debugs for a long period of time.
messages in the controller log or on a syslog server. This issue creates serviceability problems when
trying to enable debugs for a long period of time.
•
CSCsc36000—The show running-config CLI command includes all associated access point
details, which makes the output very lengthy. The access point information should be removed from
the output of this command.
details, which makes the output very lengthy. The access point information should be removed from
the output of this command.
•
CSCsd10643—The default EAP timeout value of 1 second is too aggressive for some clients. The
default value should be changed to 30 seconds.
default value should be changed to 30 seconds.
•
CSCsd29484—The access point log shows the reason for the last access point restart. However,
under certain conditions, the restart reason does not provide enough useful information. For
example, if an access point disconnects from a controller because the controller is running at a high
CPU speed, the access point sends an LWAPP discovery packet to the controller, and the controller
replies with an LWAPP discovery response. When the access point requests the MAC address of the
AP-manager, the controller drops the ARP packet from the access point. The AP log shows “Could
not resolve switch ARP in Join” as the restart reason.
under certain conditions, the restart reason does not provide enough useful information. For
example, if an access point disconnects from a controller because the controller is running at a high
CPU speed, the access point sends an LWAPP discovery packet to the controller, and the controller
replies with an LWAPP discovery response. When the access point requests the MAC address of the
AP-manager, the controller drops the ARP packet from the access point. The AP log shows “Could
not resolve switch ARP in Join” as the restart reason.