WLC 5508 FUS+Software upgrade

Hello,
I have 2 controllers 5508 (7.0.98.0) and i want to upgrade to version 7.4.110.0.
What is the recommended sequence for software upgrade and FUS ugrade to 1.7.0.0?
First to upgrade the FUS,reload the controller and then the upgrade the software or the opposite?
Is possible to download both files and reboot the controllers later?
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.98.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... N/A
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... WLC-5508-A
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Thanks.

"Field Upgrade Software (FUS) is a special AES package that contains several system related component upgrades. These include the bootloader, field recovery image, and FPGA/MCU firmware. Installing the FUS image requires special attention because it installs some critical firmware. The FUS image is independent of the runtime image"
Yes, this is highly recomended to do this upgrade. Otherwise you may have wired issues of APs are not working as expected.
Here is a document explain this process
https://supportforums.cisco.com/docs/DOC-23757
Here are some reference post FUS upgrades helped
https://supportforums.cisco.com/thread/2250073
https://learningnetwork.cisco.com/thread/63054
HTH
Rasika
*** Pls rate all useful responses ****

Similar Messages

Wlc 5508 fus upgrade to v1.9

Hi folks,
I have a pair of wlc 5508, configured as a HA pair. I want to upgrade the FUS to ver 1.9.
Is it necessary to break the HA pair, and upgrade each wlc individually?

Ref : http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html
>...
The FUS image can be upgraded while the controllers have HA enabled. The secondary controller will get upgraded just like it does when upgrading the regular code. However, when you initiate the reboot on the primary controller both controllers will be unreachable until the FUS upgrade completes on both the active and the standby in the HA pair. This process will take around 30 to 40 minutes to complete just like in a non-HA FUS upgrade.
M.

WLC 5508 Failure to upgrade code

Hi,
I'm trying to upgrade a WLC 5508 and I'm getting the following errors:
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Failure while validating the signature!
TFTP Failure while storing in flash!
The image is good and for the right model. Does anyone have any ideas?

Hello Kayle
both of my controllers are brandnew according to their serial-#: and Leolaohoo's post.
Controller_1 : FCW1522L021
Controller_2 : FCW1522L022
Facts:
=====
1. Both are running code 7.0.98.218
2. Upgrade to 7.0.116.0 (AIR-CT5500-K9-7-0-116-0.aes) failed
Just to be sure, I also tried code AIR-CT5500-LDPE-K9-7-0-116-0.aes, which also failed on both
3. No firewall or antivirus is active on my workstation
4. Upgrade was tried via Service-Port as well as management-interface
5. Upgrade was tried via FTP as well as TFTP
6. Short after file-transfer has been finished I get the corresponding message and even short after that I receive the message "Failure while validating the signature"
7. Doing a "show logging", I get the message that the downloaded file seems to be corrupted (screenshot below), but checking the filesize gives me exactly the same size as on the CCO before downloading

Wlc 5508 inaccessible after upgrade to version 8

dear all,
I have a problem after upgrading wlc 5508,
at first after upgrade everything works fine, but while waiting for APs to rejoin, wlc suddenly inaccessible either via SSH, telnet or console
I have restart the wlc with no luck
LED indicator for SYS and ALR are off
any suggestion will be highly appreciated
thanks
regards

If the appliance failed in the first month after delivery, you might be able to squeeze off an RMA.
If the appliance failed in the first year after delivery, I don't care what is written in the "warranty", you can't do anything until you have a valid Service Contract.

WLC 5508 Fus upgrade

Hi,
I have few 5508 controlers with 7.0.116.0 version and i decided to upgrade to 7.4. I did an upgrade of software and FUS (
AIR-CT5500-K9-1-7-0-0-FUS.aes) on three of them without any problems. But on the last one i cannot upgrade fus image.. I dowload code from tftp server, wlc checks image and ask for reload for changes to take effects. After reboot it still has old fus installed :/ I have no access to console to see if there are any errors during the reboot. Is there any way of troubleshooting?
Thanks

Hi Ad,
same exact image is being used for all WLCs upgrade? or this is a different one (downloaded separately)?
Rating useful replies is more useful than saying "Thank you"

WLC 5508 preloaded software by default

While ordering cisco part AIR-CT5508-100-K9 via multiline configurator.
My question would be which software version comes whith it by default when choosing SWC5500K9-70.
Is it particularly file named AIR-CT5500-K9-7-0-230-0.aes loaded onto controller?
Many thanks.

Usuall
7.0 or 7.2 is shipped On the wlc. For some reason sometimes the wlc comes with older versions.
If you want to order with specific code i suggest you ask for latest 7.2.
HTH
Amjad
Sent from Cisco Technical Support iPad App

Problem Concurent client WLC 5508

Hi All support,
i have running cisco wlc 5508 with software upgrade 7-4-100-0.aes and 24 cisco 1552 AP with mode mesh, concurent client only show 185 clients but if we using dual load wlc ( Whitout mobility group, if using mobility group clients still stuck concurent) clients can get online 150 on wlc01 and 130 on wlc02 ,total client we have is 300 client.for more information we using feature passive client on this network. any body can help ??
regards,
Sigit H.W

this is debug iapp :
*iappSocketTask: Mar 18 11:13:09.419:      [0480] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.419:      [0496] 00 00 00 00 00 27 22 16 13 f9 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0512] 00 00 00 02 00 00 00 00 00 00 01 46 b8 17 01 00
*iappSocketTask: Mar 18 11:13:09.420:      [0528] 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0544] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0560] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0576] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0592] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0608] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0624] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0640] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0656] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0688] 00 00 27 22 40 a8 81 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0704] 01 00 00 00 00 00 00 00 a8 b9 19 01 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0720] 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0736] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0752] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:09.420:      [0768] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.785: IAPP Rx Frame (1633)
*iappSocketTask: Mar 18 11:13:10.785:      [0000] d0 c2 82 e3 ae c4 2c 36 f8 73 e6 80 81 00 00 0b
*iappSocketTask: Mar 18 11:13:10.785:      [0016] 08 00 45 00 05 cc d3 da 40 00 ff 11 28 8a 0a 9d
*iappSocketTask: Mar 18 11:13:10.785:      [0032] 32 6d 0a 9d 32 15 3e 69 14 7f 05 b8 00 00 00 20
*iappSocketTask: Mar 18 11:13:10.785:      [0048] 03 20 bb 9f 00 00 01 04 00 00 00 00 00 00 01 08
*iappSocketTask: Mar 18 11:13:10.785:      [0064] 00 00 2c 36 f8 73 e6 80 2c 36 f8 73 e6 80 2c 36
*iappSocketTask: Mar 18 11:13:10.785:      [0080] f8 73 e6 80 00 00 aa aa 03 00 40 96 00 00 06 03
*iappSocketTask: Mar 18 11:13:10.785:      [0096] 32 8b 2c 36 f8 73 e6 80 2c 36 f8 73 e6 80 00 00
*iappSocketTask: Mar 18 11:13:10.785:      [0112] 39 00 05 ed e1 cf 0a 30 08 00 00 27 22 40 a4 df
*iappSocketTask: Mar 18 11:13:10.785:      [0128] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0144] 00 00 a0 05 00 00 00 00 00 0c 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0160] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0176] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0192] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0208] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0224] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0240] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0256] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0272] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0288] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0304] 00 00 00 00 00 00 00 00 27 22 84 89 30 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0320] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a3
*iappSocketTask: Mar 18 11:13:10.786:      [0336] 06 00 00 00 00 00 18 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0352] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0368] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0384] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0400] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0416] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0432] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0448] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0464] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0480] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0496] 00 00 00 00 00 27 22 40 a8 57 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0512] 00 00 00 00 00 00 00 00 00 00 00 00 aa 0d 01 00
*iappSocketTask: Mar 18 11:13:10.786:      [0528] 00 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0544] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0560] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0576] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0592] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0608] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0624] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0640] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0656] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0688] 00 00 27 22 2c a9 c6 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0704] 00 00 00 00 00 00 00 00 00 a2 06 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0720] 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0736] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0752] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:10.786:      [0768] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554: IAPP Rx Frame (1633)
*iappSocketTask: Mar 18 11:13:12.554:      [0000] d0 c2 82 e3 ae c4 2c 36 f8 73 04 20 81 00 00 0b
*iappSocketTask: Mar 18 11:13:12.554:      [0016] 08 00 45 00 05 cc 00 50 40 00 ff 11 fc 17 0a 9d
*iappSocketTask: Mar 18 11:13:12.554:      [0032] 32 6a 0a 9d 32 15 30 44 14 7f 05 b8 00 00 00 20
*iappSocketTask: Mar 18 11:13:12.554:      [0048] 03 20 bb fa 00 00 01 04 00 00 00 00 00 00 01 08
*iappSocketTask: Mar 18 11:13:12.554:      [0064] 00 00 2c 36 f8 73 04 20 2c 36 f8 73 04 20 2c 36
*iappSocketTask: Mar 18 11:13:12.554:      [0080] f8 73 04 20 00 00 aa aa 03 00 40 96 00 00 06 03
*iappSocketTask: Mar 18 11:13:12.554:      [0096] 32 8b 2c 36 f8 73 04 20 2c 36 f8 73 04 20 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0112] 39 00 05 ed 00 00 0a 30 08 00 00 27 22 40 a8 f0
*iappSocketTask: Mar 18 11:13:12.554:      [0128] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0144] 00 00 b0 14 01 00 00 00 00 12 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0160] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0176] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0192] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0208] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0224] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0240] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0256] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0272] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0288] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0304] 00 00 00 00 00 00 00 00 27 22 16 a3 f7 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0320] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ad
*iappSocketTask: Mar 18 11:13:12.554:      [0336] 10 01 00 00 00 00 24 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0352] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0368] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0384] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0400] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0416] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0432] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0448] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0464] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0480] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0496] 00 00 00 00 00 27 22 40 a9 37 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0512] 00 00 00 00 00 00 00 00 00 00 00 00 b1 13 01 00
*iappSocketTask: Mar 18 11:13:12.554:      [0528] 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0544] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0560] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0576] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0592] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0608] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0624] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0640] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0656] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0672] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0688] 00 00 27 22 40 a9 fd 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0704] 00 00 00 00 00 00 00 00 00 b2 16 01 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0720] 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0736] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0752] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*iappSocketTask: Mar 18 11:13:12.554:      [0768] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(Cisco Controller) >debug iapp all disable

WLC 5508 reboots itself after upgrading to 7.5.102.0

Hello all.
We have two WLC 5508 and we upgraded both to software release 7.5.102.0 two weeks ago. We also upgrade the FUS to version 1.7.
Since then both WLC reboot randomly once or twice a day with no obvious reason.
Is anyone else facing the same issue?
Many thanks.

Ok, in that case it is very difficult to pin-point the cause for these sorts reboots. It may be due to a unknown bug. Go through below 7.5.102.0 release notes and see any unresolved caveats related to your issue
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn75.html#wp1030058
Have you configure syslog on your WLC ? If so see what is the last syslog message sent by WLC before reloading, it may indicate something.
Do more observation & see whetehr controller reboot every time it hit 1k client limit. Try to narrow down the criteria to identify under what conditions this will trigger.
In my controller I do not have that many clients & cannot comment if it is related.
HTH
Rasika

WLC 5508 Software 7.2.103.0 to 6.0.199.4 is possible to degrade

Hi i got my first WLC 5508 with software 6.0.199.4 and i deployed in site and the branches i have started registring AP's HREAP mode.
And its working fine .
The second WLC came with software 7.2.103.0 so i doubt if i connect this WLC IN one of the site so it will be a issue .
So whats the best practice. is it possible to Downgrade the second WLC to 6.0 version

You better upgrade both WLCs to the latest version. Besides the bug fixes that you get, there are many new features in 7.0 than 6.0. also, 7.2 is having more features than 7.0.
If you want anyway to downgrade, that is possible. But you may lose your configuratoin. so you need to take the precautions and get a backup before the downgrade.
HTH
Amjad
You want to say "Thank you"? Don't. Just rate the useful answers, that is more useful than "Thank you".

EAP-TLS with WLC 5508, Microsoft NPS and custom EKU OID´s

We are trying to implement EAP-TLS with client certificates that have a custom EKU OID to distinguish the WLAN clients. The Microsoft Press Book
Windows Server 2008 PKI and Certificate Security gives an example on how to configure a policy in NPS that matches specific EKU OID´s. At the moment we have two policies that have an allowed-certificate-oid configured that matches the OID´s in our certificates, but our setup is not working as expected. Authentications will only be successful, if the client authenticates with the certificate that is matched by the first policy rule.
For example:
Policy 1: allowed-certificate-OID --> corporate
Policy 2: allowed-certificate-OID --> private
Client authenticates with EKU corporate --> success
Client authenticates with EKU private --> reject
My expectation was, that if Policy 1 will not match the NPS goes over to Policy 2 and tries to authenticate the client.
Has anyone a simmilar setup or can help to figure out what is going wrong?
We have a WLC 5508 with Software Version 7.4.100.0 and a NPS on a Windows Server 2008 R2
regards
Fabian

The policy rejects and the NPS goes to the next policy, only if the user does not belong to the configured group.
This means I need to have one AD group per application policy, but that will not solve my problem. A user could belong to more than one group, depending on how many devices he/she has. It will work with one group only for each user, because the first policy that matches a AD group, the user belongs to, could have a OID that is not in the certificate. This would cause a recejct with reason code 73:
The purposes that are configured in the Application Policies extensions, also called Enhanced Key Usage (EKU) extensions, section of the user or computer certificate are not valid or are missing. The user or computer certificate must be configured with the Client Authentication purpose in Application Policies extensions. The object identifier for Client Authentication is 1.3.6.1.5.5.7.3.2.
The certificate does include this OID but not the custom EKU.

2 Cisco WLC 5508 controllers and software upgrade 7.6.130 + FUS 1.9

Hi
I have two WLC 5508 controllers that need 7.6.130 and FUS 1.9 installed. (Current version 7.3 and FUS 1.7)
Configuration: One controller is at Site A and the other controller is at Site B (two different states..)
They're configured so that if Site A goes down, Site A AP's will failover to Site B and vice versa ..
- What would be the recommended approach for upgrading the software to 7.6.130.0 (from 7.3) and also upgrading FUS 1.9 (from 1.7)?
My plan was to download 7.6.130.0 to both controllers and pre-download the software to all AP's (about 100 total between both sites) and then reboot the controllers at night at the same time? Or one before the other?
Step 2. Install FUS 1.9 to each controller.
I'm concerned over what might happen during the upgrade and AP failover etc..
Thanks

This is what I would do:
Upload v7.6.130.0 to all WLCs and then use the pre image download to push the image to all access points.
Dont reboot the wlc
Image swap in the access points so that v7.6.130.0 is primary
Move all access point to one of the WLCs (A)
Enable ap AAA authentication on the WLC that has no access points and the one you will work on first. This prevents access points from joining
Reboot the WLC (A)
Upload the FUS 1.9.0.0
Reboot WLC (A) this takes up to 45 minutes
When the WLC (A) comes back online, uncheck ap AAA authentication
Move access points from WLC (B) to WLC (A)
Enable ap AAA authentication on WLC (B)
Perform all the other task you did earlier on WLC (A)
That's it.
-Scott

WLC 5508 Software Upgrade

Hi There,
I have upgraded the software version of a WLC 5508 that was running version 6.0.182.0 to 7.0.235.0 version. Looking at the show sysinfo on the controller (as shown below), I notice the Field Recovery Image Version has the previous version. As far I understand that image version will kick in if the 'ESC' character is hit during the boot up process.
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.235.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
Can someone please explain if the FRIV should be upgraded, if yes what is the best way? or otherwise if it should be ok to leave as is?
Best Regards,
egua5261

Thanks for the info. I've upgraded it.
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.235.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 7.0.112.21
Firmware Version................................. FPGA 1.7, Env 1.8, USB console

Upgrade Software Version WLC 5508

Dear,
i try to upgrade the software from 6.0.199.4 to 7.5.102
can we do it directly or we shoud upgrade gradually first from 6.0 to 7.0 then 7.5 ?
when we try from TFTP it give error [code file error disconnected- unknown error]
tru FTP error is [cont send replay disconnected]
Can you Help me Please

addition to Sandeep & Scotts feedback,
When you do the upgrade, make sure your 5508 FUS also get upgraded to latest version 1.9.0.0. Here is the release notes for that
https://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.pdf
This process will take 30-40min & do this within a sufficient outage/maintenance window.
Here is the release notes for 7.4.121.0(7.4MR2) the one I would recommend
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn74mr02.html
Also refer the compatibillity matrix to see which product it will support depending on the products that are available at your environment
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
HTH
Rasika
**** Pls rate all useful responses ****

WLC 5508 Firmware Upgradation

Hi All,
WLC 5508 - current firmware 7.0.116.0 is running on it. we need add couple of 2700 series AP. From the release notes i got know 2700 series supported on the 7.6.120.x and later.
http://www.cisco.com/c/en/us/td/docs/wireless/access_point/2700/quick/guide/ap2700getstart.html
- whereas 7.6.120.x is the latest one in the train. can we have this firmware on the controller as its latest??
- from the release notes - we can have a direct upgrade to 7.6.120.0., upgrading from 7.0.x.x to 7.6.120.x missing so many version in between. any potential problems i may get ??
- FUS (Field upgrade software is necessary) which version and how it can be installed ??
Regards,
Channa

Hi Channa,
Go for the 7.6.130.0 (7.6MR3) when it is available to public. To be released within next couple of weeks.If you need to do this before 7.6MR3 comes then you can get pre-release of that code via TAC. Refer below for that.
https://supportforums.cisco.com/document/12245186/76mr3-beta-availability
Yes, you have to upgrade your FUS, It is recommended to go for v 1.9.0.0. Below will give you the upgrade procedure. Better to do it via CLI & allocate 30-45min downtime for this upgrade
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
Feature wise there are lots of feature available in 7.6.x compare to 7.0.x. But I do not expect any problem going from 7.0.x to 7.6.x as long as you upgrade your FUS first.
Also read these compatibility matrix to see all your AP models are supporting by this 7.6.x code & any other PI or MSE compatibility if you have those.
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
HTH
Rasika
**** Pls rate all useful responses ****

WLC 5508 upgrade

Hi All,
We currently have 4 x WLC 5500 (AIR-CT5508-K9) V01 and V02
So two in one datacenter and the other two in another datacenter. They are connected via Mobility group to and BOYD open wifi with an Anchor WLC the other 1.
All four of them are 7.4.110.0 and the APs we use are AIR-LAP1142N-E-K9 and AIR-CAP2602I-E-K9.
We are looking to get 2700 or 3700 AP so we can use 802.11ac, but we need to upgrade all WLC to 7.6.130.0.
1. is it a direct upgrade from 7.4.110.0 to 7.6.130.0?
2. If I upgrade one datacenter one weekend and the other next weekend, during that week two WLC would be 7.4 and other two 7.6 would it break or cause issue with Mobility group to and BOYD open wifi with an Anchor WLC?
3. Can any please provide step to step guide for the upgrade from 7.4 to 7.6?
Many Thanks
appreciate it :)

Hi Rasika,
Many Thanks for your reply and help!
1. In regards to Upgrade the FUS, is it required to be upgraded once the WLC are upgraded to 7.6 or is just good practice?
2. Or I can I upgrade the FUS another time?
Here is our sysinfo
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.110.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... bupa-sw_sta-un1-dcwlc
System Location.................................. Unit1 DC
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.96.5.10
Last Reset....................................... Software reset
System Up Time................................... 448 days 13 hrs 9 mins 12 secs
System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +39 C
External Temperature............................. +26 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 572
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 64:00:F1:F1:1E:40
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 175
3. Also once Ive upgraded the WLCs from 7.4 to 7.6, should I reboot the WLC and let it upgrade all APs, the upgrade the FUS or upgrade FUS after upgrading the WLC without the reboot which is required?
Many Thanks,
Zilad

WLC 5508 FUS+Software upgrade

Similar Messages

Maybe you are looking for