Cisco Cisco 4402 Wireless LAN Controller

CSCsk08657–In the controller GUI, entry of an antenna gain greater than the highest allowed 
antenna gain threshold value is allowed with no resulting error message.

Workaround: Verify that the entered antenna gain is within the FCC limit.

CSCsk32623–When Bridge Group Names (BGN) are not employed in a mesh network, access 
points might flap between the Ethernet and 802.11a backhaul uplinks.

Workaround: Always configure and use Bridge Group Names in the network.

CSCsl70218–The BOOT bootloader environment variable is not set on some early shipments of 
1520 mesh access points. Any image download that fails during upgrade might cause a partial image 
to be written on the1520. Without the BOOT variable, the bootloader might attempt to boot the 
partial image rather than the original complete image, causing the 1520 to get stuck and not join the 
controller. 

This is seen when a controller is upgraded from mesh release 4.1.190.5 to 4.1.191.24M and the 1520 
has a wireless connection to the controller. It might also happen when a controller is upgraded from 
4.1.190.5 to other future mesh releases.

Workaround: To recover from an incomplete 1520 boot up due to a 4.1.190.5 to 4.1.191.24M 
upgrade, enter the following bootloader commands in the AP console:

delete flash:/update/c1520-k9w9-mx.124-3g.JMB/c1520-k9w9-mx.124-3g.JMB

set BOOT flash:/c1520-k9w9-mx.124-3g.JMA/c1520-k9w9-mx.124-3g.JMA

boot

To verify the configuration, enter

set

For details on connecting to the AP console, refer to the “Connecting to the Access Point 
Locally”

 

section of the

 

Installation Guide found at: 

To prevent the 1520 boot up problem, a change in the boot variable must be made prior to 
4.1.190.5 from a compatible non-mesh release or any upgrade from 4.1.190.5 to 
4.1.191.24M (or greater mesh release). Refer to the 

 for configuration details. 

CSCsj70714–When an AP 1520 radio was trying to back off to send a beacon, it did not 
acknowledge (ACK) receipt of a packet. This condition could cause an increase in packet retry 
events when a large size packet was sent at low rate.