Cisco Cisco 2106 Wireless LAN Controller

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

CSCsi22591—Changing the 802.11a channel on the RAP access point turned off RRM channel 
assignment on the 802.11b radios for all the access points on the sector.

CSCsi49767—When a WLAN was configured with an interface that had an ACL and an AP group 
had been applied on the access point that overrode the ACL, the controller sometimes crashed when 
a client associated to the access point.

CSCsi68958—MAP reported radar events on the backhaul when radar was detected on another 
channel. The MAP would send radar detect messages to the controller and the controller would 
change the MAP’s channel. This could cause a scanning MAP to become stranded.

CSCsj69233, CSCsj70841—In certain configurations, controllers had problems handling Address 
Resolution Protocol (ARP) packets from wireless clients that could result in a denial of service 
(DoS) in certain environments.

CSCsb01980—When the operator enters incorrect data for the management interface in the 
controller web configuration wizard, error messages are shown only at the end of the wizard, and 
the user must return to the Management Interface page for correction. The data entered on the 
Management Interface page, such as the port number, are not validated immediately but at the end 
of the wizard. As a result, any error messages are shown only at the end. The workaround is to use 
the CLI configuration wizard.

CSCsb01983—The controller web configuration wizard is not reachable after making repeated 
invalid entries for the management interface port. If an operator connects to the wizard on address 
192.168.1.1 and enters an invalid port number on the Management Interface page, the operator is 
redirected at the end of the wizard to the Management Interface page to correct the port. If the 
operator enters an incorrect port and submits, the wizard becomes inaccessible. The workaround is 
to reboot the controller through the CLI to access the wizard again.

CSCsh81683—The WiSM controller sometimes becomes unmanageable: it cannot be pinged or 
accessed through telnet or other protocols. Disabling Gigabit ports 3 and 4 on the Catalyst 6000 
switch side of the port channel causes the WiSM to become fully operational. The workaround is to 
reboot the WiSM.

CSCsi32464—The controller sometimes drops data traffic when the controller moves to the backup 
port on the same NPU. The workaround is to configure the backup port as port 3.

If you need information about a specific caveat that does not appear in these release notes, you can use 
the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:

(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not 
yet have a customer-visible description, or the defect might be marked Cisco Confidential.)