Cisco Cisco 2000 Series Wireless LAN Controller Release Notes

Page of 40
 
33
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.0.206.0
OL-11824-01
  Caveats
CSCsh61347—In some regulatory domains outside the US and Canada, MESH access points fail to 
join a controller after they are upgraded from software version 4.0.179.11 to 4.0.206.
Workaround: None.
CSCsh64994—RADIUS account records are not generated when an access point is configured in 
H-REAP mode with a locally switched SSID.
Workaround: None.
CSCsh67106—AAA interface override results in ACLs are sometimes not installed.
Workaround: None.
CSCsh68089—Access points connected directly to a port on 2000 or 4400 series controllers 
sometimes fail to receive an IP address through DHCP.
Workaround: Create and enable a DHCP scope on the controller’s internal DHCP server. The scope, 
even a placeholder or non-functioning scope, is enough to disable the CHADDR filter and allow an 
access point to receive an IP address.
CSCsh69985—When a Cisco 7920 phone is associated to a lightweight access point the controller 
sometimes fails to forward packets to the phone.
Workaround: None.
Resolved Caveats
These caveats are resolved in controller software release 4.0.206.0.
CSCsb87264—If WLAN ID 1 is not configured on the controller, a REAP access point broadcasts 
the “Airespace” SSID after entering standalone mode. Clients can access this unsecured SSID and 
use the REAP access point to access the network.
CSCsc05495—Controllers intermittently send a state attribute 24 in an access-request packet.
CSCsc14045—When you choose the VPN Passthrough Layer 3 security option on the WLANs > 
Edit page, you should not be able to enable the Web Policy feature on the same page.
CSCsc44326—A 4400 series controller may fail to respond to ARP requests for the ap-manager2 
interface’s IP address when the ARP request is addressed at the MAC layer to the unicast MAC 
address of the interface rather than to the broadcast MAC address. As a result, there may be sporadic 
interruptions in connectivity at ARP refresh time, resulting in the periodic loss of associations for 
access points associated through the ap-manager2 interface.
CSCsd27529—Static WEP does not operate properly for a REAP access point in standalone mode.
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.
CSCsd85126—The access point may reboot unexpectedly after upgrading to software release 
3.2.116.21.
CSCsd87382—Bridging functionality for REAP devices is not available on OEM builds of 
controller software.
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.
CSCse11202—WPA clients may receive an error message indicating that the WEP key may be 
configured incorrectly on the client.