Chapter 19sdfg

8/13/2019 Chapter 19sdfg

1/31


2/31

WLC Upgrading

Prior to upgrading or downgrading thesoftware on a controller it is important toknow the current version and thehardware platform.

The platform will enable you to find thecorrect software version for your particularcontroller as the software is not genericacross hardware platforms.

WLC Software changes


3/31

WLC Upgrading

To find the current software version: Look in the SUMMARYpage under the

MONITORmenu from the web interface

From the CLI use the show sysinfocommand.

To find the specific hardware platform:

Look in the INVENTORYpage of theCONTROLLERmenu from the web interface

From the CLI use the show inventorycommand



4/31

WLC Upgrading

The WLC can be upgraded via three differentmethods:

1. Using the Web Interface

2. Using the CLI

3. Using WCS

All three methods need the same information andthe same set of files.

They are just different interfaces that perform asingle function.



5/31

WLC Upgrading

The WLC needs to have two filesinstalled to complete the upgrade.

unless you have a 2100 series, they only have asingle file.

The each of the files are a compressed andencrypted archive. (aes extension is used)

The Image Archive

The Boot Loader



6/31

WLC Upgrading

The WLC Image Archive file contains:

The Real-Time Operating system (RTO).

Shell Scripts and Java Aps to run the CLI and WebInterface.

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.


7/31

WLC Upgrading

The WLC bootloader file contains:

Boot strap coding for the controller to start theoperating system.

The Naming format for the bootloader archive is:

AIR-WLCxxxx-[vers ion]-ER.aes

Where xxx is the hardware platform the image is designated for.

Example: AIR-WLC4400-K9-5-2-178-0-ER.aes



8/31


9/31

WLC Upgrading

You can upgrade or downgrade the controller

software only between certain releases.

In some instances, you must first install anintermediate release prior to upgrading to

software release.

The release notes for the Wireless LANcontroller software can provide information on

the upgrade path specific to a software release.



10/31

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 3rdparty 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 aregreater than 32 MB in size, so you must makesure that your TFTP server supports files larger

than 32 MB.



11/31

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 IPconnection to operate.

During the upgrade process you will lose Layer 3connectivity when the controller reboots.

Cisco recommended that you have a console portconnection available to check the state of the

controller during the upgrade, incase you need toinstigate any recovery processes.



12/31


After you log into the web interface you can

check the current software version running onyour WLC under the Controller Summary page.



13/31

WLC Upgrading Web interfaceClick Commandsin 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



14/31

WLC Upgrading Web interfaceClick Commandsin 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 theroot directory of your TFTP server.



15/31


Reboot the system after the file transfer is complete in order

for the new software to take effect



16/31

WLC Upgrading CLITo 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 fi lename filename To specify the name of the image

WLC Upgrading CLI


17/31

WLC Upgrading CLI

(Cisco Controller) >transfer download datatype code

(Cisco Controller) >transfer download mode tftp

(Cisco Controller) >transfer download serverip10.77.244.196

(Cisco Controller) >transfer download path .

(Cisco Controller) >transfer download filename AIR-WLC4400-K9-5-2-178-0.aes

WLC Upgrading CLI transfer parameters


18/31

WLC Upgrading CLI

Once the parameters have been defined, the next step is tostart 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 thearchive 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


19/31

WLC Upgrading

When you upgrade the controller's software, the software on

the controller's associated access points is alsoautomatically upgraded.

When an access point is loading software, each of its LEDsblinks in succession.

Up to 10 access points can be concurrently upgraded fromthe controller.

Do not power down the controller or any access point

during this process; otherwise, you might corrupt thesoftware image.

WLC Upgrading


20/31

WLC Upgrading

When you upgrade the controller to an intermediate software

release, and need to perform another upgrade to attain thedesired software version be sure to wait until all the accesspoints joined to the controller are upgraded to theintermediate release before you install the next release ofthe software.

Upgrading the WLC before all the APs have managed tosynchronize their versions with the intermediate release,may cause some APs to not be able to download the nextrelease and become orphaned from the WLC.

WLC Upgrading


21/31

Configuration Files

Configuration files are stored in NVRAM and are executedwhen 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


22/31

Configuration Files

Configuration files are stored in NVRAM and are executedwhen the controller boots.

To save configuration files you can issue the CLIcommand

(Cisco Controller) >save config

When you want to save the configuration to a backupserver, you need to upload the file from the WLCperspective.

The configuration files on a WLC are in XLM format, nottext.



23/31

Configuration Files

Configuration files, prior to release 5.2, were transferredfrom 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 thatis saved in NVRAM. If the CRC check fails, it will not load theconfiguration file, and set all parameters back to default values.



24/31

Configuration Files

Configuration from 5.2 onwards are still stored on thecontrollers in XLM format.

However, when you upload the configuration files to a TFTPor FTP server, software versions from 5.2 onwards willconvert 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 tothe controller, the download process will convert the text file

into an XML file with a correct CRC before storing it inNVRAM.



25/31


26/31

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



27/31


You can also enable encryption of yourconfiguration files prior to transmission:

transfer encrypt enable

transfer encrypt set-key key

Once parameters are defined, you need tostart the upload of the file.

transfer upload



28/31


29/31


30/31


31/31

Downloading Configuration Files

Once the parameters for the download are

completed, you need to start the downloadprocess.

transfer download start

When the file has been successfully downloadedto the controller, the controller needs to be resetin order for the configuration to be executed.

reset system

Downloading Configuration Files

Chapter 19sdfg

Documents

Transcript of Chapter 19sdfg