Cisco Cisco 2106 Wireless LAN Controller

CSCsh47269—In software releases 4.0.179 and earlier, broadcast and multicast forwarding were 
both controlled with a single global flag that enabled multicast. In software release 4.0.206, these 
functions were broken into separate configuration flags: one that controls broadcast and one that 
controls non-broadcast multicast. If you have multicast enabled in software releases 4.0.179 and 
earlier, the broadcast flag is left disabled after upgrading to software release 4.0.206. As a result, 
some applications that rely on broadcast do not work after the upgrade.

CSCsh47364—When access point debugging is enabled on a controller and you enter 
debug lwapp ? during a telnet or SSH session to the controller, the controller reboots.

CSCsh47906 and CSCsh50966—The controller sometimes fails to answer unicast ARP requests for 
the AP-manager interfaces. As a result, there might be sporadic interruptions in connectivity at ARP 
refresh time, resulting in the periodic loss of associations for access points associated through AP 
managers other than the first (ap-manager). This scenario is especially likely if the default router is 
running an IOS version that is subject to CSCeb53542.

CSCsh48977—The controller IP stack becomes inoperable on a large Layer 2 subnet. The controller 
stops responding to pings, SNMP, and other management traffic, and RADIUS stops working. 
Access points stay connected, but client devices are able to associate and pass traffic only on 
WLANs that do not require authentication.

CSCsh49310—Clearing the configuration on a 2000 series controller sometimes corrupts the image.

CSCsh50527—NPU truncates padding from unicast ARP frames. Access points now use the length 
field in the LWAPP header to determine the number of bytes to transmit over the air. As a result, 
padding is stripped from unicast ARP frames.

CSCsh61347—In some regulatory domains outside the U.S. and Canada, mesh access points fail to 
join a controller after they are upgraded from software release 4.0.179.11 to 4.0.206.

CSCsh64994—RADIUS account records are not generated when an access point is configured in 
hybrid-REAP mode with a locally switched SSID.

CSCsh67106—The AAA interface override results in ACLs that are sometimes not installed.

CSCsh68089—Access points connected directly to a port on 2000 or 4400 series controllers 
sometimes fail to receive an IP address through DHCP.

CSCsh68460—The controller allows the Web Authentication Headline template with an apostrophe 
to be successfully applied from WCS even though apostrophes are not allowed on the controller.

CSCsh69985—When a Cisco 7920 phone is associated to a lightweight access point, the controller 
sometimes fails to forward packets to the phone.

CSCsh73667—The controller drops the broadcast DHCP offer for the RLDP feature.

CSCsh74316—In controller software release 4.0.179.8, guest tunneling between a foreign controller 
and an anchor controller may fail due to a WLAN security policy mismatch.

CSCsh77760—Access point fallback mode does not work correctly for 1000 series access points 
when master controller mode is enabled. The access points should leave their controller and migrate 
to the master controller; however, they stay attached to the current controller.

CSCsh80542—If the AP1000 has both radios disabled and it receives a new IP address, it does not 
send the IP address payload to the controller. The result is multiple ARP entries on the controller.

CSCsh81746—The GE Dash unit requires padding. It is an 802.11 client that discards any received 
packet that has an 802.11 payload of less than 46 bytes.

CSCsh84930—The RFID telemetry vendor field does not support up to 128 bytes.

CSCsh85147—The controller may reboot when handling large telemetry values.