Cisco Cisco 4402 Wireless LAN Controller

CSCsc11660—The current country screen is not 100% accurate for all deployment scenarios, which 
may cause confusion in some instances. 

Workaround: None at this time. 

CSCsc68154—The controller’s error log repeatedly displays the “Got an idle-timeout message from 
an unknown client” error message for some unknown reason.

Workaround: None at this time.

CSCsd52483—When you make changes in the boot loader of a 2006 controller or a Controller 
Network Module, the bootup process may halt, and the controller may stop responding. 

Workaround: None at this time. The controller must be returned for repair through the RMA process.

CSCsd54171—After the controller configuration is modified, the changes may not take effect or 
function properly. 

Workaround: Save the controller configuration to a TFTP server or WCS; then reset the controller 
to restore the default configuration. After completing the setup wizard, reload the saved 
configuration from the TFTP server or WCS.

CSCse10109—For WMM clients without TSPEC support, ACM must be disabled for proper QoS 
mapping.

Workaround: Disable ACM for WMM clients without TSPEC support.

CSCse66714—When you use the controller GUI to set a static IP address on a different subnet than 
the one the access point is on, the access point reboots, but the GUI page does not refresh. When the 
access point reboots, it sometimes uses a fallback address, and the display shows the static IP 
address configuration as well as the IP address it is using.

Workaround: Check the configuration using the show ap config name CLI command, which shows 
the access point using a fallback address.

CSCsf29806—When a mesh access point (MAP) joins the controller with the default bridge group 
name (BGN), the MAP BGN should appear as “DEFAULT.” However, the MAP BGN value is empty 
if the MAP does not have a BGN set or if the set value shows up on the controller even though the 
MAP joined the controller with the “DEFAULT” BGN string.

Workaround: None at this time. 

CSCsf99924—There is no option for configuring the controller to adjust automatically for daylight 
saving time. 

Workaround:

Configure the controller for Greenwich mean time (GMT), with no timezone offset.

During standard time, run with the standard offset. When daylight saving time takes effect, 
manually configure the controller time for the correct local time. For example, if your controller 
is in the US Eastern timezone, then before March 11, 2007, your offset is -5.  When DST takes 
effect, enter this CLI command:

CSCsg04339—Controller user documentation does not mention this limitation: Controllers allow a 
maximum of 16 DHCP scopes.

CSCsg12879—When you attempt to disable power-over-Ethernet (PoE) through the controller GUI, 
the following error message appears: “Error is setting Power Over Ethernet.”

Workaround: None at this time.