Cisco Cisco 4404 Wireless LAN Controller Release Notes
29
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.202.0
OL-15156-01
Caveats
•
CSCse34481—Numerous system event messages are received when trying a TFTP download.
Workaround: None.
•
CSCse52143—IPSec authentication with certificates may not always operate properly.
Workaround: None.
•
CSCse72413—The controller may reboot due to a failure with the debugMaintask software.
Workaround: None.
•
CSCse80636—Under heavy traffic conditions, the VPN module may reach capacity and fail to
accept additional packets.
accept additional packets.
Workaround: None.
•
CSCse88067—An “aborting SA dump due to timeout” error message is received when entering
show ipsec brief command on the 4012 controller console.
show ipsec brief command on the 4012 controller console.
Workaround: None.
•
CSCsf04684—On the 4400, the FPGA and VPN module are losing some packets. The packet loss
is a small percentage of total throughput.
is a small percentage of total throughput.
Workaround: None.
•
CSCsf17520—With REAP AP connected to the controller, the first WLAN with WMM enabled on
the controller does not get a client DHCP IP address.
the controller does not get a client DHCP IP address.
Workaround: You can disable the WMM from which the client gets the IP address.
•
CSCsf21931—The Cisco WiSM does not support Layer 2 LWAPP mode.
Workaround: The option to configure Layer 2 LWAPP mode is available through both the controller
GUI and CLI.
GUI and CLI.
•
CSCsf27061—If you are configuring the AP group VLAN, all controller interfaces (CLI, web, and
WCS) show the dynamic ap-manager interface in the interface-mapping-to-the-WLAN list. Because
dynamic AP manager is not supposed to be mapped to a WLAN, it should not appear in the list.
WCS) show the dynamic ap-manager interface in the interface-mapping-to-the-WLAN list. Because
dynamic AP manager is not supposed to be mapped to a WLAN, it should not appear in the list.
Workaround: None.
•
CSCsf28181—When two ct4400s are connected and security mobility is enabled, the client loses
the current IP address from the dynamic interface during the handoff and gets a new IP address from
the new controller.
the current IP address from the dynamic interface during the handoff and gets a new IP address from
the new controller.
Workaround: None.
•
CSCsh41347—The following warning appears when you enter dynamic interface details and click
Apply:
Apply:
Changing the Interface parameters causes the WLANs to be temporarily disabled and thus
may result in loss of connectivity for some clients.
After accepting the warning message, the GUI does not apply the interface configuration. This
warning occurs only on a ct4000 and ct2006.
warning occurs only on a ct4000 and ct2006.
Workaround: None.
•
CSCsh44942—When an ipsec client roams from a 4400 to a 4000 controller, a crash occurs in
apfReceiveTask, and a “crypto card not responding” message occurs.
apfReceiveTask, and a “crypto card not responding” message occurs.
Workaround: None.
•
CSCsh45097—When associating a client to an ipsec WLAN on a 4000 locally, a “crypto card not
responding” error message appears.
responding” error message appears.
Workaround: None.