Примечания к выпуску для Cisco Cisco 4404 Wireless LAN Controller
20
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.0.179.8
OL-11101-01
Caveats
•
CSCse08879—External web authentication fails to operate after upgrading the controller software
from 2.2.127.9 to 3.1 or 3.2.
from 2.2.127.9 to 3.1 or 3.2.
Workaround: Follow these guidelines:
–
For 4xxx controllers, add the external web server to the list of external server IP addresses using
this command: config custom-web ext-webserver add server-ip-address. Then remove the
preauthentication ACL configuration for the web authentication WLAN.
this command: config custom-web ext-webserver add server-ip-address. Then remove the
preauthentication ACL configuration for the web authentication WLAN.
–
For 2006 controllers, make sure that the preauthentication ACL is configured properly.
•
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.
•
CSCse10283—An error message may appear on the controller GUI when you try to assign a
4.9-GHz channel to an access point.
4.9-GHz channel to an access point.
Workaround: Before you can assign a 4.9-GHz channel to an access point from the controller GUI,
you must enable the 4.9-GHz backhaul feature. To do so, enter this command using the controller
CLI: config ap public-safety enable Cisco_AP.
you must enable the 4.9-GHz backhaul feature. To do so, enter this command using the controller
CLI: config ap public-safety enable Cisco_AP.
•
CSCse14889—The controller does not generate traps for ad-hoc rogues.
Workaround: None at this time.
•
CSCse15326—Inconsistent file sizes may occur during configuration backups.
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.
•
CSCse26358—The controller reboots if you enable local switching on any WLAN from 9 through
16.
16.
Workaround: Enable local switching on a WLAN other than 9 through 16.
•
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.
•
CSCse31241—The backhaul transmit power level cannot be changed for a mesh access point.
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.