Release Notes

Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.176.0

OL-31336-01

Caveats

• CSCsu84220—When Cisco 1131 and 1242 access points are joined to a controller running software

release 4.2.130.0 and a WAN outage occurs, the access points come back up, but sometimes the

radios do not.

Workaround: Reboot the access points.

• CSCsu84498—The transmit diversity for multicast-broadcast packets is not alternating on the 1240

series access point’s antenna ports.

Workaround: None.

• CSCsu84629—The 1250 series access points change from maximum uniform transmit power back

to maximum transmit power on neighbor discovery packets.

Workaround: None.

• CSCsu86627—The controller currently issues commands to transmit single neighbor discovery

packets. However, the controller should issue bursts of neighbor discovery packets to access point

radios in order to force radio transmit power control loops to settle at new power settings.

Workaround: None.

• CSCsu88532—When you download new software to the controller, a routine system resource

notification appears on the controller console.

Workaround: None.

• CSCsu90335—Intel 4965 client cards might lose connectivity for up to 1 minute when another client

connects to the same 1250 series hybrid-REAP access point on a controller running software release

4.2.130.0.

Workaround: Disable local switching on the SSID.

• CSCsu92667—The controller might reboot after you make a change to the configuration.

Workaround: None.

• CSCsu95855—After you change the mobility group name on some controllers, you cannot remove

one of the controllers. An error appears stating that the controller is configured as an anchor for a

WLAN, even though none of the existing WLANs has this controller configured as its anchor.

Workaround: If the CLI shows that this controller is configured as an anchor for a WLAN that does

not exist, create that WLAN. Then overwrite the WLAN and remove its anchors. Then you can

remove the controller from the mobility group.

• CSCsu96916—When you issue the show run-config CLI command via SSH on a 4400 series

controller running software release 4.2.130.0 with paging disabled, the output locks up at a certain

point, probably because the controller runs out of buffers.

Workaround: Enable paging or use a Telnet session.

• CSCsu98641—The core-dump configuration does not show in the running configuration on the

Cisco WiSM.

Workaround: None.

• CSCsv00108—An invalid message integrity check (MIC) might be reported on beacon frames.

Workaround: None.

• CSCsv01484—The controller prepends UID usernames with “CN=,” which can cause problems for

LDAP authenticated binds. The controller should check for usernames with “UID” but not prepend

them with “CN=.”

Workaround: None.