Cisco Cisco 2000 Series Wireless LAN Controller Release Notes

CSCsb30211—Cisco lightweight access points continue rebooting when WMM mode is enabled. 
Cisco lightweight access points may not be able to join the Wireless LAN Controller if WMM is 
enabled on any of the WLANs.
Workaround: Make sure that the port to which the Cisco lightweight access point is connected is 
configured as trunk port and not an access port if any WLAN has WMM enabled.

CSCsb34149—Disabling or deleting a WLAN on which a large number of clients exist may not 
result in deletion of all of the clients. This occurs when a large number (several thousand) clients 
are using a WLAN when the WLAN is disabled or deleted.
Workaround: Make sure that WLANs are not deleted or disabled with a large number of clients 
associated.

CSCsb37605—When the admin status of Cisco Aironet 1000 series lightweight access point radio 
A is disabled, toggling the 802.11a network status flag re-enables radio A, although the admin status 
of radio A is still in disabled state. 
Workaround: Disabling radio A and reapply.

CSCsb42133—When editing a WLAN, on entering an invalid value for session timeout, an incorrect 
range is shown to the operator in the error message. 
This bug appears when the operator selects the edit option for a WLAN on the Wireless LAN 
Controller UI and the WLAN is set for 802.1x security, and when the operator enters an invalid value 
for session timeout, the error message shown on clicking Apply incorrectly states that the correct 
range is 0 to 86400.
Workaround: The correct range for the WLAN session timeout is: 300-86400 for 802.1x and 
0-65535 for all other security types.

CSCsa47748—RLDP protocol is not supported in Cisco Aironet 1130 series lightweight access 
points, Cisco Aironet 1200 series lightweight access points, and Cisco Aironet 1240 series 
lightweight access points. 
Workaround: Use “Rogue Detector AP” to detect rogue access points.

CSCsb52557—Cisco lightweight access points do not connect to the Cisco 4400 Series Wireless 
LAN Controller if the time is not set first.
Workaround: Set the time on the Cisco 4400 Series Wireless LAN Controller before the Cisco 
lightweight access points connect.

CSCsb53746—A 350 or CB20A client running ACU 6.4 or ACU 6.5 and configured for LEAP 
authentication with WPAv1 encryption, can authenticate to a Cisco lightweight access point but does 
not receive an IP address. This problem does not affect clients running ACU 6.3, which does not use 
WME data frames.
To check for this problem enable the following debug on the Wireless LAN Controllers:

debug dot1x events enable

In the body of the trace which follows authentication by an affected client see the following:

Fri Jun 3 07:29:59 2005: Received EAPOL-Key from mobile xx:xx:xx:xx:xx:xx

Fri Jun 3 07:29:59 2005: Received EAPOL-key message with invalid version number from 
mobile xx:xx:xx:xx:xx:xx

Workaround: Configure WME policy to be allowed for the WLAN on the Wireless LAN Controller. 
To do this via the GUI, browse to the WLANs->Edit page for the WPAv1 WLAN in question and in 
the drop-down box next to WME policy, select Allowed or Required.
The allowed option means that both WME and non-WME clients can authenticate and receive an 
IP address, for example both Aironet ACU 6.4/6.5 and 6.3 clients. The required option means that 
only WME clients can authenticate; that is, only ACU 6.4/6.5 clients.