Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller

Скачать
Страница из 66
 
56
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.2.193.0
OL-31336-01
  Caveats
CSCsz80820—When you enable AP join priority and access points are connected to a secondary 
controller when the primary is already full, the access points will not fall back automatically to the 
primary.
Workaround: Reboot the access points.
CSCsz80918—Controllers fail to filter CAPWAP debug messages by MAC address.
Workaround: None.
CSCsz82533—The username and password configured on an access point are lost when you 
upgrade from a 4.x controller release to a 5.x or 6.x controller release.
Workaround: None.
CSCsz82577—2100 series and 526 controllers sometimes deauthenticate a client device 
periodically and repeatedly.
Workaround: None.
CSCsz86043—When a mix of 1130 series access points and 1522 access points are connected to a 
controller, the controller sometimes incorrectly displays four radio interfaces on the 1130 access 
points.
Workaround: None.
CSCsz88122—4400 series controllers sometimes reboot and report the reason as “Reaper Reset at 
task sshpmM,” but recover without intervention.
Workaround: None.
CSCsz89135—Controllers sometimes fail to increase power after finding failed clients and 
prealarms.
Workaround: None.
CSCsz92558—Ethernet interface statistics from access points sometimes fail to appear on the 
controller GUI.
Workaround: Enter the show interface g0 command on the controller CLI to see access point 
Ethernet statistics. 
CSCsz94843—Multicast traffic sometimes fails across NPU on 4404 controllers.
Workaround: None.
CSCsz95406—When an 1140 access point is connected to a 3750E switch that is configured to 
provide inline power up to 20w, the controller that the access point joins sometimes reports that the 
access point is receiving low power, and WCS creates an alarm.
Workaround: None.
CSCsz95595—Some access point IOS commands (copy, for example) may be unavailable from the 
access point CLI when you use Telnet or SSH to connect to the access point.
Workarounds:
Connect a console cable to the access point. At the ap# prompt, enter one of the following 
hidden commands:
#debug lwapp console cli (4.2 [12.4(10b)J*] or earlier)
#debug capwap console cli (5.0 [12.4(13d)JA] or above)
On the controller WLC CLI, enter the following command:
debug ap enable APname