Cisco Cisco Wireless Services Module 2 (WiSM2)

You can upgrade or downgrade the controller software only between certain releases. In some 
instances, you must first install an intermediate release prior to upgrading to software release 
7.0.250.0. 

 shows the upgrade path that you must follow before downloading software release 

7.0.250.0.

Before you use an AP802 series lightweight access point with controller software release 7.0.250.0, 
you must upgrade the software in the Next Generation Cisco 880 Series Integrated Services Routers 
(ISRs) to Cisco IOS 151-4.M or later releases.

When you upgrade the controller to an intermediate software release, wait until all of the access 
points associated with the controller are upgraded to the intermediate release before you install the 
7.0.250.0 software. In large networks, it can take some time to download the software on each access 
point.

You cannot install the Cisco Unified Wireless Network Controller Boot Software 7.0.230.0 ER.aes 
file on the Cisco 5500 Controller platform.

Field Upgrade Software (FUS) is a special AES package that contains several system related 
component upgrades. These include the bootloader, field recovery image, and FPGA/MCU 
firmware. Installing the FUS image requires special attention because it installs some critical 
firmware. The FUS image is independent of the runtime image. FUS version 1.9.0.0 can be used for 
the 7.0.250.0 release. For more information about installing FUS, see 

 On this page, from the Choose Topic drop-down list, choose Other to see the FUS 

release notes.

The ER 

.aes

 files are independent from the controller software files. You can run any controller 

software file with any ER.aes file. However, installing the latest boot software file (7.0.116.0 
ER.aes) ensures that the boot software modifications in all of the previous and current boot software 
ER.aes files are installed.

Consider a network deployment scenario where an OfficeExtend Access Point is configured with the 
Least Latency Join option enabled and the controller is configured with NAT enabled. The Least 
Latency Join feature enables the access point to choose a controller with the least latency when 
joining, that is, when the feature is enabled, the access point calculates the time between the 
discovery request and the response and joins the controller that responds first. NAT enables a device 
such as a router to act as an agent between the Internet and the local network. NAT enables you to 
map the intranet IP address of a controller to a corresponding external address.

When an OfficeExtend Access Point that is configured with the Least Latency Join option and is 
upgraded to the controller release 7.0.250.0 tries to associate to the controller with NAT enabled, 
the access point fails to join the controller. Due to an update to the software code of 7.0.250.0, the 
OEAP tries to join the non-NAT IP address, fails to join, and tries a rediscovery that fails again. The 
OEAP can never connect to the controller.

The issue can be resolved by setting the access point mode to local mode on the controller and let 
the access point join the controller. On joining, you must disable least latency join and upgrade to 
7.0.250.0 release.

If you require a downgrade from one release to another, you might lose the configuration from your 
current release. The workaround is to reload the previous controller configuration files saved on the 
backup server or to reconfigure the controller.

Control which address(es) are sent in CAPWAP discovery responses when NAT is enabled on the 
Management Interface using the following command:

config network ap-discovery nat-ip-only {enable | disable}

Where: