- 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.
-
It is not
possible to directly upgrade to this release from a release that is older than
6.0.182.0.
-
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 the latest software release.
-
When you
upgrade the controller to an intermediate software release, you must wait until
all of the access points that are associated with the controller are upgraded
to the intermediate release before you install the latest controller software.
In large networks, it can take some time to download the software on each
access point.
-
When you
upgrade to the latest software release, the software on the access points
associated with the controller is also automatically upgraded. When an access
point is loading software, each of its LEDs blinks in succession.
-
We recommend
that you access the controller GUI using Microsoft Internet Explorer 6.0 SP1
(or a later release) or Mozilla Firefox 2.0.0.11 (or a later release).
-
Cisco
controllers support standard SNMP Management Information Base (MIB) files. MIBs
can be downloaded from the Software Center on Cisco.com.
-
The controller
software is factory installed on your controller and automatically downloaded
to the access points after a release upgrade and whenever an access point joins
a controller. We recommend that you install the latest software version
available for maximum operational benefit.
-
We recommend
that you install Wireless LAN Controller Field Upgrade Software for Release
1.7.0.0-FUS, which 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. For more information, see
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html.
-
Ensure that you have a TFTP or FTP server available for
the software upgrade. Follow these guidelines when setting up a TFTP or FTP
server:
-
Ensure that your TFTP server
supports files that are larger than the size of the controller software
release. Some TFTP servers that support files of this size are tftpd32 and the
TFTP server within the Cisco Prime Infrastructure. If you attempt to download
the controller software and your TFTP server does not support files of this
size, the following error message appears: “TFTP failure while storing in
flash.”
-
If you are
upgrading through the distribution system network port, the TFTP or FTP server
can be on the same or a different subnet because the distribution system port
is routable
-
When you plug
a controller into an AC power source, the bootup script and power-on self-test
run to initialize the system. During this time, you can press Esc to display
the bootloader Boot Options Menu. The menu options for the 5500 and Flex 7500
series controllers are different than for other controller platforms.
Bootloader
menu for 5500 Series Controllers:
Boot Options
Please choose an option from below:
1. Run primary image
2. Run backup image
3. Change active boot image
4. Clear Configuration
5. Format FLASH Drive
6. Manually update images
Please enter your choice:
Bootloader menu for other controller platforms:
Boot Options
Please choose an option from below:
1. Run primary image
2. Run backup image
3. Manually update images
4. Change active boot image
5. Clear Configuration
Please enter your choice:
Enter
1 to run
the current software, enter
2 to run
the previous software, enter
4 (on a
5500 series controller), or enter
5 (on
another controller platform) to run the current software and set the controller
configuration to factory defaults. Do not choose the other options unless
directed to do so.
Note |
See the
Installation Guide or the Quick Start Guide for your controller for more
details on running the bootup script and power-on self-test.
|
-
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
Note |
To avoid
stranding APs, you must disable AP link-latency (if enabled) before you use the
disable option for the
config network ap-discovery
nat-ip-only command. To disable AP link-latency, use the
config ap link-latency
disable all command.
|
-
You can
configure 802.1p tagging by using the
config qos dot1p-tag
{bronze |
silver |
gold |
platinum} tag. For the 7.2.103.0 and later
releases, if you tag 802.1p packets, the tagging has impact only on wired
packets. Wireless packets are impacted only by the maximum priority level set
for QoS.
-
You can reduce
the network downtime using the following options:
-
You can
predownload the AP image.
-
For
FlexConnect access points, use the FlexConnect Efficient AP upgrade feature to
reduce traffic between the controller and the AP (main site and the branch).
-
Do not power
down the controller or any access point during the upgrade process; otherwise,
you might corrupt the software image. Upgrading a controller with a large
number of access points can take as long as 30 minutes, depending on the size
of your network. However, with the increased number of concurrent access point
upgrades supported, the upgrade time should be significantly reduced. The
access points must remain powered, and the controller must not be reset during
this time.
-
If you want to
downgrade to a previous release, do either of the following:
-
After you
perform these functions on the controller, you must reboot the controller for
the changes to take effect:
-
Enable or
disable link aggregation (LAG)
-
Enable a
feature that is dependent on certificates (such as HTTPS and web
authentication)
-
Add new or
modify existing SNMP v3 users
-
Modify an
existing SNMP v3 engine ID
-
Add a new
license or modify an existing license
-
Increase
the priority for a license
-
The controller
bootloader stores a copy of the active primary image and the backup image. If
the primary image becomes corrupted, you can use the bootloader to boot with
the backup image.
With the
backup image stored before rebooting, be sure to choose
Option 2: Run Backup Image from the boot menu to
boot from the backup image. Then, upgrade with a known working image and reboot
the controller.
-
The recovery
image provides a backup image that can be used if an access point power-cycles
during an image upgrade. The best way to avoid the need for access point
recovery is to prevent an access point from power-cycling during a system
upgrade. If a power-cycle occurs during an upgrade to an oversized access point
image, you can recover the access point using the TFTP recovery procedure.
To recover
the access point using the TFTP recovery procedure, follow these steps:
-
Download
the required recovery image from Cisco.com (c1100-rcvk9w8-mx, c1200-rcvk9w8-mx,
or c1310-rcvk9w8-mx) and install it in the root directory of your TFTP server.
-
Connect
the TFTP server to the same subnet as the target access point and power-cycle
the access point. The access point boots from the TFTP image and then joins the
controller to download the oversized access point image and complete the
upgrade procedure.
-
After the
access point has been recovered, you can remove the TFTP server.
-
You can upgrade
to a new release of the controller software or downgrade to an older release
even if Federal Information Processing Standard (FIPS) is enabled.
-
If you upgrade
from a release that is prior to Release 7.5 directly to Release 7.6.X or a
later release, the predownload process on Cisco AP2600 and AP3600 fails. After
the Cisco WLC is upgraded to Release 7.6.X or a later release, the new image is
loaded on Cisco AP2600 and AP3600. After the upgrade to a Release 7.6.X image,
the predownload functionality works as expected. The predownload failure is
only a one-time failure.