Guidelines For Upgrading To Controller Software 5.2 In Mesh Networks - Cisco 2100 Series Configuration Manual

Chapter 9 Managing Controller Software and Configurations
Table 9-1
Current Software Release
3.2.78.0 or later 3.2 release
4.0.155.5 or later 4.0 release
4.1.171.0 or later 4.1 release
4.1.191.xM or 4.1.192.xM
4.2.61.0, 4.2.99.0, or 4.2.112.0
4.2.130.0
4.2.173.0 or 4.2.176.0
5.0.148.0 or later 5.0 release
5.1.151.0 or later 5.1 release
•
If you require a downgrade from one release to another, you may lose the configuration from your
Caution
current release. The workaround is to reload the previous controller configuration files saved on the
backup server or to reconfigure the controller.

Guidelines for Upgrading to Controller Software 5.2 in Mesh Networks

Before upgrading your controller to software release 5.2 in a mesh network, you must comply with the
Caution
following rules.
OL-17037-01
Upgrade Path to Controller Software Release 5.2
When you upgrade the controller to an intermediate software release, wait until all of the
Note
access points joined to the controller are upgraded to the intermediate release before you
install the 5.2 software. In large networks, it may take some time to download the software
on each access point.
Cisco recommends that you install the Cisco Unified Wireless Network Controller Boot Software
5.2.157.0 ER.aes file on all controller platforms. This file resolves CSCsm03461 and is necessary
to view the version information for ER.aes files in the output of the show sysinfo CLI command. If
you do not install this ER.aes file, your controller does not obtain the fix for this defect, and "N/A"
appears in the Field Recovery Image Version field in the output of this command.
The ER .aes files are independent from the controller software files. You can run any
Note
controller software file with any ER.aes file. However, installing the latest boot software file
(5.2.157.0 ER.aes) ensures that the boot software modifications in all of the previous and
current boot software ER.aes files are installed.
Upgrade Path to 5.2 Software
First upgrade to a 4.1 release and then upgrade to 4.2.176.0 before
upgrading to 5.2.
Upgrade to 4.2.176.0 before upgrading to 5.2.
Upgrade to 4.2.176.0 before upgrading to 5.2.
You can upgrade directly to 5.2.
Upgrade to 4.2.176.0 or to a 5.1 release before upgrading to 5.2.
Upgrade to 4.2.176.0 before upgrading to 5.2.
You can upgrade directly to 5.2.
You can upgrade directly to 5.2.
You can upgrade directly to 5.2.
Cisco Wireless LAN Controller Configuration Guide
Upgrading Controller Software
9-3