![]() |
Table Of Contents
Release Notes for Wireless LAN Controller Field Upgrade Software for Release 1.9.0.0
Downloading Field Upgrade Software
Installing Field Upgrade Software (CLI)
Obtaining Documentation and Submitting a Service Request
Release Notes for Wireless LAN Controller Field Upgrade Software for Release 1.9.0.0
First Published: January 2014OL-31390-01Contents
These release notes contain the following topics:
•
Installing Field Upgrade Software (CLI)
Introduction
Cisco Wireless LAN Controller (WLC) Field Upgrade Software (FUS) is a special AES package that performs various system-related component upgrades. We recommend that you install the FUS image to upgrade components such as the bootloader, field recovery image, FPGA/MCU, and other firmware to their latest respective versions.
Table 1 lists the components that are upgraded after you install Field Upgrade Software for various controller platforms.
Guidelines and Limitations
CautionEnsure that there are no power outages during the upgrade. Power outages during the upgrade may lead to the controller not being usable.
•
This release of the Field Upgrade Software is applicable to Cisco WLCs that are installed with the controller software release 6.0 and later.
•
You must install the FUS image only once.
•
Console access to the WLC during the upgrade process is not required. However it is recommended that you have console access so that you can monitor the progress of the process.
•
The FUS upgrade process reboots the Cisco WLC several times, and reboot the default runtime image. The whole process takes approximately 30 minutes.
•
After you install the FUS image for a Cisco Flex 7500 Controller platform, the RAID firmware is also upgraded. During the installation process, the console messages displayed do indicate upgrade of the RAID firmware. However, it is not possible to verify the RAID firmware upgrade either by entering a command or viewing the bootlog.
Supported Hardware
The FUS image is applicable only to the following controller platforms in this release:
–
Cisco 2500 Series Wireless LAN Controller
–
Cisco 5500 Series Wireless LAN Controller
–
Cisco Flex 7500 Series Wireless LAN Controller
–
Cisco Wireless Services Module 2 (WiSM2)
Downloading Field Upgrade Software
Step 1
Go to the Cisco Software Center at this URL: http://www.cisco.com/cisco/software/navigator.html
Step 2
Choose Products > Wireless > Wireless LAN Controller.
Step 3
Choose either of the following depending on the controller platform you use:
•
Integrated Controllers and Controller Modules
•
Standalone Controllers
Step 4
Choose the controller model number or name. The Download Software page is displayed.
Step 5
Choose Wireless LAN Controller Software.
Step 6
Click a controller software release. The software releases are labeled as follows to help you determine which release to download:
•
Early Deployment (ED)—These software releases provide new features and new hardware platform support as well as bug fixes.
•
Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software maintenance.
•
Deferred (DF)—These software releases have been deferred. We recommend that you migrate to an upgraded release.
Step 7
Click a software release number. Click the filename (for example, AIR-CT5500-K9-1-9-0-0-FUS.aes). The following AES files are available for various controller platforms:
–
AIR-CT5500-K9-1-9-0-0-FUS.aes
–
AIR-CT5500-LDPE-1-9-0-0-FUS.aes
–
AIR-CT7500-K9-1-9-0-0--FUS.aes
–
AIR-WISM2-K9-1-9-0-0-FUS.aes
–
AIR-CT2500-K9-1-9-0-0-FUS.aes
Step 8
Click Download.
Step 9
Read Cisco's End User Software License Agreement and then click Agree.
Step 10
Save the file to your hard drive.
Step 11
Copy the AES file (for example AIR-CT5500-K9-1-9-0-0-FUS.aes) to the default directory on your TFTP or FTP server.
Installing Field Upgrade Software (CLI)
Step 1
Enter the following commands on the Cisco WLC CLI:
a.
transfer download datatype code
b.
transfer download serverip serverip
c.
transfer download mode {tftp | ftp}
d.
transfer download username user
e.
transfer download password password
f.
transfer download filename filename.aes
g.
transfer download path /
h.
transfer download start
Step 2
Enter the following command to reboot the Cisco WLC:
reset system
Information similar to the following is displayed; this is a sample output from a Cisco Flex 7500 Series WLC:
The system has unsaved changes.Would you like to save them now? (y/N) yConfiguration Saved!System will now restart!Updating license storage ... Done.SoftDog: Unexpected close, not stopping watchdog!umount: /mnt/wlc: device is busyumount: /mnt/wlc: device is busyplease save console output below and send to DEUSER PID ACCESS COMMAND/mnt/wlc: root 3651 f.c.. licensedINIT:INIT: Sending processes the TERM signalStopping portmap daemon....Sending all processes the TERM signal... done.Sending all processes the KILL signal... done.Stopping hotplug subsystem:pcipci [success]usbusb [success]isapnpisapnp [success]ideide [success]inputinput [success]scsiscsi [success]done.Starting reboot command: rebootRebooting...Restarting system.[0m[37m[40m[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[23;01HConnecting Boot Devices and Adapters.[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550 M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters..[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters...[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters....[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters.....[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters......[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters.......[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters........[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters.........[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters..........[0m[30m[40m[1m[37m[40m[02;01HPlatform Initalization Complete[0m[37m[40m[04;01HSystem x3550M3UEFI Build Ver: 1.11 IMM Build Ver: 1.25 Diagnostics Build Ver: 9.27[08;01H2 CPUPackages Available at 5.86GT/s Link Speed[09;01H12288MB Memory Available at 1067MHz inIndependent Channel Mode[23;01HConnecting Boot Devices and Adapters...........[23;01H [2J[01;01H[2J[01;01HStart boot option[19;01H<F1> Setup[19;21H<F2>Diagnostics[19;41H<F12> Select Boot Device[1m[37m[40m[2J[01;01H[2J[01;01HBoot Failed.CD/DVD RomBoot Failed. Floppy Disk[2J[01;01H[=3h[2J[01;01H[2J[01;01H[0m[37m[40m[2J[01;01H[00m[40m[37m[2J[01;01HPlease wait,initializing legacy usb devices...Done[02;01H[02;01H[02;01H[03;01H[03;01H[04;01HBroadcom[04;10HNetXtreme[04;20HII[04;23HEthernet[04;32HBoot[04;37HAgent[04;43Hv5.2. 7[04;01H[05;01HCopyright[05;11H(C)[05;15H2000-2009[05;25HBroadcom[05;34HCorporation[05;01H[06;01HAll[06;05Hrights[06;12Hreserved.[06;01H[07;01H[07;01H[08;01H[08;01H[09;01HBroadcom[09;10HNetXtreme[09;20HII[09;23HEthernet[09;32HBoot[09;37HAgent[09;43Hv5.2. 7[09;01H[10;01HCopyright[10;11H(C)[10;15H2000-2009[10;25HBroadcom[10;34HCorporation[10;01H[11;01HAll[11;05Hrights[11;12Hreserved.[11;01H[12;01H[12;01H[13;01HLSI[13;05HMegaRAID[13;14HSAS-MFI[13;22HBIOS[13;01H[14;01HVersion[14;09H4.24.00[14;17H(Build[14;24HMarch[14;30H03,[14;34H2011)[14;01H[15;01HCopyright(c)[15;14H2011[15;19HLSI[15;23HCorporation[15;01H[16;01H[16;01H[17;01HHA[17;04H-0[17;07H(Bus[17;12H1[17;14HDev[17;18H0)[17;21HServeRAID[17;31HM1015[17;37 HSAS/SATA[17;46HController[17;01H[18;01H[18;80H[18;01H[18;01H[19;01H0[19;03HJBOD(s)[19;11Hfound[19;17Hon[19;20Hthe[19;24Hhost[19;29Hadapter[19;01H[20;01H0[20;03HJBOD(s)[20;11Hhandled[20;19Hby[20;22HBIOS[20;01H[21;01H[21;01H[22;01H1[22;03HVirtual[22;11HDrive(s)[22;20Hfound[22;26Hon[22;29Hthe[22;33Hhost[22;38Hadap ter.[22;01H[23;01H[23;01H[24;01H[24;80H[24;01H1[24;03HVirtual[24;11HDrive(s)[24;20Hhandled[24;28Hby[24;31HBIOS[24;01H[25;01H[25;80H[25;01HPress[25;07H<Ctrl><H>[25;17Hfor[25;21HWebBIOS[25;29Hor[25;32Hpress[25;38H<Ctrl><Y>[25;48Hfor[25;52HPreboot[25;60HCLI[25;64H[25;01H [25;02H [25;03H [25;04H [25;05H [25;07H [25;08H [25;09H [25;10H [25;11H [25;12H[25;13H [25;14H [25;15H [25;17H [25;18H [25;19H [25;21H [25;22H [25;23H [25;24H [25;25H[25;26H [25;27H [25;29H [25;30H [25;32H [25;33H [25;34H [25;35H [25;36H [25;38H [25;39H[25;40H [25;41H [25;42H [25;43H [25;44H [25;45H [25;46H [25;48H [25;49H [25;50H [25;52H[25;53H [25;54H [25;55H [25;56H [25;57H [25;58H [25;60H [25;61H [25;62H [25;80H[25;01H[25;01H[2J[01;01HCisco Bootloader (Version 7.6.101.2).o88b. d888888b .d8888. .o88b. .d88b.d8P Y8 `88' 88' YP d8P Y8 .8P Y8.8P 88 `8bo. 8P 88 888b 88 `Y8b. 8b 88 88Y8b d8 .88. db 8D Y8b d8 `8b d8'`Y88P' Y888888P `8888Y' `Y88P' `Y88P'Booting Primary Image...Press <ESC> now for additional boot options...Booting 'Primary image'Detecting hardware . . . . 3INIT: version 2.86 bootingStarting the hotplug events dispatcher: udevd.Synthesizing the initial hotplug events...done.Waiting for /dev to be fully populated...done.Activating swap...done.Remounting root filesystem...done.Mounting local filesystems: mount none on /var/run type tmpfs (rw)none on /tmp type tmpfs (rw)Setting up networking ....Starting hotplug subsystem:pcipci [success]usbusb [success]isapnpisapnp [success]ideide [success]inputinput [success]scsiscsi [success]done.Starting portmap daemon....Octeon Found...Detecting Hardware ...Booting Octeon...Using user supplied board name: nic_xle_10gAll cores in reset, skipping soft reset.Using bootloader image: /octeon/u-boot-octeon_nic_xle_10g_pciboot.binInitialized 2048 MBytes of DRAMINIT: Entering runlevel: 3Total DIMMs are: 3Cryptographic library self-test....passed!XML config selectedValidating XML configurationRead HA Config before validationocteon_device_init: found 1 DPsCisco is a trademark of Cisco Systems, Inc.Software Copyright Cisco Systems, Inc. All rights reserved.Cisco AireOS Version 7.6.101.2Initializing OS Services: okInitializing Serial Services: okInitializing Network Services: okInitializing Licensing Services: okLicense daemon start initialization.....License daemon running.....Starting Statistics Service: okStarting ARP Services: okStarting Trap Manager: okStarting Network Interface Management Services: okStarting System Services: okStarting FIPS Features: ok : Not enabledStarting Fastpath Hardware Acceleration: okokStarting Fastpath DP Heartbeat : okFastpath CPU0.00: Starting Fastpath Application. SDK-1.8.1, build 294. Flags-[DUTY CYCLE]: okFastpath CPU0.00: Initializing last packet received queue. Num of cores(12)Fastpath CPU0.00: Init MBUF size: 1856, Subsequent MBUF size: 2040Fastpath CPU0.00: Core 0 Initialization: okFastpath CPU0.00: Initializing Timer...Fastpath CPU0.00: Initializing Timer...done.Fastpath CPU0.00: Initializing Timer...Fastpath CPU0.00: Initializing NBAR AGING Timer...done.Fastpath CPU0.01: Core 1 Initialization: okFastpath CPU0.02: Core 2 Initialization: okFastpath CPU0.03: Core 3 Initialization: okFastpath CPU0.00: Received instruction to get link statusFastpath CPU0.04: Core 4 Initialization: okFastpath CPU0.05: Core 5 Initialization: okFastpath CPU0.06: Core 6 Initialization: okFastpath CPU0.07: Core 7 Initialization: okFastpath CPU0.08: Core 8 Initialization: okFastpath CPU0.09: Core 9 Initialization: okFastpath CPU0.10: Core 10 Initialization: okFastpath CPU0.11: Core 11 Initialization: okStarting Switching Services: okStarting QoS Services: okStarting Policy Manager: okStarting Data Transport Link Layer: okStarting Access Control List Services: okStarting System Interfaces: okStarting Client Troubleshooting Service: okStarting Management Frame Protection: okStarting Certificate Database: okStarting VPN Services: okStarting DNS Services: okHBL initialization is successfulStarting Licensing Services: okStarting Redundancy: okStarting LWAPP: okStarting CAPWAP: okStarting LOCP: okStarting Security Services: okStarting Policy Manager: okStarting Authentication Engine: okStarting Mobility Management: okStarting Capwap Ping Component: okStarting AVC Services: okStarting Virtual AP Services: okStarting AireWave Director: okStarting Network Time Services: okStarting Cisco Discovery Protocol: okStarting Broadcast Services: okStarting Logging Services: okStarting DHCP Server: okStarting IDS Signature Manager: okStarting RFID Tag Tracking: okStarting RF Profiles: okStarting Environment Status Monitoring Service: okStarting RAID Volume Status Monitoring Service: okStarting Mesh Services: okStarting TSM: okStarting CIDS Services: okStarting Ethernet-over-IP: okStarting DTLS server: enabled in CAPWAPStarting CleanAir: okStarting WIPS: okStarting SSHPM LSC PROV LIST: okStarting RRC Services: okStarting SXP Services: okStarting Alarm Services: okStarting FMC HS: okStarting IPv6 Services: okStarting Config Sync Manager : okStarting Hotspot Services: okStarting Portal Server Services: okStarting mDNS Services: okStarting Management Services:Web Server: CLI: Secure Web: ok
Upgrading FUS Image
Step 1
Upload your controller configuration files to a server to back them up.
Step 2
Get the controller software image as defined in Downloading Field Upgrade Software, and follow these steps:
a.
Choose Wireless > Wireless LAN Controller. The following options are available: Integrated Controllers and Controller Modules and Standalone Controllers.
b.
Depending on your controller platform, click one of the above options.
c.
Click the controller model number or name. The Download Software page is displayed.
d.
Click a controller software release. The software releases are labeled as follows to help you determine which release to download:
–
Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bug fixes.
–
Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software maintenance.
–
Deferred (DF)—These software releases have been deferred. We recommend that you migrate to an upgraded release.
e.
Choose a software release number.
f.
Click the filename (for example, AIR-CT5500-K9-1-9-0-0-FUS.aes).
g.
Click Download.
h.
Read Cisco's End User Software License Agreement and then click Agree.
i.
Save the file to your hard drive.
j.
Repeat steps a through k to download the remaining file.
Step 3
Copy the controller software image (filename.aes) to the default directory on your TFTP or FTP server.
Step 4
(Optional) Disable the 802.11 networks.
Note
For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disable the 802.11 networks as a precautionary measure.
Step 5
Disable any WLANs on the controller.
Step 6
Choose Commands > Download File to open the Download File to Controller page.
Step 7
From the File Type drop-down list, choose Code.
Step 8
From the Transfer Mode drop-down list, choose from the following options:
•
TFTP
•
FTP
Step 9
In the IP Address text box, enter the IP address of the server.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text boxes should work correctly without any adjustment. However, you can change these values.
Step 10
If you are using a TFTP server, the default values of 10 retries for the Maximum Retries text field, and 6 seconds for the Timeout text field should work correctly without any adjustment. However, you can change these values if desired. To do so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries text box and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeout text box.
Step 11
In the File Path text box, enter the directory path of the software.
Step 12
In the File Name text box, enter the name of the controller software file (for example, AIR-CT5500-K9-1-9-0-0-FUS.aes).
Step 13
If you are using an FTP server, follow these steps:
•
In the Server Login Username text box, enter the username to log into the FTP server.
•
In the Server Login Password text box, enter the password to log into the FTP server.
•
In the Server Port Number text box, enter the port number on the FTP server through which the download occurs. The default value is 21.
Step 14
Click Download to download the software to the controller. A message appears indicating the status of the download.
Step 15
After the download is complete, click Reboot.
Step 16
If prompted to save your changes, click Save and Reboot.
Step 17
Click OK to confirm.
Step 18
After the controller reboots, repeat step 6 to step 17 to install the remaining file.
Step 19
Reenable the WLANs.
Step 20
For Cisco WiSM2, reenable the controller port channel on the Catalyst switch.
Step 21
If you have disabled the 802.11 networks in Step 4, reenable them.
Step 22
To verify the controller software version, choose Monitor on the controller GUI and see Software Version in the Controller Summary area.
Caveats
The following sections lists Open Caveats and Resolved Caveats for Cisco controllers and lightweight access points for version 1.9.0.0. For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•
Commands are in boldface type.
•
Product names and acronyms might be standardized.
•
Spelling errors and typos might be corrected.
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:
https://tools.cisco.com/bugsearch/search
Note
If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.
Open Caveats
Table 2 lists the open caveats in this release.
Resolved Caveats
Table 3 lists the resolved caveats in this release.
Service and Support
Troubleshooting
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website at
http://www.cisco.com/en/US/support/index.html
Click Product Support > Wireless. Then choose your product and Troubleshooting to find information on the problem you are experiencing.
Related Documentation
For additional information on the Cisco controllers and lightweight access points, see these documents:
•
The quick start guide or installation guide for your particular controller or access point
•
Cisco Wireless LAN Controller Configuration Guide
•
Cisco Wireless LAN Controller Command Reference
•
Cisco Prime Network Control System Configuration Guide
•
Cisco Prime Network Control System Command Reference
You can access these documents from this link:
http://www.cisco.com/cisco/web/support/index.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2014 Cisco Systems, Inc. All rights reserved.