You are on page 1of 31

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

– unless you have a 2100 series.WLC Upgrading The WLC needs to have two files installed to complete the upgrade. they only have a single file. (aes extension is used) • The Image Archive • The Boot Loader WLC Software changes . The each of the files are a compressed and encrypted archive.

Example: AIR-WLC4400-K9-5-2-178-0.WLC Upgrading The WLC Image Archive file contains: – – – The Real-Time Operating system (RTO). .aes The WLC needs to have two files installed to complete the upgrade.aes Where xxx is the hardware platform the image is designated for. AP firmware code The Naming format for the image archive is: AIR-WLCxxxx-[version]. Shell Scripts and Java Aps to run the CLI and Web Interface.

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. Example: AIR-WLC4400-K9-5-2-178-0-ER.aes Where xxx is the hardware platform the image is designated for. The Naming format for the bootloader archive is: AIR-WLCxxxx-[version]-ER.

The 2100 Series WLC.WLC Upgrading The WLC boot loader file. . The bootloader is only needed on versions after 4. The WLC needs to have two files installed to complete the upgrade. Software upgrades for the 2100 do not require a bootloader upgrade. you cannot upgrade the bootloader version due to hardware limitations.1 the boot loader was included in the Image archive.1 – Prior to 4.

WLC Upgrading You can upgrade or downgrade the controller software only between certain releases. . In some instances. 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. you must first install an intermediate release prior to upgrading to software release.

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. . The newer controller software releases are greater than 32 MB in size. If you are not using the WCS. – WCS has a build in tftp service that is used when you upgrade a controller via that application. you will need a 3rd party TFTP server accessible by the controller.WLC Upgrading To get the software into the controller a TFTP server is needed.

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

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 .

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

you can insert a dot (. Enter the download parameters: • • • • • TFTP server IP Address File Path Maximum retries Timeout File Name For the File Path. The Download File to Controller window appears.WLC Upgrading – Web interface Click Commands in the menu at the top of the window. Be sure the file type is set to CODE. WLC Upgrading – Web interface .) as long as the image is in the root directory of your TFTP server.

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 .

– 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 . – transfer download serverip TFTP_server_IP_address • To define the TFTP server IP address.WLC Upgrading – CLI To upgrade the controller via the CLI you first need to specify the transfer parameters. – transfer download mode tftp • To define the mode of file transfer. – transfer download datatype code • To define the type of file being downloaded.

WLC Upgrading – CLI (Cisco Controller) >transfer download datatype code (Cisco Controller) >transfer download mode tftp (Cisco Controller) >transfer download serverip 10.77.196 (Cisco Controller) >transfer download path .244.aes WLC Upgrading – CLI transfer parameters . (Cisco Controller) >transfer download filename AIRWLC4400-K9-5-2-178-0.

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

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

WLC Upgrading .WLC Upgrading When you upgrade the controller to an intermediate software release. Upgrading the WLC before all the APs have managed to synchronize their versions with the intermediate 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. may cause some APs to not be able to download the next release and become orphaned from the WLC.

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. WLC configuration files .Configuration Files Configuration files are stored in NVRAM and are executed when the controller boots. you need to upload the file from the WLC perspective.

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. The configuration files on a WLC are in XLM format. you need to upload the file from the WLC perspective.Configuration Files Configuration files are stored in NVRAM and are executed when the controller boots. WLC configuration files . not text.

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

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

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

x transfer upload filename name-of-file Uploading 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.

transfer upload Uploading Configuration Files . you need to start the upload of the file.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.

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

Downloading Configuration Files The controller does not support incremental configuration downloads. The download process replaces the old configuration file with the one transferred. The configuration file must contain all mandatory commands. 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 .

you need to start the download process.Downloading Configuration Files Once the parameters for the download are completed. 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 .