Cisco Cisco 2000 Series Wireless LAN Controller
19
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.0.179.11
OL-11734-01
Caveats
•
CSCse08725—A Vocera badge running MS-PEAP fails when trying to associate to an AP1010. This
problem occurs because the controller is dropping the packets.
problem occurs because the controller is dropping the packets.
Workaround: None at this time.
•
CSCse10109—For WMM clients without TSPEC support, ACM must be disabled for proper QoS
mapping.
mapping.
Workaround: Disable ACM for WMM clients without TSPEC support.
•
CSCse14889—The controller does not generate traps for ad-hoc rogues.
Workaround: None at this time.
•
CSCse15932—The 4404 controller may reboot if the TimerTickTask software fails.
Workaround: None at this time.
•
CSCse17260—WPA clients may receive an error message indicating that the WEP key may be
configured incorrectly on the client.
configured incorrectly on the client.
Workaround: None at this time.
•
CSCse18855—RADIUS accounting cannot be disabled on an individual WLAN. Once a RADIUS
accounting server is defined globally, WLANs fall back to the global RADIUS accounting server if
no RADIUS accounting server is selected in the WLANs.
accounting server is defined globally, WLANs fall back to the global RADIUS accounting server if
no RADIUS accounting server is selected in the WLANs.
Workaround: Create a fictitious RADIUS accounting server and assign it to the WLAN for which
RADIUS accounting is not required.
RADIUS accounting is not required.
•
CSCse28941—Cisco 1510 series mesh access points (MAPs) can become isolated when deployed
in the ETSI (European Telecommunications Standards Institute) domain if the Dynamic Frequency
Spectrum (DFS) feature detects what appear to be radar signals, even if no actual radar is present.
Because the access point automatically stops using channels on which it detects radar, a MAP can
quickly run out of usuable channels and be unable to communicate with its rooftop access point
(RAP). A MAP with no usable channels becomes isolated and even the lonely recovery mechanism
cannot bring it back. You cannot reach or signal a MAP in this state from the controller (WLC) or
from a RAP. MAPs in the US domain are not affected by this defect because radar detection is not
used for the 5.8-GHz band.
in the ETSI (European Telecommunications Standards Institute) domain if the Dynamic Frequency
Spectrum (DFS) feature detects what appear to be radar signals, even if no actual radar is present.
Because the access point automatically stops using channels on which it detects radar, a MAP can
quickly run out of usuable channels and be unable to communicate with its rooftop access point
(RAP). A MAP with no usable channels becomes isolated and even the lonely recovery mechanism
cannot bring it back. You cannot reach or signal a MAP in this state from the controller (WLC) or
from a RAP. MAPs in the US domain are not affected by this defect because radar detection is not
used for the 5.8-GHz band.
Workaround: None at this time.
•
CSCse29193—The controller marks a RADIUS server as dead if a single request is not responded
to after five retries and switches to a backup server.
to after five retries and switches to a backup server.
Workaround: None at this time.
•
CSCse31271—The 4.9-GHz band cannot be changed on the -P regulatory domain if public-safety
is disabled.
is disabled.
Workaround: To change the 4.9-GHz band on the -P regulatory domain, enter this command using
the controller CLI: config ap public-safety enable Cisco_AP.
the controller CLI: config ap public-safety enable Cisco_AP.
•
CSCse34673—If you globally disable and then globally enable management frame protection
(MFP) on a controller that is part of a mobility group and connected to LWAPP-enabled access
points, the access points that are connected to the other controllers within the mobility group may
report sequence number MFP anomalies.
(MFP) on a controller that is part of a mobility group and connected to LWAPP-enabled access
points, the access points that are connected to the other controllers within the mobility group may
report sequence number MFP anomalies.
Workaround: None at this time.
•
CSCse36426—Controllers with AP-group VLANs configured sometimes cause WCS to hang when
the controllers are added to WCS.
the controllers are added to WCS.
Workaround: Remove access point group VLANs before you add the controller.