Release Notes

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

OL-31336-01

Caveats

• CSCsj61649—Whenever a log analysis report is generated on a CCXv5 client using WCS, the

DHCP and AAA logs are swapped.

Workaround: Use the controller CLI to view this information.

• CSCsj67447—When you use the controller GUI to modify an existing (or newly created) guest LAN

and you choose an ingress interface that is already in use, no error appears. The error that appears

on the CLI should also appear on the GUI: “Ingress interface is in use by some other guest lan.”

Workaround: None.

• CSCsj85329—The controller GUI should explain how the password changes with RADIUS

compatibility mode. The RADIUS server names help users match to their type of RADIUS server, but

the server types should be explained:

–

Cisco ACS—In the RADIUS access-request packet, the username is the client MAC address,

and the password is the client MAC address.

–

Free RADIUS—In the RADIUS access-request packet, the username is the client MAC address,

and the password is the controller’s shared secret with the RADIUS server.

–

Other—In the RADIUS access-request packet, the username is the client MAC address, and the

password is not sent in the RADIUS access-request packet.

Workaround: None.

• CSCsj87925—The controller GUI netmask for an ACL accepts arbitrary values.

Workaround: Enter a valid netmask.

• CSCsj88889—WGB and wired WGB clients are shown using different radios.

Workaround: None.

• CSCsj88990—Rogue access point client information shown for the access point does not match the

client information from the Rogue Client Details link.

Workaround: View the current rogue client information from the controller.

• CSCsj96589—Using the MAC address from the label on an 1131 or 1242 access point in the debug mac

addr command produces limited debug output.

Workaround: None.

• CSCsj97900—The call admission control (CAC) TSPEC is not traffic shaping and allows a new call

setup when the physical data rate is higher than one single data rate configured on the controller.

Workaround: Follow the instructions in the VoWLAN deployment guide to enable a realistic higher

data rate for the Cisco 7921 phone and turn on the supported rate as recommended.

• CSCsk01633—The EAPOL key message is truncated with an invalid replay counter.

Workaround: None.

• CSCsk08401—The formatting for the config paging ? CLI command needs to be corrected.

Workaround: None.

• CSCsk08707—The 1250 series access points receive console error messages indicating that the

primary discover decode failed.

Workaround: None.

• CSCsk12420—Sometimes a 1000 series access point does not accept the DHCP offer from a

Catalyst 3750 switch.

Workaround: None.