Cisco Cisco 4404 Wireless LAN Controller Notas de publicación

CSCsh04777—The AP1000 does not periodically send neighbor packets on the non-dynamic 
frequency selection (DFS) channels (36-48). As a result, the access point is hindered from properly 
forming a neighborhood with other access points in the same RF domain.

CSCsh12911—Configurations are sometimes sorrupted in access points in MAP mode after 
software upgrade.

CSCsh20492—Access points in MAP mode sometimes reboot after they receive a configuration 
request from the controller.

CSCsh35306—Unicast ARPs may drop from export-foreign clients because the IP address is not 
known at the foreign controller.

CSCsh44486, CSCsh45987—A 1200 series access point sometimes reboots when a client device is 
associated to the radio interface that you're configuring. 

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 contols 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.

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.

CSCsh50966, CSCsh47906—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 is especially likely if the default router is running 
an IOS version that is subject to CSCec40253.

CSCsh56703—The controller interface now indicates whether RFID is enabled on an access point.

CSCsh59927—Access points sometimes fail to set the encryption keys after a CCKM roam due to 
a timing issue.

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.

CSCsh61708—Access points in MAP mode in the -E regulatory domain sometimes require up to 
thirty minutes to reassociate to the RAP-mode access point when the channel is changed on the RAP 
access point.

CSCsh62107—Change tags are now supported on a per-platform basis.

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

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