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

Similar Messages

  • 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 ****

  • 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 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

  • 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 ios upgrade in ha mode

    I am having 2 wlc 5508 in HA mode, and want to upgrade ios from 7.5 to 7.6
    Current IOS file status in primary and secondary.
    Primary  WLC IOS :  AIR-CT5500-K9-7-5-102-0.aes
    Standby WLC IOS :  AIR-CT5500-LDPE-K9-7-5-102-0.aes
    HA WLC ios upgrade procedure is when we  upgrade ios in primary wlc it will push to standby wlc and if earlier ios version match it will accept it.
    ISSUE : If you check in wlc status detail I have given upper both has same ios version but IOS file are different and currently in HA mode and working.
    Now I am trying to upgrade IOS it is not allow me to upgrade it.
    Giving below error :
    TFTP receive complete... extracting components.
    Checking Version Built.
    Image version check passed.
    Informing the standby to start the transfer download process
    Waiting for the Transfer & Validation result from Standby.
    Standby - Standby receive complete... extracting components.
    Standby - Checking Version Built.
    Standby - Image version check passed.
    Standby - Transfer failure : Upgrade from non LDPE to LDPE software is not allowed.
    Please download AIR-CT5500-K9-x-x-x-x.aes image instead.
    Transfer & Validation on Standby failed.
    Transfer download failed both on Active & Standby, Please retry download
    (Cisco Controller) >
    Please suggest how I can upgrade IOS in HA mode.

    Primary WLC IOS : AIR-CT5500-K9-7-5-102-0.aes
    Standby WLC IOS : AIR-CT5500-LDPE-K9-7-5-102-0.aes
    This won't work and you'll see from the error message.  Your standby WLC has a particular firmware loaded with LDPE enabled.  So first, you need to answer if you need LDPE or not.   
    Both firmwares has to match, including LDPE.  If you need LDPE, the your primary has to be loaded with LDPE before you can proceed.  If you don't need LDPE, then you need to downgrade the secondary to non-LDPE version before you can proceed.

  • 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 and Autonomous AP 1240 upgrade to Lightweight

    Hi All,
    very simple question, for who knows it... :-)
    Does an autonomous Cisco AP 1240G/AG series upgraded to Lightweight register/associate to a WLC 5508 ??
    I found some documention, it seems not:
    These Cisco wireless LAN  controllers support autonomous access points upgraded to lightweight  mode:
    • 2000 series  controllers
    • 4400 series  controllers
    • Cisco Wireless Services  Modules (WiSMs) for Cisco Catalyst 6500 Series  Switches
    • Controller Network Modules  within the Cisco 28/37/38xx Series Integrated Services  Routers
    • Catalyst 3750G Integrated  Wireless LAN Controller Switches
    The 5500 is not in the list...
    However based in some posts and other webpages, it looks that the 1240 converted to LAP can join a 5508...
    Somebody can help please??
    MANY THANKS!!!
    Alex Bertrán

    Yes, it can. Always check release notes for controller code, it lists supported access points:
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn601820.html

  • Can we upgrade IOS in WLC 5508 through CISCO prime?

    I have CISCO prime 2.0 and CISCO WLC 5508 HA SSO pair.
    I would like to upgrade the software code for the WLC HA pair.
    Can I do through the CISCO prime ......
    As per the link :http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-43571
    1. After the WLCs are configured in the HA setup, the Standby WLC cannot be upgraded directly from the TFTP/FTP server.
    Prime do the upgrade through FTP server , so will it be ok if we do the upgrade through it, for HA WLC.

    Please check this link to upgrade wLC software in HA setup.
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html
    Once the Primary WLC complete the upgrade , it will transfer the entire image to the Standby WLC via the Redundant Port.
    Regards
    Dont forget to rate helpful posts

  • 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.

  • Upgrade WLC 5508 IOS 8.0.100

    Hi
    I wan to upgrade the IOS version on WLC 5508, but I do not is recommended, 
    Can you help me is recommended upgrade for this version?.
    The apple devices have a problem with retry authentication constantly
    regards

    After WLC upgrade to 8.0.100 [ not in HA mode], the AP seem to be dropping out and reconnect using the fallback to IP-  inspite of the statically configured IP on the AP
    Running Outdoor mesh AIR-CAP1552E-N-K9 on WLC 5508
    (Cisco Controller) >show boot
    Primary Boot Image............................... 8.0.100.0 (default) (active)
    Backup Boot Image................................ 7.6.101.2
    =========
    Last AP disconnect details
    - Reason for last AP connection failure.................... The AP has been reset by the controller
    - Last AP disconnect reason................................ Unknown failure reason
    Last join error summary
    - Type of error that occurred last......................... Lwapp join request rejected
    - Reason for error that occurred last...................... No Mwar payload found in join request
    - Time at which the last join error occurred............... Dec 03 00:05:26.114
    AP disconnect details
    - Reason for last AP connection failure.................... The AP has been reset by the controller

  • Upgrade WLC 5508

    I'm trying to upgrade my Cisco WLC 5508 with 125 AP's from 7.0.116 to 7.4.110, so it can support the new AIR-CAP2602 and the old AIR-LAP1142 at the same time, but for some reasons the AP's will not accept the new software.
    (Cisco Controller) >show boot
    Primary Boot Image............................... 7.0.116.0 (default) (active)
    Backup Boot Image................................ 7.4.110.0
    I have tried to predownload the new image to all AP's from the WLC, and it sucses, but the predownloaded image was not copied into the Backup image.
    (Cisco Controller) >show ap image all
    Total number of APs..............................   125
    Number of APs
            Initiated........................................... 0
            Predownloading................................ 125
            Completed predownloading................ 0
            Not Supported.................................. 0
            Failed to Predownload....................... 0
                                                     Predownload     Predownload
    AP Name            Primary Image  Backup Image   Status          Version        Next Retry Time  Retry Count
    AP-xx-01               7.0.116.0      7.0.116.0      Complete        7.4.110.0      NA               NA
    When I then re-boot the WLC on the new software (7.4.110), the AP's just show up in the GUI as "downloadning" and the the AP's re-boot. This going on and on, so I had to force the WLC to reset on the old software (7.0.116).
    I think my problem is, that the AP's have the same image atached to both Primary and Backup, so my question is:
    How do I clear the information about the Backup image in the AP's and downlod the new image to the AP's?
    Can I ftp/tftp the new image direct to the AP's and Then do any configurations at the AP's to make it the Backup image?
    THX Frank

    Hi Frank,
    (Cisco Controller) >show bootPrimary Boot Image............................... 7.0.116.0 (default) (active)Backup Boot Image................................ 7.4.110.0
    Since your controller backup image is 7.4.100.0, when you pre-download the image to AP use the following ("backup" keyword instead of "primary")
    (Cisco Controller) >config ap image predownload backup all
    Then check "show ap image all" to confirm that new image version shown as pre-downloaded image version in your APs.
    Then you can go ahead & swap the image on all your APs using
    (Cisco Controller) >config ap image swap all
    Then you can change the boot image on WLC to pointing to 7.4.110.0 & reset your controller.
    (Cisco Controller) >config boot backup
    (Cisco Controller) >show boot
    Primary Boot Image............................... Code 7.0.116.0 (active)
    Backup Boot Image................................ Code 7.4.110.0 (default)
    (Cisco Controller) >reset system
    Let us know how it goes
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • Some C1242 Radios are disabled after WLC 5508 upgrade to 7.3.101.0

              One week ago I use a WLC 5508 to place and replace another WLC 5508 with version 6.0.199.4, when I conect the new WLC all AP´s works OK only 10 dont work and not are recognizes from the WLC with version 7.3.101.0. The fail is the radios stay disabled. All ap´s are AIR-AP1242G-AK9 . See the image below, the only difference this ten AP´s are conected in switches cisco all the rest are connected in switches of ohter vendor.  
    If possible some command in the configuration is not neccesary and make the bad function?
    This is tipically config apllied by the customer in they cisco switches
    interface   GigabitEthernet0/22
    description PB-RS-A22
    switchport access vlan 5
    switchport mode access
    switchport port-security
    switchport port-security aging time 2
    switchport port-security violation restrict
    switchport port-security aging type   inactivity
    macro description cisco-desktop
    spanning-tree portfast
    spanning-tree bpduguard enable
    I reed some documents but i don´t found the right solution can any help me?
    Thank

    Are the APs being powered through POE or perhaps an injector (if injector, do you have the injector override enabled for joined APs with their radios down?)  What's the disparity of the models; are all 1242s in this "down radio" state, or only the 1242s plugged in to the Cisco Switches?
    When you say the 10 don't work and are not "recognized" by the WLC, are you indicating that they have not re-joined the newer WLC or are they joined but their radios are not operationally up?  Please clarify the state of these APs.
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn73.html#wp965532
    Please note that a version prior to 7.0.98.0 cannot be upgraded directly to 7.3.101.0 from the WLC perspective, but it's possible your 1242 AP's image (used from the 6.0.199.4 release) is not able to properly join and download code for the 7.3.101.0 WLC that was put in to place.  The 1242 APs in your scenario would still be running the old 6.0.199.4 image.
    I'm curious what all is or isn't happening from the questions above, but you may need to load a newer recovery release on the 1242s to have them join properly - or - downgrade the WLC to a version that allows a direct upgrade from 6.0.199.4 such as 7.0.240.0.  Let the APs join the downgraded WLC and finish up any image downloads and re-join, then upgrade the WLC back to 7.3.101.0 (would recommend latest 7.3.112.0 instead) and see if they rejoin and radios are online.

  • 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

  • Anchor mobility configuration getting lost in wlc 5508 ios code 7.4.100.0

    It is observed that in WLC 5508 , ios 7.4.100.0 ,  mobility anchor configuration on wlan  is getting lost .  we configure anchor ip address on  guest wlan > mobility anchor >  Switch IP Address (Anchor).
    We have configured the template on NCS 2.0 to push the anchor mobility ip address on all WLC
    Has anyone oberved this behavoiur. We have more than 100 WLC  , and  everyweek  mobility anchor configuration is lost on some WLC having code  7.4.100.0.

    I am having this exact same problem.  I am running 7.3 on 5508 WLC.   My remote site LAP's are using Flex (HREAP).  The initial access point that my laptop associates to connects with no problem, as soon as I wander out of range of the initial LAP and into the area of another access point, I lose data connectivity.   The was validated like the original post as I start a constant ping on the LAN and watch as the ping latency increases and then ping replies stop.  The only way to correct the problem is resetting of the wireless adapter on the laptop.  Side note my DroidX has no problem wandering from AP to AP.
    Laptop: Windows 7 32bit
    I then returned to my home site and test where I have a secondary controller and the LAP's are configured for local mode, no problems roaming from access point to access point.   Validated with constant ping test.  The pings drop for a second and re-
    continues as the laptop reconnects.
    **Edit: I am going to try the removing the DHCP Addr. Assignment required option, and report that back to the TAC engineer.
    Message was edited by: Michael Dunki-Jacobs
    **Edit Solved:***
    The problem is in deed solved by turning the "DHCP Address Required" but why?

Maybe you are looking for

  • JVM Crash: ConcMarkSweepGC related?

    We're experiencing the following JVM crash approximately 2-5 times per day on a well traffic application server running Tomcat 5.5 under Java 1.5 (05) on Linux with a 2.4.21-37 kernel. I'm posting here because we kind of have no route to take: I can'

  • Video Chat doesn't work

    My ichat Video chat sometimes works, yet usually doesn't The error message: Date/Time: 2009-03-28 23:40:49.446 +0800 OS Version: 10.5.6 (Build 9G55) Report Version: 4 iChat Connection Log: 2009-03-28 23:40:26 +0800: AVChat started with ID 1038444205.

  • AP Payment document update

    Hi Consultants, We have requirement to update AP payments checks voucher field in payment overview screen from Cash Management. we will load the bank back file (which have account number) to CM for reconcilication after this process we need to update

  • SQL developer download - unable to connect

    Hello, I'm a beginner at Oracle SQL developer. I just downloaded the sql developer 3.2.20.09.87 one which includes zip file JDK. However it is not letting me connect. This is the error I'm getting. failure- test failed: IO error: The network adapter

  • No email option in Delivery Extension for SP2010 and SSRS integrated mode

    I just set up SSRS R2 in integrated mode with SharePoint 2010. When I went in to setup a subscription, the only options I had under delivery extension were Windows File Share, SharePoint Library and Null Provider. Did I miss something on the setup to