Release Notes
36
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.176.0
OL-31336-01
Caveats
• CSCsq35590—If you change a 1240 series access point’s country of operation from Spain to the
U.S., tracebacks might occur while the access point joins the controller.
Workaround: None.
• CSCsq37810—If you add a controller to WCS and later reboot the controller, WCS does not receive
the trap for a cold start, which prevents it from pushing the configuration back to the controller.
Workaround: Manually push the configuration from WCS.
• CSCsq38075—If you change a 1240 series access point’s country of operation to Spain, tracebacks
might appear on the access point console.
Workaround: None.
• CSCsq38700—If you change the power level on an access point radio while clients are associated
to the access point, the controller might display DOWN for the operational status of that radio.
However, clients continue to pass traffic and function properly.
Workaround: None.
• CSCsq47493—The cLReapApVlanId is not being updated on the controller, and the API is not
throwing any exception to indicate that it has not been set.
Workaround: First change the native VLAN ID. Then change the cLReapApVlanId.
• CSCsq67907—If a large number of rogue access points are present and there is a substantial amount
of client activity, the apfRogueTask might report lock asserts.
Workaround: None.
• CSCsq73118—When a Cisco WiSM is used with multiple WLANs and the VLAN override feature,
malformed packets might appear on the native VLAN associated to the link aggregation (LAG)
trunk.
Workaround: Isolate the native VLAN on the switch so that it does not propagate malformed
packets.
• CSCsq74144—The controller does not show the channel on which an access point in sniffer mode
is sniffing. It shows only the last channel on which the access point was broadcasting in local mode.
Workaround: None.
• CSCsr01195—The controller drops a packet after a train of large packets.
Workaround: None.
• CSCsr02316—Some SNMPSet operations show a successful status even though the controller is
truncating the string.
Workaround: Set a shorter value for the string.
• CSCsr18694—After passing a substantial amount of traffic, the D0 interface might shut down on a
controller running software release 4.2.173.0. Some packets might be stuck in the queue.
Workaround: None.
• CSCsr20434—Missing and invalid message integrity check (MIC) management frame protection
(MFP) traps might be reported on 1250 series access points.
Workaround: None.
• CSCsr32354—When a 1250 series access point with an external power supply is connected to a
6548 FE blade inside a Cisco Catalyst 6500 switch, the line protocol does not come up after a reset.
This problem also occurs intermittently when a power injector is used.
Workaround: None.