Cisco Cisco 2000 Series Wireless LAN Controller
18
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.0.179.11
OL-11734-01
Caveats
•
CSCsc04907—Resetting the access point to factory defaults does not clear the static IP address.
Workaround: Clear the access point’s static IP address by hand.
•
CSCsc05495—Controllers intermittently send a state attribute 24 in an access-request packet.
Workaround: Apply the Microsoft KB 883659 patch to IAS. The Microsoft patch may or may not
work. There is no workaround on the controller.
work. There is no workaround on the controller.
•
CSCsc11660—The current country screen is not 100% accurate for all deployment scenarios, which
may cause confusion in some instances.
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.
an unknown client” error message for some unknown reason.
Workaround: None at this time.
•
CSCsd25491—The management IP address of a controller incorrectly sends an ARP request for a
client IP address on a WLAN subnet over the wired interface. The ARP request is not answered
because the management IP address and the client WLAN are on different subnets.
client IP address on a WLAN subnet over the wired interface. The ARP request is not answered
because the management IP address and the client WLAN are on different subnets.
Workaround: None at this time.
•
CSCsd27529—Static WEP does not operate properly for a REAP access point in standalone mode.
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.
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.
function properly.
Workaround: Save the controller configuration to a TFTP server or WCS, then reset the controller.
After completing the setup wizard, reload the saved configuration from the TFTP server or WCS.
After completing the setup wizard, reload the saved configuration from the TFTP server or WCS.
•
CSCsd54750—The Cisco WiSM may display numerous timeout messages.
Workaround: None at this time.
•
CSCsd69158—After a RADIUS session timeout expires, the access point does not send a unicast
key to the client.
key to the client.
Workaround: None at this time.
•
CSCsd82363—Channel utilization is incorrectly reported in radio utilization reports on the
controller and in WCS. Channel utilization may appear as zero when there is active client traffic or
as an aggregate of client transmit and receive traffic.
controller and in WCS. Channel utilization may appear as zero when there is active client traffic or
as an aggregate of client transmit and receive traffic.
Workaround: None at this time.
•
CSCsd85126—The access point may reboot unexpectedly after upgrading to software release
3.2.116.21.
3.2.116.21.
Workaround: None at this time.
•
CSCsd87382—Bridging functionality for REAP devices is not available on OEM builds of
controller software.
controller software.
Workaround: None at this time.
•
CSCsd95992—When IGMPv3 is enabled on the controller, a significant amount of packet loss
occurs. The packet loss is even greater when there is an active multicast stream.
occurs. The packet loss is even greater when there is an active multicast stream.
Workaround: None at this time.