Filter
Top Products
25
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.171.6
OL-11567-02
Caveats
• CSCse30514—When an LWAPP-enabled AP1100 or AP1200 first connects to a controller, the
secondary controller name on the All APs > Details page in the controller GUI is not blank. The
output of the show ap config general command also shows that the secondary controller name is
not blank.
Workaround: None at this time.
• CSCse30696—The controller does not refresh the access point’s IP address correctly when the
admin status for that access point is disabled.
Workaround: None at this time.
• CSCse32656—The 4402 controller supports an enhanced security module (ESM) card only in slot
1, not in slot 2. Slot 2 is reserved for 4404 controllers.
Workaround: Use slot 1, which is the slot closest to the power outlet, for an ESM card in the 4402
controller.
• CSCse40636—The foreign controller incorrectly forwards multicast traffic onto the auto-anchor
WLAN.
Workaround: Configure the WLAN on the foreign controller to map to an invalid VLAN.
• CSCse52143—IPSec authentication with certificates may not always operate properly.
Workaround: None at this time.
• CSCse60689—The controller may reboot due to a failure with the sshpmAddIPv4IpsecRules
software.
Workaround: None at this time.
• CSCse72413—The controller may reboot due to a failure with the debugMaintask software.
Workaround: None at this time.
• CSCse80636—Under heavy traffic conditions, the VPN module may reach capacity and fail to
accept additional packets.
Workaround: None at this time.
• CSCsf10167—The controller may reboot due to a failure with the pemReceiveTask software
watchdog.
Workaround: None at this time.
• CSCsf11862—Controllers sometimes reboot during a software upgrade.
Workaround: Download the software image twice. On the second try, the controller successfully
loads the new image.
• CSCsg10391—When you use the remote-debug enable command on the controller CLI to enable
remote debugging on an access point, debugging stops when your CLI session times out.
Workaround: Open a new CLI session, disable remote debugging (enter remote-debug disable), and
re-enable remote debugging.