5508 WLC Upgrade from 7.0.116 to 7.2.111.3

I am planing to upgrade 2 of my 5508 series WLC from 7.0.116 to version 7.2.111.3.  I understand that legacy AP's are no longer supported.  Is there any other issues I should be aware of that others have experienced?  Is the upgrade straight-forward just like other code upgrades?  Thank you.

Thanks so much for all the information.  Afterr reading throught this, it makes sense now.  I do have one more question. After doing a show sysinfo on these controllers, it does look like the FUS does need to be updated.  Should I perform this before I upgrade to version 7.2 code, or after I have peformed the upgrade to 7.2, or does it matter?
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.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

Similar Messages

  • 5508 WLC Upgrade steps

    Single 5508 WLC with 8 x 1142 APs.
    5508 is running FUS 1.3, software version 7.0.116.0, field recovery image 6.0.182.0.
    I need to bring the software version up to at least 7.2.115 to support 2 new 2602 AP i need to install.
    Question is; do I install FUS 1.9 then update my controller to 7.6.120 or do I need to do any intermediate steps?
    This is my first time upgrading a WLC so I'm fresh and this is a production WLC.
    Cheers

    Hi Fisher.
    Normally It doesn't matter as long as you get it done but make sure that you reboot the WLC before doing the next. 
    Here is the procedure for FUS upgrade:
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
    WLC Software upgrade Procedure:
    http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/68835-wlc-upgrade.html
    Regards
    Dont forget to rate helpful posts

  • 5508 WLC upgrade

    Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
    We are currently running an older code  6.0.196.0
    Are there any issues that I need to worry about with this upgrade ?
    Do I need to upgrade the AP's at the same time ?
    Any help would be appreciated.
    Cheers
    Dave

    Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
    Is the WLC going to be used in RUSSIA?  That's what this code is for.  If not, use the "AIR-CT5500-K9-7-2-103-0.aes" file instead.
    Do I need to upgrade the AP's at the same time ?
    The WLC will do it for you.

  • WLC upgrade from 5.1.151 to 7.0.116

    Dears ,
    I have upgraded my WLC from version 5.1.151 to version 6.0.202 and then to 7.0.116 .
    Since when , I see that all clients are disconnected every around 20 minutes and re-connected again .
    Does anyone has any clues ?
    WLC is 4402
    AP are AIR-LAP1231G-E-K9 and AIR-LAP1242G-E-K9 

    when the issue happens.. what does the logs say?? in the mean time.. disable the session timout on all the WLAN on the WLC..
    WLC GUI >> WLAN >> WLAN EDIT >> Advanced >> Session timeout >> Uncheck
    Regards
    Surendra

  • IP Phone 7921 / 7925 roaming issues after WLC upgrade from Version 7.2 to 7.3 and / or 7.4

    Hi,
    We have a customer which is using a Cisco WLC 5508 and 3502I APs. As he used the 7.2.103 release, There were no issues with VoWLAN. Now he needed new APs and ordered the 2602I. To use them he needed to upgrade the WLC to a 7.3 or later release. After the upgrade, he now encounters problems while roaming with the phones. The phones were tested with FW 1.4.1, 1.4.2 and 1.4.3.
    Configuration is set according to wireless voice design guides (VoWLAN DG 4.1, 7921 Deployment Guide). A Cisco TAC is also in progress, but they seem to be uncertain whether it is a wireless or CUCM issue, but I don't see a reason why it should be the CUCM when the only thing changed is the WLC Software Version.
    Is there anybody who is aware of such issues and can offer help?
    Thank you in advance.
    Best regards,
    Patrick

    Hi,
    we had a TAC ticket open with this customer and after some time, the TAC gave us the advise to use this release and the problems are now solved.
    So for others having the same issue: If you only need to support the 2600 APs, stay with the latest 7.2 release as there are some issues with the 7.3 and 7.4 release. If the customer requires HA, AVC or any of the new features + wireless voice, be very careful as it seems that the newer releases are having problems with that. I hope that Cisco will fix this very soon.
    regards,
    Patrick

  • Problem after upgrading from 7.0.116.0 to 7.2.111.3

    We have upgraded 2 of our 5 controllers to 7.2.111.3 but after the upgrade we get ssl-error on our web-auth ssid that use a local netuser. We tried to reinstall the certificate on the controller and it started working but stopped again after 10 min. We have alsot tried reinstalling the web-auth bundle but no luck.
    We get ip-address and the PC indicates that it has internet connection but when we open the browser the ssl problem pops up. After some troubleshooting we moved beyond the ssl problem(we havent solved the problem) and now get this when we open a browser.
    http://portal.zzzz.xx/fs/customwebauth/hotellespinternet.html?switch_url=http://portal.zzzzz.xx/login.html&ap_mac=10:8c:cf:b5:a6:d0&client_mac=f0:7b:cb:67:8a:2d&wlan=Hotell-Esplanad&redirect=portal.zzzz.xx/fs/customwebauth/hotellespinternet.html?switch_url=http://portal.zzzzzz.xx/login.html&ap_mac=10:8c:cf:b5:a6:d0&client_mac=f0:7b:cb:67:8a:2d&wlan=Hotell-Esplanad&redirect=portal.zzzz.xx/fs/customwebauth/hotellespinternet.html?switch_url=http://portal.zzzz.xx/login.html&ap_mac=10:8c:cf:b5:a6:d0&
    porta.zzz.xx is the dns name we use for our web redirects.
    hotellespinternet.html is the web-auth html page
    We have removed the dhcp proxy function on the controller. We have alsot tried with one of our other web-auth pages and that didnt help either.
    Anyone having any suggestions on how we can solve this?

    Did you double check the configuration on the WLC?  Are you anchoring, if so, make sure the mobility is up.  Also, did you upload the FUS image since you went to 7.2?  This is required.
    https://supportforums.cisco.com/docs/DOC-23757
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • CSCuh46996 - Clients behind 3rd party WGB fail DHCP post upgrade from 7.0.116.0

                       Has software version 7.6(1.70) been made available to the public?
    Downloads Home
    Products
    Wireless
    Wireless LAN Controller
    Standalone Controllers
    Cisco 5500 Series Wireless Controllers
    Cisco 5508 Wireless Controller
    Wireless LAN Controller Software
    only has release 7.4.110.0 ED available

    The following entry may indicate a failing harddrive, so doing backups and replacing the harddrive may be in order.
    Disk Information:
              TOSHIBA MK7559GSXF disk0 : (750,16 GB)
              S.M.A.R.T. Status: Failing                                  <-----------
    A little bit about drive S.M.A.R.T. status:
    "The most basic information that SMART provides is the SMART status. It provides only two values: "threshold not exceeded" and "threshold exceeded". Often these are represented as "drive OK" or "drive fail" respectively. A "threshold exceeded" value is intended to indicate that there is a relatively high probability that the drive will not be able to honor its specification in the future: that is, the drive is "about to fail". The predicted failure may be catastrophic or may be something as subtle as the inability to write to certain sectors, or perhaps slower performance than the manufacturer's declared minimum."
    http://en.wikipedia.org/wiki/S.M.A.R.T.

  • WLC Upgrade - FUS Upgrade

    Greetings,
    I am planning on upgrading our redundant 5508 WLC’s from v.7.3.112.0 to v.7.4.110.0 this weekend. One thing I noticed in the release notes of 7.4 is the guideline to update the Field Upgrade Software to v. 1.7.0.0-FUS.
    My question is should this FUS be upgraded before or after I upgrade the WLC to 7.4? On the release notes it does state a FPGA error on the does occur on the 5500 series controllers.
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html#wp45499
    On a Cisco 5500 Series Controller, it is observed that the controller sporadically reboots (due to a defect CSCtr39523) and displays the following FPGA error message:
    fpga: Lost heartbeat from Environment controller, system will reboot in 5 seconds!!!
    A crash file is not created to debug or troubleshoot the error.
    You can resolve this issue by installing the FUS image. Please see Resolved Caveats for more details.
    Thanks,
    Robert

    Honestly, it doesn't really matter the ordr you upgrade in.
    Though, I tend to update the FUS before the image.
    HTH,
    Steve
    Please remember to rate useful posts, and mark questions as answered

  • Is 1252G AP compatible with 5508 WLC

    hi,
    I want to know whether 1252G AP can register with 5508 WLC? from the datasheet 5505 support CAPWAP while 1252 is LWAP. Kindly provide the link regarding the compatibility as well.
    Regards
    Nareh

    hi,
    I would also to add that I will be using CAP 1552E (802.11N) outdoor AP with the 1252G AP. Is it possible that both LWAP and CAPWAP AP registers with the same 5508 WLC ?
    Regards
    Nareh

  • Upgrade from 7.0.235 to 7.0.240 5508 WLC

    Does anyone see a reason to upgrade from 7.0.235 to 7.0.240? I can't go any higher right because we are still using WCS. I read the white papers but as far as I can tell there are no new features..

    Leo is a risky Australian.... beware
    You might be able to get it to work, just Cisco will not support it.  They need to keep the LifeCycle going $$$$$$$
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

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

  • How to Upgrade (legacy setup) 5508 wlc in HA

    How to Upgrade 5508 wlc in HA (both the WLC with permanant AP license only, i.e, without HA license).
    As per 
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf
    Both the WLCs have a valid AP Count license
    • The CLI should be used to configure one WLC as the Standby WLC (as mentioned in the
    configuration section) provided it satisfies the requirement of minimum permanent license count.
    This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are
    needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500,
    and 8500.
    • AP-count license information will be pushed from Active to Standby.
    • In the event of a switchover, the new Active WLC will operate with the license count of the previous
       Active WLC and will start the 90-day countdown.
    • The WLC configured as Secondary will not use its own installed license, and only the inherited
       license from the active will be utilized.
    • After 90-days, it starts nagging messages. It will not disconnect connected APs.
    • With the new WLC coming up, HA SKU at the time of paring will get the AP Count:
    – If the new WLC has a higher AP count than the previous, the 90-day counter is reset.
    – If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.
    – After switchover to a lower AP count, the WLC offset timer will continue and nagging messages 
       will be displayed after time expiry.
    My query is:
    How can we upgrade the WLC version in this scenatio (where both the WLC have only permanent
    AP License and not the HA license), Is it the same as done with HA controller or some othe procedure?
    Pls comment.

    Thanks Freerk for the comments, 
    But my query is, What would be the procedure for image upgradation after configuring HA between both the controllers (Primary-Secondary).
    Will it be same as with the Primary-HA controller, or do i've to upgrade them individually and
    re-configure HA again.

  • WLC Upgrades to 7.5.102.0 from 7.4.100.0 Question

    We went through an upgrade from 7.4.100.0 for all of our WLC's this morning.  One of the interesting features, that we wanted to take advantage of, was the BYOD profiling that the release notes talk about.  I'm going through the controllers and see that there is now a tab under the SSID called "policy mapping".  However, when I look for where I can create the local policy, I cannot find anything on the WLC for completing that task.  I've been looking for instructions and notes on how to do this, but cannot seem to find any.  Would anyone be able to point me in the right direction?  Thanks!   

    Please
    follow the below steps to create Local Policies.
    Step 1  
    Choose Security > Local   Policies.
    Step 2  
    Click New to create a new policy.
    Step 3  
    Enter the policy name and click Apply.
    Step 4  
    On the Policy List page, click the   policy name to be configured.
    Step 5  
    On the Policy > Edit page,   follow these steps:
    In the Match Criteria area,        enter a value for Match Role String. This is the user type or user group        of the user, for example, student, teacher, and so on.
    From the Match EAP Type drop-down        list, choose the EAP authentication method used by the client.
    From the Device Type        drop-down list, choose the device type.
    Click Add to add the device        type to the policy device list.
    The   device type you choose is listed in the Device List.
    In the Action area, specify        the policies that are to be enforced. From the IPv4 ACL drop-down list,        choose an IPv4 ACL for the policy.
    Enter the VLAN ID that should        be associated with the policy.
    From the QoS Policy drop-down        list, choose a QoS policy to be applied.
    Enter a value for Session        Timeout. This is the maximum amount of time, in seconds, after which a        client is forced to reauthenticate.
    Enter a value for Sleeping        Client Timeout, which is the timeout for sleeping clients.
    Sleeping   clients are clients with guest access that have had successful web   authentication that are allowed to sleep and wake up without having to go   through another authentication process through the login page.
    This   sleeping client timeout configuration overrides the WLAN-specific sleeping   client timeout configuration.
    In the Active Hours area,        from the Day drop-down list, choose the days on which the policy has to        be active.
    Enter the Start Time and End        Time of the policy.
    Click Add.
    The   day and start time and end time that you specify is listed.
    Click Apply.

Maybe you are looking for