10-23-2013 03:35 PM - edited 07-04-2021 01:08 AM
Hi.
I have a WLC 5508 with its WLC HA in a redudancy mode.
The systems works fine, but I have the necessity to upgrade from 7.3 to 7.5.
Which is the corrects procedure?
Regards.
Mirko Severi.
Solved! Go to Solution.
10-24-2013 09:21 PM
Hi,
Once you upgrade primary WLC , it will automatically update the file to secondary WLC. And need to reboot together.
10-25-2013 03:37 PM
Complete these steps:
After the WLCs are configured in the HA setup, the Standby WLC cannot be upgraded directly from the TFTP/FTP server.
Initiate upgrade on the Active WLC in the HA setup via CLI/GUI, and wait for the upgrade to finish.
Once the Active WLC executes all the upgrade scripts, it will transfer the entire image to the Standby WLC via the Redundant Port.
When the Standby WLC receives the image from the Active WLC, it will start executing the upgrade scripts. The transfer of the image to standby and the execution of the upgrade scripts on the Standby WLC can be seen on the Active WLC Console/Telnet/SSH/Http connection.
After a successful message of Standby Upgrade is observed on the Active WLC, it is important to issue the show boot command on the Active WLC in order to make sure the new image is set as the primary image.
Once verified, initiate primary image pre-download on the Active WLC in order to transfer the new image to all the APs in the network.
After pre-image is completed on all the APs, issue the show ap image all command in order to verify that the primary image on the WLC is set as the backup image on APs.
Initiate swap option to interchange the backup image as primary on the APs. With this implementation, the WLC's and AP's primary image is set to the new image.
Issue the reset system in command as per planned outage with the “no swap option” in order to reset the APs and WLCs so that they can boot with the new image.
The Standby WLC will reset just one minute before the scheduled reset time to boot and come up first to take over the network with the new image.
All the APs will reboot and join the new Active WLC, and the previous Active WLC will transition to the standby role.
Issue the show boot, show sysinfo, show ap image all, and show redundancy summary commands in order to verify that both the WLCs and APs have booted with the new image.
Service Upgrade is not supported in this release, so network downtime should be planned before you upgrade the WLCs in the HA setup.
The peer should be in the Hot Standby state before you start the upgrade in the HA setup.
It is recommended to reboot both the WLCs almost together after upgrade so that there is no software version mismatch.
Schedule Reset applies to both the WLCs in the HA setup. The peer WLC reboots one minute before the scheduled timer expiry on the Active WLC.
The Standby WLC can be rebooted from the Active WLC using the reset peer-system command if a scheduled reset is not planned.
Debug transfer can be enabled on the Active WLC as well as the Standby WLC.
If Active WLC unexpectedly reboot between software download and reboot both WLCs, you need to reboot both WLCs in order to complete software upgrade.
No direct download and upload configuration is possible from the Standby WLC.
All download file types like Image, Configuration, Web-Authentication bundle, and Signature Files will be downloaded on the Active WLC first and then pushed automatically to the Standby WLC.
Once the configuration file is downloaded on the Active WLC, it is pushed to the Standby WLC. This results in the reset of the Standby WLC first, followed by the reset of the Active WLC.
The Peer Service Port and Static route configuration is a part of a different XML file, and will not be applied if downloaded as part of the configuration file.
The download of certificates should be done separately on each box and should be done before pairing.
Uploading different file types like Configuration, Event Logs, Crash files, and so forth can be done separately from the Standby WLC. However, the CLI to configure different parameters for upload like Server IP, file type, path and name should be done on the Active WLC. Once the upload parameters are configured on the Active WLC, the transfer upload peer-start command should be issued on the Active WLC in order to initiate the upload from the Standby WLC.
The service port state will be synched from the Active WLC to the Standby WLC. That is, if DHCP is enabled on the Active WLC service port, the Standby WLC will also use DHCP for getting the service port IP address. If the service port of the Active WLC is configured with a Static IP Address, the Standby WLC also needs to be configured with a different Static IP Address. The CLI to configure the IP Address for the Standby WLC service port is configure redundancy interface address peer-service-port
For more info
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml#upgrade
10-24-2013 12:07 AM
(Now if you reboot the controller all aps will reboot and get the new CAPWAPP IOS from the rebooted WLC. To copy new files to each AP automatically from controller and reboot will take time for AP , (approx. 25min)But after loading IOS in AP it will start broadcasting SSID with new image
If you want to avoid the time for Each AP to copy IOS from controller ,to reduce down time . After uploading the WLC image you can go to WIRELESS->All Aps-> Global Configuration->Download Primary
10-24-2013 12:48 AM
Hi, Shibi.
Thanks for you reply, but the problem is the upgrade of the sku HA.
How can upgrade both wlc and wlc sku HA?
I upgrade the primary and automatically it also updates the wlc sku HA?
Regards.
Mirko.
10-24-2013 05:35 AM
Take a look at the link below
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml
Steve
Sent from Cisco Technical Support iPhone App
10-24-2013 09:21 PM
Hi,
Once you upgrade primary WLC , it will automatically update the file to secondary WLC. And need to reboot together.
10-24-2013 11:31 AM
Yes, it is necessary and how to do so with steps please refer to the link-
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml#cliconfig
10-25-2013 03:37 PM
Complete these steps:
After the WLCs are configured in the HA setup, the Standby WLC cannot be upgraded directly from the TFTP/FTP server.
Initiate upgrade on the Active WLC in the HA setup via CLI/GUI, and wait for the upgrade to finish.
Once the Active WLC executes all the upgrade scripts, it will transfer the entire image to the Standby WLC via the Redundant Port.
When the Standby WLC receives the image from the Active WLC, it will start executing the upgrade scripts. The transfer of the image to standby and the execution of the upgrade scripts on the Standby WLC can be seen on the Active WLC Console/Telnet/SSH/Http connection.
After a successful message of Standby Upgrade is observed on the Active WLC, it is important to issue the show boot command on the Active WLC in order to make sure the new image is set as the primary image.
Once verified, initiate primary image pre-download on the Active WLC in order to transfer the new image to all the APs in the network.
After pre-image is completed on all the APs, issue the show ap image all command in order to verify that the primary image on the WLC is set as the backup image on APs.
Initiate swap option to interchange the backup image as primary on the APs. With this implementation, the WLC's and AP's primary image is set to the new image.
Issue the reset system in command as per planned outage with the “no swap option” in order to reset the APs and WLCs so that they can boot with the new image.
The Standby WLC will reset just one minute before the scheduled reset time to boot and come up first to take over the network with the new image.
All the APs will reboot and join the new Active WLC, and the previous Active WLC will transition to the standby role.
Issue the show boot, show sysinfo, show ap image all, and show redundancy summary commands in order to verify that both the WLCs and APs have booted with the new image.
Service Upgrade is not supported in this release, so network downtime should be planned before you upgrade the WLCs in the HA setup.
The peer should be in the Hot Standby state before you start the upgrade in the HA setup.
It is recommended to reboot both the WLCs almost together after upgrade so that there is no software version mismatch.
Schedule Reset applies to both the WLCs in the HA setup. The peer WLC reboots one minute before the scheduled timer expiry on the Active WLC.
The Standby WLC can be rebooted from the Active WLC using the reset peer-system command if a scheduled reset is not planned.
Debug transfer can be enabled on the Active WLC as well as the Standby WLC.
If Active WLC unexpectedly reboot between software download and reboot both WLCs, you need to reboot both WLCs in order to complete software upgrade.
No direct download and upload configuration is possible from the Standby WLC.
All download file types like Image, Configuration, Web-Authentication bundle, and Signature Files will be downloaded on the Active WLC first and then pushed automatically to the Standby WLC.
Once the configuration file is downloaded on the Active WLC, it is pushed to the Standby WLC. This results in the reset of the Standby WLC first, followed by the reset of the Active WLC.
The Peer Service Port and Static route configuration is a part of a different XML file, and will not be applied if downloaded as part of the configuration file.
The download of certificates should be done separately on each box and should be done before pairing.
Uploading different file types like Configuration, Event Logs, Crash files, and so forth can be done separately from the Standby WLC. However, the CLI to configure different parameters for upload like Server IP, file type, path and name should be done on the Active WLC. Once the upload parameters are configured on the Active WLC, the transfer upload peer-start command should be issued on the Active WLC in order to initiate the upload from the Standby WLC.
The service port state will be synched from the Active WLC to the Standby WLC. That is, if DHCP is enabled on the Active WLC service port, the Standby WLC will also use DHCP for getting the service port IP address. If the service port of the Active WLC is configured with a Static IP Address, the Standby WLC also needs to be configured with a different Static IP Address. The CLI to configure the IP Address for the Standby WLC service port is configure redundancy interface address peer-service-port
For more info
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml#upgrade
10-28-2013 08:58 AM
Hi All.
Tks a lot for your help.
The update is done automatically for both unit.
Regads.
Mirko Severi.
12-29-2017 08:18 AM
Is there anyway to do this without taking an outage...
I have 8510's in HA pair formatt running 8.2.160.0 code
12-29-2017 08:20 AM