Cisco Cisco 2000 Series Wireless LAN Controller
16
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.116.21
OL-9542-01
Caveats
Caveats
This section lists resolved and open caveats in operating system release 3.2.116.21 for Cisco controllers
and lightweight access points.
and lightweight access points.
Resolved Caveats
These caveats are resolved in operating system release 3.2.116.21.
•
CSCeh68636—If a power injector is inserted between an AP1131 or AP1242 and a Cisco Catalyst
switch and an AC power adapter is connected directly to the access point, the access point does not
use the power from the switch. After the access point boots up, it waits for CDP packets from the
switch. If the output power of the switch does not support the access point, the access point changes
both 802.11 radio interfaces to a reset state.
switch and an AC power adapter is connected directly to the access point, the access point does not
use the power from the switch. After the access point boots up, it waits for CDP packets from the
switch. If the output power of the switch does not support the access point, the access point changes
both 802.11 radio interfaces to a reset state.
•
CSCsb13548—Cisco lightweight access points frequently reset.
•
CSCsb63749—A client on an anchor controller cannot ping another client that has roamed to a foreign
2006 controller.
2006 controller.
•
CSCsb76419—The client state appears on two switches in a Layer 2 roaming environment
.
•
CSCsb78835—The controllers are not sending all rogue trap information to Cisco WCS.
•
CSCsb88424—Cisco Aironet 1030 Remote Edge Lightweight Access Points in REAP mode reboot
continuously.
continuously.
•
CSCsb97559—The candidate list returned by the controller in association/reassociation responses may
have an access point that the client cannot reach as the top-most entry.
have an access point that the client cannot reach as the top-most entry.
•
CSCsc06090—For some systems with a large number of access points and controllers, the rogue
access point scheduled task can take up to 35 or 45 minutes to complete.
access point scheduled task can take up to 35 or 45 minutes to complete.
•
CSCsc33769—The controller’s radio resource management (RRM) algorithms set the transmit
power to 6 on Cisco Aironet 1000 Series Lightweight Access Points.
power to 6 on Cisco Aironet 1000 Series Lightweight Access Points.
•
CSCsc37217—Over the temperature extremes of the product specification (and primarily at the hot
temperature extreme of 55 degrees Celsius), the Cisco Aironet 1500 Series Lightweight Outdoor
Access Point may not meet the IEEE 802.11a/b/g transmitter linearity parameter of error vector
magnitude (EVM) of the 54Mb and 48Mb product specification.
temperature extreme of 55 degrees Celsius), the Cisco Aironet 1500 Series Lightweight Outdoor
Access Point may not meet the IEEE 802.11a/b/g transmitter linearity parameter of error vector
magnitude (EVM) of the 54Mb and 48Mb product specification.
•
CSCsc42773—LWAPP-enabled 1130 and 1200 series access points may shut down their radio
interfaces because of insufficient power from power over Ethernet (PoE).
interfaces because of insufficient power from power over Ethernet (PoE).
•
CSCsc42923—A 32-character SSID does not allow access points to join the controller.
•
CSCsc43587—The controller crashes in the apfReceiveTask software.
•
CSCsc47951—The mmListen task may miss the software watchdog, causing the controller to reboot.
•
CSCsc49148—The 2006 controller may crash because of a stack corruption of the apfRogueTask. When
an SSID of 32 characters is advertised by the rogue access point, such a crash is likely.
an SSID of 32 characters is advertised by the rogue access point, such a crash is likely.
•
CSCsc51291—An EAP ID request is always sent to the client when the PMK/WEP+ cache expires, even
if the client is not associated to a WLAN that is configured for WEP+ or WPA2 security.
if the client is not associated to a WLAN that is configured for WEP+ or WPA2 security.
•
CSCsc59377—Access points fail to join a controller with sustained high CPU utilization (~97%).
During a user-initiated reboot, the access points fail to join the controller until the access point count
is reduced from 32 to 25. After the initial 25 join, the remaining access points can be added and will
join the controller.
During a user-initiated reboot, the access points fail to join the controller until the access point count
is reduced from 32 to 25. After the initial 25 join, the remaining access points can be added and will
join the controller.