09-28-2014 12:08 PM - edited 07-05-2021 01:36 AM
Hi Experts,
Awhile ago, I upgraded the standby 4404 WLC from 5.1.151.0 to 5.2.193.0 to 7.0.240.0 and the upgrade was successful. Before upgrading the active WLC, I tested a couple of APs to join the standby WLC (enabled master controller) and the APs don't join the standby WLC, it joins back to the active WLC. The client wants to return to the old code. Is there any downgrade path I have to follow and what would be the procedure for downgrading?
Regards,
Solved! Go to Solution.
09-28-2014 02:05 PM
You should convince customer NOT to go back to 5.x, no body able to support that old code.
Did you try to set 7.0.x code WLC as primary controller for that AP ? If that option is not available in 5.x code (High Availability tab of AP settings) then you can try assign it via CLI like this.
LAP#capwap ap primary-base <WLC-NAME> <WLC-MGT-IP>
OR
LAP#lwapp ap primary-base <WLC-NAME> <WLC-MGT-IP>
Give it a try & see
Why you cannot see the option of upgrading the active WLC to 7.0.x as a resolution. Makesure AP in use supported by this code version
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
Regarding a downgrade, I haven't done this sort of downgrade which involve major software codes. (not recommended). Here is a reference post for a downgrade within the same software train.
http://mrncciew.com/2013/03/14/downgrading-wlc-software/
HTH
Rasika
**** Pls rate all useful responses ****
09-28-2014 11:33 PM
I have never done that & even Cisco does not recommend any downgrades. If something goes wrong you would be helpless.
I think safe approach would be talk to customer & organize a sufficient outage window to upgrade the primary in step by step manner (like you did for standby).
If you are 7.0.x code at least you are in a supported code release.
Pls do not forget to rate our responses if that is useful to you :)
HTH
Rasika
09-28-2014 02:05 PM
You should convince customer NOT to go back to 5.x, no body able to support that old code.
Did you try to set 7.0.x code WLC as primary controller for that AP ? If that option is not available in 5.x code (High Availability tab of AP settings) then you can try assign it via CLI like this.
LAP#capwap ap primary-base <WLC-NAME> <WLC-MGT-IP>
OR
LAP#lwapp ap primary-base <WLC-NAME> <WLC-MGT-IP>
Give it a try & see
Why you cannot see the option of upgrading the active WLC to 7.0.x as a resolution. Makesure AP in use supported by this code version
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
Regarding a downgrade, I haven't done this sort of downgrade which involve major software codes. (not recommended). Here is a reference post for a downgrade within the same software train.
http://mrncciew.com/2013/03/14/downgrading-wlc-software/
HTH
Rasika
**** Pls rate all useful responses ****
09-28-2014 10:03 PM
Hi Rasika,
I did try setting the standby controller as the primary controller in the AP. The AP type is 1131. What I didn't check is the global setting for primary and secondary controller. Right now the active controller is still 5.1.151.0 code. There are 85 APs. Do you think If i upgrade the active controller, all APs will join the active controller? I don't think upgrading the code in the standby controller caused this issue.
Regards,
09-28-2014 10:17 PM
If you have a test 1131 AP then test this again while monitoring the AP console, that will tell us what's happening.
Prior to upgrade the active one we want to make sure AP can fail over to standby unit.
I also do not think upgrade standby 4400 cause any of these.
HTH
Rasika
**** Pls rate all useful responses ***
09-28-2014 10:47 PM
Hi Rasika,
There is no extra 1131 AP. Can I use this command to force the AP to join the standby controller (lwapp ap controller ip address 10.0.254.5) in AP cli,
Regards,
09-28-2014 11:09 PM
Hi,
No, that command won't help you to force that AP to go & register to that WLC (unless you have a single WLC ). Once AP register to a WLC it will learn all the WLC information in that mobility group. So as long as your active & standby 4400 in same mobility group all your AP already aware of both WLC.
You have to specify the primary controller in order for an AP to go & register for that particular WLC. Below do that for you.
LAP#capwap ap primary-base <WLC-NAME> <WLC-MGT-IP>
OR
LAP#lwapp ap primary-base <WLC-NAME> <WLC-MGT-IP>
If 5.x. support you can do that via WLC CLI as well.
config ap primary-base <controller_name> <Cisco_AP_name> [controller_IP_Addres]
See this for AP Failover behavior of this 7.x code.
http://mrncciew.com/2013/04/07/ap-failover/
HTH
Rasika
**** Pls rate all useful responses ****
09-28-2014 11:26 PM
Hi Rasika,
Worst case scenario, if the client insists to revert back to 5.1.151.0, how do I do this? Can I downgrade directly from 7.0.240.0 to 5.1.151.0 or 7.0.240.0 to 5.2.193.0 to 5.1.15.0? I have taken a backup configuration before I did the upgrade.
Regards,
09-28-2014 11:33 PM
I have never done that & even Cisco does not recommend any downgrades. If something goes wrong you would be helpless.
I think safe approach would be talk to customer & organize a sufficient outage window to upgrade the primary in step by step manner (like you did for standby).
If you are 7.0.x code at least you are in a supported code release.
Pls do not forget to rate our responses if that is useful to you :)
HTH
Rasika
09-28-2014 11:39 PM
Hi Rasika,
Thanks a lot for the info.
Regards,
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: