Scribd
Upload
233 views3 pages

Plan of Action To Upgrade F5 Software Image To BIGIP and Redundancy Test

The document outlines a plan to upgrade the F5 software image on multiple BIG-IP devices while maintaining high availability and redundancy. It involves backing up the configuration, downloading necessary upgrade files, activating licenses, installing the new software version on standby devices, forcing a failover to the upgraded standby, then repeating the process on the other devices. Steps will be taken to sync configurations and monitor devices to ensure services are maintained during the upgrade without loss of traffic or connectivity.

Uploaded by

Milan Lamsal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
233 views3 pages

Plan of Action To Upgrade F5 Software Image To BIGIP and Redundancy Test

The document outlines a plan to upgrade the F5 software image on multiple BIG-IP devices while maintaining high availability and redundancy. It involves backing up the configuration, downloading necessary upgrade files, activating licenses, installing the new software version on standby devices, forcing a failover to the upgraded standby, then repeating the process on the other devices. Steps will be taken to sync configurations and monitor devices to ensure services are maintained during the upgrade without loss of traffic or connectivity.

Uploaded by

Milan Lamsal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Plan of Action to upgrade F5 software image to BIGIP

1) Backup the configuration by generating a UCS archive and download it on a safe place
• System –> Archives –> Create [After being created, download it to a local storage (your PC
or laptop]

2) Generate Qkview of devices before upgradation

3) Download .iso files needed for the upgrade from F5 Downloads

4) Check if need to re-activate the license before upgrading


• Use command >>> grep "Service check date" /config/bigip.license
• If the service check date is earlier than the license check date ( check it on the image in the
download section), the license reactivation is needed by clicking the “Re-activate...” button under
the License section:

5) Upload .Iso file for by browsing from the location where .iso file is downloaded and saved
on both primary and secondary device.
• Log in to the Configuration utility with administrative privileges
• To upload the necessary ISO files, go to System > Software Management
• Select Import.
• Select Browse to select the file to upload from your local computer.
• Select Import.

6) Install an imported file to a new volume or over an existing volume on both primary and
secondary device.
• System > Software Management > Image list.
• Select the box next to the point release image or the hotfix image you want to install.
• Select Install.
• Select an available disk from the Select Disk menu.
• Select an empty volume set from the Volume Set Name menu or type a new volume set name.
• Select Install

7) Force offline (For HA) on Standby Device


• on Standby Device, Click on Standby and then press the “Force offline” button to set the state
to “FORCED OFFLINE”

8) Rebooting to the newly upgraded software volume


• Log in to the Configuration utility with administrative privileges
• Go to System > Software Management > Boot Locations.> HD.x(The one that is to be made
active)
• Select the boot location containing the newly upgraded software volume.
• Select install configuration (YES)
• To restart the system to the specified boot location, select Activate and OK
9) Wait some minutes
• until the device reboots and, afterwards,
• check it booted up correctly, the version number is the new expected one
• and that the configuration is successfully loaded

10) Release offline the upgraded node


• Upgraded node – Release offline

11) Force to standby the non-upgraded node


• Non-Upgraded node – Force to standby

12) Test the new version


• Ensure everything works correctly to proceed to upgrade the other node

13) Upgrade the other node by repeating Steps 7 to 10

14) Make active unit as Standby


• Active Node – Force to standby

15) Test the new version


• Ensure everything works correctly

**** Will follow the same Steps as mentioned above to revert to Current version if any issue is
observed. ***

Device list and the date to be upgraded along with the version details are as follows:

Recommended Version
Device IP Device Name (To Be Upgraded To) Date
172.16.32.110 KTM_ADNS 15.1.5.1 10-May-22
172.16.32.111 KTM_ADNS 15.1.5.1 10-May-22
172.16.32.116 KTM_ADNS (HOST) 15.1.5.1 10-May-22
172.16.32.117 KTM_ADNS (HOST) 15.1.5.1 10-May-22
172.16.32.164 KTM_LB_WAF1.ncell.axiata.com 14.1.4.6 10-May-22
172.16.32.165 KTM_LB_WAF2.ncell.axiata.com 14.1.4.6 10-May-22
172.16.32.166 ktm-lb-2-vcmp10-pri.ncell.axiata.com 14.1.4.6 10-May-22
172.16.32.167 ktm-lb-2-vcmp10-pri.ncell.axiata.com 14.1.4.6 10-May-22
172.16.32.168 ktm-lb-2-vcmp20-pri.ncell.axiata.com 14.1.4.6 10-May-22
172.16.32.169 ktm-lb-2-vcmp20-pri.ncell.axiata.com 14.1.4.6 10-May-22
Performing Redundancy Test:

The upgrade will be performed with zero down time. The high availability of the devices has made it
possible to upgrade one device and switch the traffic to another device in HA till the time the device
comes back online. This also concludes that the devices are successful in redundancy tests. The
following steps will be taken to make sure the same:

Step 1: Sync both the devices: Any pending changes to the primary device will be then pushed to the
secondary and both will have the same configuration running.

Step 2: Upgrade the Standby: After the device’s configuration is identical, the primary device will
continue to listen and handle the traffic while the secondary will install the new upgrade version.

Step 3: Monitor the behavior of Standby Device: After the upgrade the secondary device will be
monitored till it comes up and the basic configuration along with the license will be checked. If it has all
the configuration, then the traffic from the primary will then be forwarded to the secondary. The
services will be checked and if all services are working fine, will move to the next step else revert to the
previous version.

Step 4: Upgrade the Primary: After the redundancy HA device handles the traffic, the primary will be
upgraded and tested following the same steps as Step 2 and 3.

This will conclude that the redundancy test is successful.

You might also like