Release Notes

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

OL-31336-01

Caveats

Workaround: Install the Cisco Unified Wireless Network Controller Boot Software 4.2.112.0 ER.aes

file, which contains a new bootloader. A successful transfer and upgrade of the ER file indicates that

the ER file has been updated properly.

• CSCsm08623—If the config paging disabled CLI command is entered on the controller, the output

of the show msglog command is periodically interrupted with the “Would you like to display the

next 15 entries?” prompt.

Workaround: None.

• CSCsm25943—The meaning of the following error message on the controller is not clear. This

message does not necessarily imply that any actual “ARP poisoning” is occurring. Rather, this

message appears when a WLAN is configured for DHCP Required and a client (after associating to

this WLAN) transmits an ARP message without first using DHCP. The client is unable to send or

receive any data traffic until it performs DHCP through the controller.

DTL-1-ARP_POISON_DETECTED: STA [00:01:02:0e:54:c4, 0.0.0.0] ARP (op 1) received with

invalid SPA 192.168.1.152/TPA 192.168.0.206

Workaround: Perform the following steps:

a. Determine whether you want to force your wireless clients to perform DHCP first, after

associating, before they can send IP packets.

•If you do, then disable DHCP Required, and you will not encounter this problem.

•If you do not, then configure all clients to use DHCP.

b. If the client is configured for DHCP but sometimes still sends IP packets after associating

without performing DHCP, then perform the following:

•Verify that the client eventually does perform DHCP without undergoing an unacceptable

outage. If the outage before performing DHCP is acceptable, then you can ignore this

message.

•If the client never does perform DHCP after associating, then it can never pass Layer 3 traffic.

In this case, either determine how to change the client’s behavior so that it always performs

DHCP after associating, or simply accept that this client does not work in this application

or reconsider your decision to use DHCP Required.

• CSCsm32845—The Guest LAN parameter on the Interfaces > Edit page of the controller GUI might

cause confusion for users because the guest LAN is used for interfaces involved in wired guest

LANs, not for wireless guest WLANs.

Workaround: None.

• CSCsm34676—Voice quality might be poor with multicast paging.

Workaround: None.

• CSCsm40870—The following error message should be reworded:

Jan 24 15:20:55.374 apf_80211.c:2552 APF-4-ASSOCREQ_PROC_FAILED: Failed to process an

association request from00:13:ce:37:8b:ff. WLAN:2, SSID:TMDInternal-WPA. mobile in

exclusion list or marked for deletion

The message should read as follows:

ASSOCREQ_PROC_FAILED: Failed to process an association request from 00:13:ce:37:8b:ff.

WLAN:2, SSID:TMDInternal-WPA. Mobile excluded or marked for deletion.

Workaround: None.