11-06-2013 03:31 PM - edited 07-04-2021 01:13 AM
Hi all,
I'm preparing to enable HA SSO on a pair of 5508's; one with an HA SKU and one with a 50 AP license. I noticed that the bootloader's and FRIV's are different, even though the firmware versions are the same.
Should I apply the AIR-CT5500-K9-1-7-0-0-FUS.aes to the HA WLC before enabling AP SSO, or will the peering process take care of this for me? Thanks!
APSSO) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.5.102.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... Cisco_5f:a3:44
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.192.252.21
Last Reset....................................... Software reset
System Up Time................................... 0 days 0 hrs 18 mins 42 secs
System Timezone Location......................... (GMT -7:00) Mountain Time (US and Canada)
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... US - United States
Operating Environment............................ Commercial (0 to 40 C)
WLC1) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.5.102.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 7.0.112.21
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... MHP-5508-WLC1
System Location.................................. SMDC G-13
System Contact................................... 0117
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.192.252.11
Last Reset....................................... Software reset
System Up Time................................... 38 days 13 hrs 14 mins 0 secs
System Timezone Location......................... (GMT -7:00) Mountain Time (US and Canada)
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... US - United States
Solved! Go to Solution.
11-06-2013 07:23 PM
Yes you should make sure the FUS is upgraded and identical prior to enabling AP SSO.
Sent from Cisco Technical Support iPhone App
11-06-2013 07:23 PM
Yes you should make sure the FUS is upgraded and identical prior to enabling AP SSO.
Sent from Cisco Technical Support iPhone App
11-07-2013 04:27 AM
Thanks. I was a bit nervous about reburning the firmware.
11-07-2013 05:03 AM
You should be fine, the important thing is to disable AP SSO.
Sent from Cisco Technical Support iPhone App
02-19-2014 01:10 PM
Scott F. You mention disabling AP SSO first. Maybe this is restating what you just said but I have a scenario where I have two 5500s running FUS 1.7 with AP SSO enabled. I want to upgrade to FUS 1.9. I had heard that you could run the FUS upgrade just like the image upgrade, in other words allow the primary to send the code over to the standby using redundancy links.
Can anyone confirm if the FUS upgrade works the same way and the code upgrade? Or do I have to disable AP _SSO and then do each controller indovudually?
TIA
02-19-2014 01:22 PM
Don't think that will work since this is a boot image upgrade. You can open a TAC case and confirm, but you can try and see if the HA gets the image. If it doesn't, then you know that you have to install it separately.
Sent from Cisco Technical Support iPhone App
02-19-2014 01:25 PM
Ok thanks. Just opened a case. I'll reply to the thread with their answer.
02-20-2014 01:30 PM
Received this from TAC. Looks like you have to break SSO ---> upgrade FUS code ---> then enable SSO again. -Enjoy
Regarding your questions the answers are above:
-The upgrade of the FUS image behaves the same way as a normal controller code upgrade.
There is no different procedure than upgrading the controller but as it is FUS image which is independent on each controller you will have to break SSO and install the image on each controller and then bundle the controllers again after the upgrade.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
02-20-2014 01:34 PM
Yeah... Didn't think that would push. Well enjoy the fun:)
Sent from Cisco Technical Support iPhone App
02-28-2014 03:25 AM
What about forcing the standby controller into maintenace mode? Maybe it lets me initiate SW download then. Since the new FUS only updates bootloader and CF stuff it should be fine... at least I hope so.
1) Disable Uplink of standby, standby moves to maint
2) Reenable Uplink, push SW and reboot
3) Install FUS and reboot into standby mode again
4) Do switchover
5) Repeat steps 1 to 4
But I'm out of office now until april possibly. I will report back then. Maybe someone has some input on this?
02-28-2014 05:30 AM
I would stick to the instructions and break ap SSO. Your safer that way.
Sent from Cisco Technical Support iPhone App
03-03-2014 12:05 PM
I was told by TAC that the FUS upgade could be done with AP SSO enabled.
Do you know if that stance has changed recently? I was told that it would be treated just like a typical code upgrade and that the image would be pushed over to the standby controller....
03-03-2014 12:07 PM
Well... if TAC told you that, then I would try it and see.... heck.. you have it in writing, so you can blame them if it doesn't work.
Thanks,
Scott
*****Help out other by using the rating system and marking answered questions as "Answered"*****
03-03-2014 12:09 PM
Did you see the post above:
Received this from TAC. Looks like you have to break SSO ---> upgrade FUS code ---> then enable SSO again. -Enjoy
Regarding your questions the answers are above:
-The upgrade of the FUS image behaves the same way as a normal controller code upgrade.
There is no different procedure than upgrading the controller but as it is FUS image which is independent on each controller you will have to break SSO and install the image on each controller and then bundle the controllers again after the upgrade.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
Thanks,
Scott
*****Help out other by using the rating system and marking answered questions as "Answered"*****
03-03-2014 12:10 PM
I did see that post, but it seemed to contradict what I was told by TAC.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide