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

Similar Messages

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"

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

WLC upgrade due to Advisory

Hi,
We have a 5508 WLC running 7.2.110.0 and need to upgrade according to the advisory released today.
It seems we have three upgrade choices:
7.2.110.0 to 7.2.111.3
7.2.110.0 to 7.3.110.0
7.2.110.0 to 7.4.x
I've not upgraded one of these 5508's before, but if they are anything like ASAs then I need to be careful.
Can anyone advise if upgrading from our current version to 7.4 requires planning. Same for 7.3.
How will the WLC upgrades affect the APs (3502i) ?
How does one recover from a failed upgrade on these WLCs?
Thanks.

WLC version 7.4.100 will need Prime Infrastructure Version 1.3 to be managed, but Version 1.3 is not yet available to download at this time.
Huh? What is Prime Infrastructure and why do I need it?

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

Wireless Clients can't connect post WLC Upgrade to version 7.4.100.0

Upgraded WLC Flex 7500 controller to: 7.4.100.0
Previous WLC Controller version: 7.2.111.3
After the upgrade, all AP's reported back to the controller and looked like working. We have 50+ branch sites that connect back via Layer 2 to the main office. The main office SSID's were broadcasting and users could connect and get the proper IP's. Users that connected back through FlexConnect AP's couldn't obtain an IP address. The client would authenticate to the WLC and accept the SSID key, but would not get an IP address. I see with the 7.4.100.0 upgrade there are more options for DHCP for each interface, which we don't use interfaces for all sites as we did in the early days, now we make sure the flex connect tab has the vlan identifier in the tab and the traffic goes out the local firewall etc. Each remote site has a Linux based firewall and DHCP server.
Looking for any insight with the 7.4.100.0 upgrade that may cause clients to not connect and obtain an IP address.
We have since back dated our WLC Software to: 7.2.111.3 to allow things to work pre upgrade which everything worked fine.
Any suggestions would be great, we had to upgrade version 7.4.100.0 to support our AP 1602.
Thanks in advance.
Matt

Verify that you have an upgraded FUS image. Second, make sure your WLAN to vlan mapping on the FlexConnect AP's have the correct vlan mapping. I have seen these change to the default vlan mapping.
Sent from Cisco Technical Support iPhone App

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.

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

WLC Upgradation

Dear Team,
We are planning to upgrade from WLC Software Version : 7.3.112.0 to AIR-CT5500-K9-7-4-121-0 on Model : 5508.Please advise me that its correct path?
Please share the upgrade path materix.
Regards

HI Waqas,
Before upgarde, you have take a downtime window of atleast 1 hour.
From here you can download the new image:
http://software.cisco.com/download/release.html?mdfid=282600534&flowid=7012&softwareid=280926587&release=7.6.100.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
How to upgarde :
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml
Dont forget to add FUS image:
Field Upgrade Software (FUS) is a special AES package that performs various system-related component upgrades.
Here is the link:
http://software.cisco.com/download/release.html?mdfid=282600534&flowid=7012&softwareid=284364857&release=1.9.0.0&relind=AVAILABLE&rellifecycle=&reltype=latest
How to upgarde:
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html
Also check the compatibility matrix:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Hope it helps.
Reagrds
Dont forget to arte helpful posts

WLC Upgrade question

Hi
one of the WLC 5500 series is running 6.0.199.4 can I upgrade directly to 7.4
appreicate feedback
Paul

HI Paul,
Go for 7.4.121.0 MD, it si very stable version(even cisco recommanded this).
Here is the link.
http://software.cisco.com/download/release.html?mdfid=282600534&flowid=7012&softwareid=280926587&release=7.6.120.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
Upgrade FUS:
via GUI:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html#wp53877
Via CLI:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html#wp43765
Regards
Dont forget to rate helpful posts

WLC upgrade and failover

Hi,
we have two WLC. WLC1 in one data center and WLC2 in DR data center. I've to upgrade s/w on both WLCs. currently all of our APs are associated with WLC1 so I'll upgrade WLC2 1st. and then WLC1. when I ugprade WLC1 then all APs will failover to WLC2. once WLC1 s/w ugprade is done then I've to failover all APs to WLC1. how do I do that?
Plus: I found that two images on cisco website. FUS.aes and .aes file. do I have to upload both files on WLC for ugprade? which one should I upload first?

Plus: I found that two images on cisco website. FUS.aes and .aes file. do I have to upload both files on WLC for ugprade? which one should I upload first?
Please read the Release Notes first! "FUS" firmware is meant for WAPs/WLCs in Russia, comrade.
we have two WLC. WLC1 in one data center and WLC2 in DR data center. I've to upgrade s/w on both WLCs. currently all of our APs are associated with WLC1 so I'll upgrade WLC2 1st. and then WLC1. when I ugprade WLC1 then all APs will failover to WLC2. once WLC1 s/w ugprade is done then I've to failover all APs to WLC1. how do I do that?
You can pre-download the new IOS into the WAP BEFORE you reboot the WLC. This way when the WLC reboot the WAPs will too.

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

602-OEAP Access Point broken after WLC upgrade to 7.4.100.0

Hey all,
I have a TAC case open, but it doesn't seem to be making any progress....
I upgraded my 5508 controller from 7.2.111.3 up to 7.4.100.0
Most of my APs are fine. 3500s, 1100s etc.except for 602i APs. The APs associate, they update software etc, but they won't broadcast the WLAN.
An interesting thing, on the 602 AP, in the log, I see this:
*Mar 06 15:08:12.667: SSID remote, WLAN Profile Name: RemoteOEAP, added to the slot[0], disabled
So the AP is definately talking to the WLC and being pushed the correct WLAN profile.
Another thing I noticed:
On the controller, the AP shows the the Admin status of the radios is showing DOWN, but the Admin status on the AP itself shows UP
I've done a factory reset on the APs to no avail. I have a 2504 WLC as well that i'm in the process of implementing in a DMZ specificially for these APs, and for testing purposes, I associated the 602 Ap to that WLC as well. This one is running 7.4.100.0 too, same results. It would appear to be a problem with this version of software?
Anyone else had this problem?

Hey, thanks for taking a look at this. Unfortenately, that's not the issue in this case. The AP is set to "United States" and the WLC is only configured for US. Just so I'm looking in the correct place:
On the AP in the WLC, it's under the "Advanced" tab
On the WLC, its under Wireless -> Country correct?
The frustrating part is that the 600 really doesn't have anything that can be configured on it, which means troubleshooting is also limited.

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.

WLC Upgrade - FUS Upgrade

Similar Messages

Maybe you are looking for