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

Скачать
Страница из 24
 
19
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.0.179.8
OL-11101-01
  Caveats
CSCsd54171—After the controller configuration is modified, the changes may not take effect or 
function properly. 
Workaround: Reset the controller to factory defaults and then reconfigure the controller exactly the 
same way.
CSCsd54750—The Cisco WiSM may display numerous timeout messages.
Workaround: None at this time.
CSCsd59421—A wireless client fails to authenticate using 802.1X when the access point is on a 
different VLAN from the controller. 
Workaround: Configure the access point for the same VLAN as the controller.
CSCsd69158—After a RADIUS session timeout expires, the access point does not send a unicast 
key to the client. 
Workaround: None at this time.
CSCsd82363—Channel utilization is incorrectly reported in radio utilization reports on the 
controller and in WCS. Channel utilization may appear as zero when there is active client traffic or 
as an aggregate of client transmit and receive traffic. 
Workaround: None at this time.
CSCsd85126—The access point may reboot unexpectedly after upgrading to software release 
3.2.116.21. 
Workaround: None at this time.
CSCsd87382—Bridging functionality for REAP devices is not available on OEM builds of 
controller software.
Workaround: None at this time.
CSCsd89139—Pocket PC devices may fail PEAP authentication through a 4400 series controller 
after resuming from standby.
Workaround: None at this time.
CSCsd91042—An access point may reboot when no clients are associated to it. 
Workaround: None at this time.
CSCsd95992—When IGMPv3 is enabled on the controller, a significant amount of packet loss 
occurs. The packet loss is even greater when there is an active multicast stream.
Workaround: None at this time.
CSCsd96189—A CB21AG client adapter running on Windows XP SP2 experiences two ping 
timeouts when roaming from an AP1030 to an AP1242, when each is associated to a different 2006 
controller.
Workaround: None at this time.
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.
Workaround: None at this time.