Release Notes

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

OL-31336-01

Caveats

• CSCsk86536—The wrong error message appears when you change country channels with the

802.11a radio enabled.

Workaround: None.

• CSCsl01005—Sometimes bandwidth contracts do not take effect. If a user who has bandwidth

restrictions logs in and logs out and then another user who does not have bandwidth restrictions logs

in, the bandwidth restrictions are not removed immediately.

Workaround: Reassociate the user between logout of the old user and login of the new user.

• CSCsl03097—When a hybrid-REAP access point in standalone mode is on the DFS channel, the

access point’s radio goes down if a radar event occurs on its operating channel.

Workaround: Wait until the access point’s connectivity to the controller recovers, or reboot the

access point.

• CSCsl04281—The show run-config command might truncate access point neighbor information in

a large environment.

Workaround: To reduce the occurrence of this issue, disable paging using the config paging disable

command.

• CSCsl09066—The WCS access point group VLAN profile configuration does not match the actual

WLC configuration when you use multiple interface mapping profiles under the same access point

group VLAN where all of the SSIDs start with the same letters or numbers.

Workaround: None.

• CSCsl11352—The console output in software release 4.2 does not indicate which controller an

access point joins when you add it to your network.

Workaround: On the access point console, right after you see the “Press Return to get started”

message, enter enable mode (the default password is Cisco), and enter this debug command:

debug ip udp

The output shows all UDP packets sent and received by the access point.

• CSCsl16445—When an access point radio status is down due to lack of CDP response from a

neighboring switch, the controller reports Cause=Unknown. However, it should report

Cause=Waiting for CDP response.

Workaround: None; this issue is cosmetic.

• CSCsl40018—The hybrid-REAP design and deployment guide incorrectly implies that you can

configure NAT on both the hybrid-REAP and controller sides of the network link. In reality, NAT is

supported only on the access point side of the network link. The hybrid-REAP design and

deployment guide is available at this URL:

http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/71250-h-rea

p-design-deploy.html

Workaround: None.

• CSCsl41764—An access point should send a neighbor list to its clients as soon as it accepts the

association.

Workaround: None.

• CSCsl42328—The controller should not allow you to use the IP address of the gateway as the

interface address.

Workaround: Make sure that the interface IP address and gateway IP address are different.