Cisco Cisco 2000 Series Wireless LAN Controller

This section lists resolved and open caveats for Cisco controllers and lightweight access points.

These caveats are resolved in software release 3.2.195.10.

CSCsf10181—A REAP access point may reboot when you change its mode of operation from 
standalone to connected.

CSCsh57637—When a switch that is connected to several access points using power-over-Ethernet 
(PoE) is repeatedly rebooted, one or more access points may fail during bootup.

CSCsh68089—Access points directly connected to the 2006 or 4000 controller are unable to 
perform DHCP.

CSCsh71613—When you attempt to migrate an access point from the -J regulatory domain to the 
-U regulatory domain, the access point may reboot after you enter the show ap migrate command.

CSCsh97875—When you migrate an access point from the -J regulatory domain to the -U regulatory 
domain, the channel settings may not update properly. They should update as follows: channel 34 to 
36, channel 38 to 40, channel 42 to 44, and channel 46 to 48. For example, if the access point’s radio 
used channel 34 in the -J regulatory domain, it should switch to channel 36 after migration. 
However, it may switch to some other channel, such as 44.

CSCsi03229—An access point with the -J regulatory domain may join the controller with the 
country code configured as Argentina (AR), Brazil (BR), or Thailand (TH).

These caveats are open in software release 3.2.195.10.

CSCar14535—When configuring a mobility group anchor that is not part of the mobility member 
list, the controller displays an “Invalid Parameter Provided” error message.

Workaround: Make sure that the anchor controller is a mobility group member.

CSCsa95763—The controller GUI cannot display more than 80 local net users on the Security > 
AAA > Local Net Users page.

Workaround: Use the controller CLI to view all the Local Net User entries.

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.

Workaround: 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.

Workaround: Reboot the controller through the CLI to access the wizard again.