Cisco Cisco 2000 Series Wireless LAN Controller
19
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.150.10
OL-10607-02
Caveats
WCP is the protocol running between the Cisco Catalyst 6500 Series Switch Supervisor and the
WiSM. The supervisor uses WCP to monitor the health of the WiSM. If you enter the show wism
status command or see a WiSM down trap on WCS, make sure that the WiSM service port and the
supervisor are configured correctly. WCP can fail because of an incorrect configuration.
WiSM. The supervisor uses WCP to monitor the health of the WiSM. If you enter the show wism
status command or see a WiSM down trap on WCS, make sure that the WiSM service port and the
supervisor are configured correctly. WCP can fail because of an incorrect configuration.
•
CSCsb46260—A client connected to one of the controllers in a mobility group is shown as a rogue
on the other controllers, but the access point is not shown in the rogue access point list. If a client is
listed on the rogue client list, then the access point to which it is connected should be reported as a
rogue access point.
on the other controllers, but the access point is not shown in the rogue access point list. If a client is
listed on the rogue client list, then the access point to which it is connected should be reported as a
rogue access point.
•
CSCsb53746—A 350 or CB20A client running ACU 6.5 or 6.4 and configured for LEAP
authentication with WPA encryption can authenticate to a lightweight access point but does not
receive an IP address. This problem does not affect clients running ACU 6.3, which does not use
WMM data frames. To check for this problem, enter the following command on the controller:
authentication with WPA encryption can authenticate to a lightweight access point but does not
receive an IP address. This problem does not affect clients running ACU 6.3, which does not use
WMM data frames. To check for this problem, enter the following command on the controller:
debug dot1x events enable
In the body of the trace that follows authentication by an affected client, the following messages
appear:
appear:
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
xx:xx:xx:xx:xx:xx
•
CSCsb90622—AP impersonation alarms sometimes flood WCS.
•
CSCsb91943—The web authentication login window does not appear when external web
authentication has been configured on a 2000 series controller. This problem occurs because the
controller forwards all http and https traffic to the CPU prior to authentication, thereby breaking the
external web authentication mechanism.
authentication has been configured on a 2000 series controller. This problem occurs because the
controller forwards all http and https traffic to the CPU prior to authentication, thereby breaking the
external web authentication mechanism.
•
CSCsc12310—Aggressive load balancing is not performed for clients that do not send ACE
information elements (IEs) if fast roaming is enabled.
information elements (IEs) if fast roaming is enabled.
•
CSCsc17827—For Cisco Aironet 1500 Series Lightweight Outdoor Access Points and Cisco
Aironet 1030 Remote Edge Lightweight Access Points, channel 165 for the 802.11a radio is only
available for the -A SKU when the country code is set to USX. Channel 165 is not available for the
-N SKU for any of the countries that use this SKU.
Aironet 1030 Remote Edge Lightweight Access Points, channel 165 for the 802.11a radio is only
available for the -A SKU when the country code is set to USX. Channel 165 is not available for the
-N SKU for any of the countries that use this SKU.
•
CSCsc36050—A client associates to a controller running 802.1x + WEP on the first attempt.
However, the client fails a second association attempt to this controller because the controller does
not send an EAP request to the client. After removing the client information, the client is once again
able to associate.
However, the client fails a second association attempt to this controller because the controller does
not send an EAP request to the client. After removing the client information, the client is once again
able to associate.
•
CSCsc68105—Web authentication DNS queries are sent over the management interface instead of
the dynamic interface to which the WLAN is assigned.
the dynamic interface to which the WLAN is assigned.
•
CSCsc74740—A client fails to join a web-authentication WLAN with an anchor controller after a
reboot.
reboot.
•
CSCsc76306—Access points running in REAP mode restart when their associated clients become
disassociated.
disassociated.
•
CSCsc80266—The controller may crash due to a problem with the radio resource management
(RRM) logging function.
(RRM) logging function.
•
CSCsc84681—SNMP version 1 and version 2 may stop responding.
•
CSCsc84971—The access point sends two DHCP discover messages on bootup instead of a DHCP
request.
request.