wlc upgrade

Wireless LAN Controller (WLC) Software Upgrade

Document ID: 68835

IntroductionPrerequisites Requirements Components Used ConventionsConfigure GUI Upgrade Procedure CLI Upgrade Procedure Use WCS to Upgrade the WLCVerifyTroubleshootNetPro Discussion Forums − Featured ConversationsRelated Information

Introduction

This document explains the methods that you can use to upgrade the operating system (OS) software on aCisco Wireless LAN Controller (WLC).

Prerequisites

Requirements

Ensure that you meet these requirements before you attempt this configuration:

You know how to configure basic parameters on the WLC.• You have a TFTP server installed and you know how to use it.•

If you are new to WLCs and do not know how to configure the WLC, refer to Cisco Wireless LAN ControllerConfiguration Guide, Release 3.2.

Components Used

The information in this document is based on these software and hardware versions:

Cisco 2006 WLC that runs firmware 3.1.105• PC on the network that runs TFTP server Tftpd32 version 2.0•

The information in this document was created from the devices in a specific lab environment. All of thedevices used in this document started with a cleared (default) configuration. If your network is live, make surethat you understand the potential impact of any command.

Cisco − Wireless LAN Controller (WLC) Software Upgrade

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Configure

You can upgrade the Cisco WLC with either one of these methods:

GUI• Command−line interface (CLI)•

When a controller is upgraded, the code on its associated access points is also automatically upgraded. Whenan access point loads code, each of its lights blinks in succession.

Note: Do not power down the controller or any access point during this process. Otherwise, you might corruptthe software image.

The upgrade of a controller with a large number of access points can take as long as 30 minutes. The accesspoints must remain powered, and the controller must not be reset during this time.

Cisco recommends this sequence when you perform an upgrade:

Upload your controller configuration files to a server to back them up.1. Turn off the controller 802.11a and 802.11b networks.2. Upgrade your controller.3. Re−enable your 802.11a and 802.11b networks.4.

This document provides the steps to follow in order to upgrade the WLC with each of these methods.

GUI Upgrade Procedure

In this section, you are presented with the information to upgrade the WLC with use of the GUI on thecontroller.

Note: When you upgrade the WLC with use of the GUI, you lose your connection to the controller for a fewseconds during the update process. For this reason, Cisco recommends that you use a direct CLI console portconnection in order to update controller software.

Step−by−Step Instructions

Complete these steps:

Complete these steps to log into the WLC through the browser:

Enter the IP address of the controller in the address line and click Login.

You are prompted for user credentials.

a.

Enter the username and password of the controller and click OK.

The default username and password on the WLC is admin.

b.

1.


The Monitor window appears. The Summary information shows you the OS software versionthat currently runs on the WLC.

Complete these steps to define the download parameters:

Click Commands in the menu at the top of the window.

The Download file to Controller window appears.

a.

Enter the download parameters.

The parameters to define include:

TFTP server IP address◊ File path◊ File name◊ Maximum retries◊ Timeout◊

b.

Click Download in order to start the upgrade process.

Here is an example:

c.

2.


Note: When you perform the upgrade from the GUI, for File Path, you can also insert a dot(.) and make sure that the image is in the root directory of your TFTP server. This way, youdo not have to enter the path were the image is saved.

This document explains the upgrade of the WLC software from version 3.1.105.0 to version3.2.78.0. Upgrade the WLC software to the latest release that is available. Refer to theWireless Software Center for the latest version of the WLC software. Copy the downloadedOS software file for the WLC to the default directory on the TFTP server.

Note: You need a valid Cisco.com account in order to download the WLC software.Reboot the system after the file transfer is complete in order for the new software to take effect.

Click Click Here in order to reboot, as this example shows:

3.


In the the System Reboot window, click Reboot at the top right side of the window.4.

Click Save and Reboot in the Reboot System > Save window.5.


After the reboot, you see that the WLC software is upgraded to the latest code. Here is an exampleafter the upgrade process:

Note: The new version is 3.2.78.0.


CLI Upgrade Procedure

In this section, you are presented with the information to upgrade the WLC with use of the CLI on thecontroller.

Step−by−Step Instructions

Complete these steps:

Make sure that the TFTP server is reachable from the controller, and then download the desired OSsoftware file.

Refer to the Wireless Software Center in order to download the software file. Copy the file to thedefault directory on the TFTP server.

1.

Log in to the WLC CLI.2.

Complete these steps in order to define the download parameters:

Issue the transfer download mode tftp command in order to define the mode of file transfer.a. Issue the transfer download serverip TFTP_server_IP_address command in order to definethe TFTP server IP address.

b.

Issue the transfer download path 'TFTP_server_path' command in order to define the pathof the TFTP default directory where the controller OS software is located.

c.

3.


Issue the transfer download filename filename command in order to specify the name of theimage.

Here is an example:

d.

Issue the transfer download start command in order to initiate the upgrade process.

Here is an example of the upgrade process:

4.

Reboot the controller after the upgrade process is complete in order for the new code to take effect.

Issue the reset system command, and enter yor yes in response to the question "Would you like tosave them now?". Here is an example:

5.


Use WCS to Upgrade the WLC

Complete these steps in order to update controller (and access point) software using the Wireless ControlSystem (WCS).

Enter ping ip−address in order to be sure that the WCS server can contact the controller. If you usean external TFTP server, enter ping ip−address in order to be sure that the WCS server can contactthe TFTP server.

1.

Choose Configure > Controllers in order to navigate to the All Controllers page.2. Check the check box of the desired controller, choose Download Software from the Select aCommand drop−down menu, and click Go. WCS displays the Download Software to Controller page.

3.

If you use the built−in WCS TFTP server, check the TFTP Server on WCS System check box. Ifyou use an external TFTP server, uncheck this check box and add the external TFTP server IPaddress.

4.

Click Browse and navigate to the software update file (for example, AS_2000_release.aes for 2000series controllers).

The files are uploaded to the root directory which was configured for use by the TFTP server. Youcan change to a different directory.

5.

Click Download.

WCS downloads the software to the controller, and the controller writes the code to Flash RAM. AsWCS performs this function, it displays its progress in the Status field.

6.

Refer to Performing System Tasks for more information.

Verify

Use this section to confirm that your configuration works properly.

In order to verify the version of WLC software that runs, log in to the WLC after the system reboots.

Here is an example. You can see that the WLC software is upgraded to 3.2.78.0:


Troubleshoot

Use this section to troubleshoot your configuration.

During the upgrade process, you can come across some errors that affect the upgrade process. This sectionexplains what the error messages mean and how to eliminate the errors and upgrade the controller.

Code file transfer failed − No reply from the TFTP server�You get this error message if the TFTPserver is not active. Check to determine if the TFTP service is enabled on the server.

•

Code file transfer failed − Error from server: File was not found. Aborting transfer�You get thiserror message if the OS file is not present in the default directory of the TFTP server. In order toeliminate this error, copy the image file to the default directory on the TFTP server.

•

TFTP Failure while storing in flash!�You can get this error if there is a problem with the TFTPserver. Some TFTP servers have a limitation on the size of the files that you can transfer. Use adifferent TFTP server utility. There are many free TFTP server utilities that are available. Ciscorecommends use of the Tftpd32 version 2.0 TFTP server. Refer to Tftpd32 in order to download thisTFTP server.

•

The install partitions are destroyed or the image is corrupted�If you are still unsuccessful after anattempt to upgrade the software, there is a possibility that your image is corrupted. Contact CiscoTechnical Support for assistance.

•

You can also use the debug transfer trace enable command in order to view the events that occur during thecontroller software upgrade process. Here is an example, which shows the debug command output for asuccessful software upgrade:

(Cisco Controller) >debug transfer trace enable

(Cisco Controller) >transfer download start


Mode............................................. TFTPData Type........................................ CodeTFTP Server IP................................... 172.16.1.1TFTP Packet Timeout.............................. 6TFTP Max Retries................................. 10TFTP Path........................................ d:\WirelessImages/TFTP Filename.................................... AIR−WLC2006−K9−3−2−78−0.aes

This may take some time.Are you sure you want to start? (y/n) yMon Feb 13 14:06:56 2006: RESULT_STRING: TFTP Code transfer starting.Mon Feb 13 14:06:56 2006: RESULT_CODE:1

TFTP Code transfer starting.Mon Feb 13 14:06:59 2006: Still waiting! Status = 2Mon Feb 13 14:07:00 2006: Locking tftp semaphore, pHost=172.16.1.1 pFilename=d:\WirelessImages/AIR−WLC2006−K9−3−2−78−0.aesMon Feb 13 14:07:00 2006: Semaphore locked, now unlocking, pHost=172.16.1.1 pFilename=d:\WirelessImages/AIR−WLC2006−K9−3−2−78−0.aesMon Feb 13 14:07:00 2006: Semaphore successfully unlocked, pHost=172.16.1.1 pFilename=d:\WirelessImages/AIR−WLC2006−K9−3−2−78−0.aesMon Feb 13 14:07:02 2006: Still waiting! Status = 1Mon Feb 13 14:07:05 2006: Still waiting! Status = 1Mon Feb 13 14:07:08 2006: Still waiting! Status = 1Mon Feb 13 14:07:11 2006: Still waiting! Status = 1Mon Feb 13 14:07:14 2006: Still waiting! Status = 1Mon Feb 13 14:07:17 2006: Still waiting! Status = 1Mon Feb 13 14:07:19 2006: tftp rc=0, pHost=172.16.1.1 pFilename=d:\WirelessImages/AIR−WLC2006−K9−3−2−78−0.aes pLocalFilename=/mnt/download/local.tgzMon Feb 13 14:07:19 2006: tftp = 6, file_name=d:\WirelessImages/AIR−WLC2006−K9−3−2−78−0.aes, ip_address=172.16.1.1Mon Feb 13 14:07:19 2006: upd_get_code_via_tftp = 6 (target=268435457)Mon Feb 13 14:07:19 2006: RESULT_STRING: TFTP receive complete... extracting components.Mon Feb 13 14:07:19 2006: RESULT_CODE:6

TFTP receive complete... extracting components.Mon Feb 13 14:07:20 2006: Still waiting! Status = 2Mon Feb 13 14:07:23 2006: Still waiting! Status = 1Mon Feb 13 14:07:23 2006: Still waiting! Status = 1Mon Feb 13 14:07:23 2006: Still waiting! Status = 1Mon Feb 13 14:07:25 2006: RESULT_STRING: Executing init script.Mon Feb 13 14:07:25 2006: RESULT_STRING: Executing backup script.

Executing backup script.Mon Feb 13 14:07:26 2006: Still waiting! Status = 2Mon Feb 13 14:07:29 2006: Still waiting! Status = 1Mon Feb 13 14:07:31 2006: RESULT_STRING: Writing new bootloader to flash disk.

Writing new bootloader to flash disk.Mon Feb 13 14:07:32 2006: Still waiting! Status = 2Mon Feb 13 14:07:33 2006: RESULT_STRING: Executing install_bootloader script.

Executing install_bootloader script.Mon Feb 13 14:07:35 2006: Still waiting! Status = 2Mon Feb 13 14:07:35 2006: RESULT_STRING: Writing new RTOS to flash disk.Mon Feb 13 14:07:36 2006: RESULT_STRING: Executing install_rtos script.Mon Feb 13 14:07:36 2006: RESULT_STRING: Writing new Code to flash disk.

Writing new Code to flash disk.Mon Feb 13 14:07:38 2006: Still waiting! Status = 2Mon Feb 13 14:07:41 2006: Still waiting! Status = 1


Mon Feb 13 14:07:42 2006: RESULT_STRING: Executing install_code script.

Executing install_code script.Mon Feb 13 14:07:44 2006: Still waiting! Status = 2Mon Feb 13 14:07:47 2006: Still waiting! Status = 1Mon Feb 13 14:07:48 2006: RESULT_STRING: Writing new APIB to flash disk.

Writing new APIB to flash disk.Mon Feb 13 14:07:50 2006: Still waiting! Status = 2Mon Feb 13 14:07:51 2006: RESULT_STRING: Executing install_apib script.

Executing install_apib script.Mon Feb 13 14:07:53 2006: Still waiting! Status = 2Mon Feb 13 14:07:53 2006: Still waiting! Status = 1Mon Feb 13 14:07:53 2006: Still waiting! Status = 1Mon Feb 13 14:07:53 2006: Still waiting! Status = 1Mon Feb 13 14:07:53 2006: Still waiting! Status = 1Mon Feb 13 14:07:54 2006: RESULT_STRING: Writing new APIB to flash disk.Mon Feb 13 14:07:56 2006: RESULT_STRING: Executing install_apib script.

Executing install_apib script.Mon Feb 13 14:07:56 2006: Still waiting! Status = 2Mon Feb 13 14:07:59 2006: RESULT_STRING: Writing new APIB to flash disk.

Writing new APIB to flash disk.Mon Feb 13 14:08:00 2006: Still waiting! Status = 2Mon Feb 13 14:08:00 2006: RESULT_STRING: Executing install_apib script.

Executing install_apib script.Mon Feb 13 14:08:03 2006: Still waiting! Status = 2Mon Feb 13 14:08:03 2006: RESULT_STRING: Writing new Cert−patch to flash disk.Mon Feb 13 14:08:03 2006: RESULT_STRING: Executing install_cert_patch script.Mon Feb 13 14:08:03 2006: RESULT_STRING: Executing fini script.Mon Feb 13 14:08:04 2006: RESULT_STRING: TFTP File transfer is successful. Reboot the switch for update to complete.Mon Feb 13 14:08:04 2006: RESULT_CODE:11

TFTP File transfer is successful. Reboot the switch for update to complete.

Mon Feb 13 14:08:06 2006: Still waiting! Status = 2Mon Feb 13 14:08:08 2006: ummounting: <umount /mnt/download/> cwd = /mnt/applicationMon Feb 13 14:08:08 2006: finished umounting

NetPro Discussion Forums − Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions,and information about networking solutions, products, and technologies. The featured links are some of themost recent conversations available in this technology.

NetPro Discussion Forums − Featured Conversations for Wireless

Wireless − Mobility: WLAN Radio Standards

Wireless − Mobility: Security and Network Management

Wireless − Mobility: Getting Started with Wireless

Wireless − Mobility: General


Related Information

Cisco Wireless LAN Controller Configuration Guide, Release 3.2• Quick Start Guide: Cisco 2000 Series Wireless LAN Controllers• Cisco Wireless LAN Controller Command Reference, Release 3.2• Wireless Support Page• Technical Support & Documentation − Cisco Systems•

All contents are Copyright © 1992−2006 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.

Updated: Oct 01, 2006 Document ID: 68835


wlc upgrade

Documents

wireless wireless mobility

executing install code script

executing install apib script

executing install bootloader script

wireless software center

enter ping ipaddress

stepbystep instructions complete

external tftp server