Maintaining Wireless Networks

WLC Upgrading
Prior to upgrading or downgrading the software on a controller it is important to know the current version and the hardware platform. The platform will enable you to find the correct software version for your particular controller as the software is not generic across hardware platforms.

WLC Software changes

WLC Upgrading
To find the current software version: Look in the SUMMARY page under the MONITOR menu from the web interface From the CLI use the show sysinfo command. To find the specific hardware platform: Look in the INVENTORY page of the CONTROLLER menu from the web interface From the CLI use the show inventory command
WLC Software changes

WLC Upgrading
The WLC can be upgraded via three different methods: 1. Using the Web Interface 2. Using the CLI 3. Using WCS All three methods need the same information and the same set of files. They are just different interfaces that perform a single function.
WLC Software changes

WLC Upgrading
The WLC needs to have two files installed to complete the upgrade.
unless you have a 2100 series, they only have a single file.

The each of the files are a compressed and encrypted archive. (aes extension is used) The Image Archive The Boot Loader

WLC Software changes

WLC Upgrading
The WLC Image Archive file contains:
The Real-Time Operating system (RTO). Shell Scripts and Java Aps to run the CLI and Web Interface. AP firmware code

The Naming format for the image archive is:

AIR-WLCxxxx-[version].aes Where xxx is the hardware platform the image is designated for. Example: AIR-WLC4400-K9-5-2-178-0.aes
The WLC needs to have two files installed to complete the upgrade.

WLC Upgrading
The WLC bootloader file contains:
Boot strap coding for the controller to start the operating system.

The Naming format for the bootloader archive is:

AIR-WLCxxxx-[version]-ER.aes Where xxx is the hardware platform the image is designated for. Example: AIR-WLC4400-K9-5-2-178-0-ER.aes

The WLC needs to have two files installed to complete the upgrade.

WLC Upgrading
The WLC boot loader file. The bootloader is only needed on versions after 4.1
Prior to 4.1 the boot loader was included in the Image archive.

The 2100 Series WLC, you cannot upgrade the bootloader version due to hardware limitations. Software upgrades for the 2100 do not require a bootloader upgrade.
The WLC needs to have two files installed to complete the upgrade.

WLC Upgrading
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. The release notes for the Wireless LAN controller software can provide information on the upgrade path specific to a software release.

The WLC needs to have two files installed to complete the upgrade.

WLC Upgrading
To get the software into the controller a TFTP server is needed. If you are not using the WCS, you will need a 3rd party TFTP server accessible by the controller.
WCS has a build in tftp service that is used when you upgrade a controller via that application.

The newer controller software releases are greater than 32 MB in size, so you must make sure that your TFTP server supports files larger than 32 MB.

The WLC needs to have two files installed to complete the upgrade.

WLC Upgrading Web interface

Upgrading the WLC with use of the Web interface, requires an HTTPS (or http) connection. Remember that HTTP(s) requires an IP connection to operate. During the upgrade process you will lose Layer 3 connectivity when the controller reboots. Cisco recommended that you have a console port connection available to check the state of the controller during the upgrade, incase you need to instigate any recovery processes.
WLC Upgrading Web interface

WLC Upgrading Web interface

After you log into the web interface you can check the current software version running on your WLC under the Controller Summary page.

WLC Upgrading Web interface

WLC Upgrading Web interface

Click Commands in the menu at the top of the window. The Download File to Controller window appears. Enter the download parameters:
TFTP server IP Address File Path Maximum retries Timeout File Name

WLC Upgrading Web interface

WLC Upgrading Web interface

Click Commands in the menu at the top of the window. The Download File to Controller window appears. Be sure the file type is set to CODE. Enter the download parameters:
TFTP server IP Address File Path Maximum retries Timeout File Name

For the File Path, you can insert a dot (.) as long as the image is in the root directory of your TFTP server.

WLC Upgrading Web interface

WLC Upgrading Web interface

Reboot the system after the file transfer is complete in order for the new software to take effect

WLC Upgrading Web interface

WLC Upgrading CLI

To upgrade the controller via the CLI you first need to specify the transfer parameters.
transfer download datatype code
To define the type of file being downloaded.

transfer download mode tftp

To define the mode of file transfer.

transfer download serverip TFTP_server_IP_address

To define the TFTP server IP address.

transfer download path TFTP_server_path

To define the path of the TFTP default directory where the controller software is located.

transfer download filename filename

To specify the name of the image WLC Upgrading CLI

WLC Upgrading CLI

(Cisco Controller) >transfer download datatype code (Cisco Controller) >transfer download mode tftp (Cisco Controller) >transfer download serverip 10.77.244.196 (Cisco Controller) >transfer download path . (Cisco Controller) >transfer download filename AIRWLC4400-K9-5-2-178-0.aes

WLC Upgrading CLI transfer parameters

WLC Upgrading CLI

Once the parameters have been defined, the next step is to start the process to download the archive to the controller. (Cisco Controller) >transfer download start When the transfer completes, you will have the new archive stored on the WLC, but the WLC still needs to extract the archive and replace the system files. This is done automatically when the WLC boots. The last step is to reboot the controller (Cisco Controller) >reset system

WLC Upgrading CLI transfer parameters

WLC Upgrading
When you upgrade the controller's software, the software on the controller's associated access points is also automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession. Up to 10 access points can be concurrently upgraded from the controller. Do not power down the controller or any access point during this process; otherwise, you might corrupt the software image.
WLC Upgrading

WLC Upgrading
When you upgrade the controller to an intermediate software release, and need to perform another upgrade to attain the desired software version be sure to wait until all the access points joined to the controller are upgraded to the intermediate release before you install the next release of the software. Upgrading the WLC before all the APs have managed to synchronize their versions with the intermediate release, may cause some APs to not be able to download the next release and become orphaned from the WLC.

WLC Upgrading

Configuration Files
Configuration files are stored in NVRAM and are executed when the controller boots. To save configuration files you can issue the CLI command (Cisco Controller) >save config When you want to save the configuration to a backup server, you need to upload the file from the WLC perspective.

WLC configuration files

Configuration Files
Configuration files are stored in NVRAM and are executed when the controller boots. To save configuration files you can issue the CLI command (Cisco Controller) >save config When you want to save the configuration to a backup server, you need to upload the file from the WLC perspective. The configuration files on a WLC are in XLM format, not text.
WLC configuration files

Configuration Files
Configuration files, prior to release 5.2, were transferred from the controller to the server in native (XLM) format. The XLM files have a file integrity check attached to them. If you make any changes to the XLM file the integrity of the file is compromised.
When the controller boots it will do a CRC check on the file that is saved in NVRAM. If the CRC check fails, it will not load the configuration file, and set all parameters back to default values.

WLC configuration files

Configuration Files
Configuration from 5.2 onwards are still stored on the controllers in XLM format. However, when you upload the configuration files to a TFTP or FTP server, software versions from 5.2 onwards will convert the XML file to TEXT prior to the transfer. This will result in a plain text file that you can read and edit. When the plain text file is edited and then downloaded to the controller, the download process will convert the text file into an XML file with a correct CRC before storing it in NVRAM.

WLC configuration files

Uploading Configuration Files

Uploading a configuration file to a server requires the same steps as upgrading the operating system software. 1. Set the upload parameters 2. Initiate the upload

WLC configuration files

Uploading Configuration Files

transfer upload mode tftp
you can also use ftp for config files

transfer upload datatype config transfer upload serverip x.x.x.x transfer upload filename name-of-file

Uploading Configuration Files

Uploading Configuration Files

You can also enable encryption of your configuration files prior to transmission: transfer encrypt enable transfer encrypt set-key key Once parameters are defined, you need to start the upload of the file. transfer upload

Uploading Configuration Files

Downloading Configuration Files

Downloading a configuration file from the server to the controller is the same process as uploading, except you need to reset the system to have the new configuration be implemented. The new configuration is transferred to NVRAM, but it is not executed.

Downloading Configuration Files

Downloading Configuration Files

The controller does not support incremental configuration downloads. The configuration file must contain all mandatory commands. The download process replaces the old configuration file with the one transferred.

Downloading Configuration Files

Downloading Configuration Files

transfer download mode {tftp | ftp} transfer download datatype config transfer download serverip server-ip-address transfer download path server-path-to-file transfer download filename filename If you enabled encryption on the upload: transfer encrypt enable transfer encrypt set-key key
Downloading Configuration Files

Downloading Configuration Files

Once the parameters for the download are completed, you need to start the download process. transfer download start When the file has been successfully downloaded to the controller, the controller needs to be reset in order for the configuration to be executed. reset system

Downloading Configuration Files