Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

Upgrade LTM/ASM software from 11.2 to 11.6

Hi, We are planning for a BIG IP software version upgrade from 11.2 HF7 to 11.6.

I would like to follow a procedure that is best suited for a software upgrade aiming towards 11.6.

Any suggested method that have been tested and implemented before would be highly appreciated.

Current Software : BIGIP-11.2.0.2446.0.iso Currnet Hotfix: Hotfix-BIGIP-11.2.0-2747.0-HF4.iso

Cheers.

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I was going from 11.4 to 11.6, but it's probably very similar. One problem I had was I had to resize the MD1 volume. This may be particular to my hardware (not sure) but doing the following resolved the issue:

modify /sys disk logical-disk MD1 vg-reserved 10000

This was the error in question:

: "/usr/bin/tmsh -n -g load sys config partitions all" - failed. -- 01071008:3: Provisioning failed with error 1 - 'Disk limit exceeded. 16188 MB are required to provision these modules, but only 0 MB are available.' . Unexpected Error: Loading configuration process failed.

I had plenty of available disk.

R. Marc

1
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

You shouldn't have any issues, just follow the steps documented in the release notes.

https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-6-0.html#rns_upgrade

0
Comments on this Answer
Comment made 26-Oct-2014 by Moinul Rony 113
Thanks for that. I am going through the installation checklist and just to confirm Prior to upgrade should I put the backup UCS file in /var/local/ucs/ on both Unit ? Also it asks to disable mirroring, where do I fins the option to do that. I have went in System > HA and I can only see Primary and Secondary Mirror address. To disable mirror should I need to set them both to "none" ? Also is it possible to install the Software image and hotfix on a live LTM , does a software/HF install restart the unit automatically? Cheers.
0
Comment made 26-Oct-2014 by Moinul Rony 113
Also we have several custom bash scripts running from the units. Does a software upgrade removes them as it will live on a different volume ? Can we access these files after we load the unit in the new Software ? Cheers.
0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

All good questions, I have a pretty good prcedure but we have a spare set of appliances we run our upgrades on using the original UCS files. The only way for sure to know if your scripts are still there will be to do a test upgrade or upgrade the standby and give it a good checkout. I can share my upgrade instructions if you let me know where to send them or post them. Our last upgrade was from 11.2 to 11.5.1 so it should be similar. I can tell you if you are using any HTTP classes you have to get rid of them before you upgrade or you will have several problems. Tiy can create the new boot volumes directly from the Hot fix image on the standby to be safe.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hello afedden, we are preparing to upgrade our LTMs from v 11.3 to 11.6. I would be interested in taking a look at your upgrade testing documentation if you are willing to share. We have an active/standby VE pair I can use for testing.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Not sure how this will paste but I will try I like to relicense and build the volumes ahead of time and then let our 2nd level team finish the upgrade so that why I do it this way. It just saves us a lot of time so when the change window starts we can have the standby upgraded and ready as soon as the change window starts

Prod F5 11.5.2 or HFx upgrade Prerequisites done by f5 support team prior to change window, FYI only: • Make sure to place the code and hot fix on the devices prior to the implementation date • Suppress the F5s or you will create tickets during the relicense!!!!!!!! • Relicense each F5 LTM that’s getting worked on • Create a new BOOT volume on each F5 using existing code and a simple name like MD1.1 or MD1.2 no extra information!. This way you are creating a current Boot volume if needed for recovery. Remember the volume you create incase reversion is needed. The boot volume creation is described in Step 4 but this volume should use the same code version that’s running before the upgrade. (we do this a few hours prior to the actual upgrade) • Once the new volume is created create the new volume using the new code and hot fix • Make good notes on the volume numbers as the Implementation team will need this information on the night of the change To create the new boot volume for 11.5.2 HF1 : • Navigate to System ›› Software management ›› Hotfix list Note: The Hotfix install will install the base image, prior to the HF. • Select Check box next to Hotfix-BIGIP-11.5.2.1.0.169-HF1.iso • Select the boot volume your using, example is MD1 and use Volume 2 (use a number that’s not already built) This example is using MD1.2
• Click Install when the MD1.2 is selected . Monitor the progress bar for Boot location you are using. When this is done Step 5 will push the fresh configuration to this pre built volume so it has the latest changes

Implementation team instructions start here

• Stop monitoring of both F5 appliances and the distribution switches in this office for the duration of the change window. • Before upgrading make sure the device is in SYNC . Sync them if needed. • Notify 2nd level NOT TO MAKE CHANGES WHILE YOU ARE DOING THIS UPGRADE! Step 1. Change Prerequisites (backup/archive): a. Login to the F5 devices: https://yourF5-primary.org https://yourF5-standby.org b. Sync FROM the active node. c. Navigate to System ››Support d. Create and Collect QKViews from both devices.
NOTE: If the Snapshot file already has the Download Snapshot option, delete it to create a fresh Qkview. This takes several minutes. When done, download the qkview to your workstation. This file can be useful if we have post upgrade problems. It documents all VIPs, pool and nodes and the state they were in prior to the upgrade. We can compare the pre and post upgrade QKViews to see what changed. Now create a fresh backup on both the Active and Standby. e. Navigate to System ››Archive f. Click Create to and collect a new Archive (name the file PreUpgrade) g. Once back at the Archive screen, click on the new Archive you created. h. Click Download to save a local copy of the Archive. Step 2. Upgrade the STANDBY device:

From the command line on the standby access the tmsh shell if not already in it. Then run the following tmsh commands run /sys failover offline save sys config verify from the GUI That the standby is now showing forced offline in upper left corner of GUI

Step 4. Update the restore volume you created in the beginning. The restore volume has the same code as what is running now and this process just copy’s the running config to the restore volume just in case we need to revert On the stand by from the bash shell. If you are in the tmsh shell the command is run util bash to get to the bash shell. Here is an example of what it looks like when the 11.5.1 code is running in MD1.3 and you need to copy the running config to MD1.5 volume to update the restore volume 1st this command shows you where the software is located and the version info.

[userx@yourF5 Standby:Changes Pending] ~ # tmsh show sys software

Sys::Software Status

Volume Product Version Build Active Status

MD1.2 BIG-IP 11.5.2 1.0.169 no complete MD1.3 BIG-IP 11.5.1 4.8.128 yes complete MD1.5 BIG-IP 11.5.1 4.8.128 no complete

[userx@YourF5:Standby:Changes Pending] ~ # Here is the command and what the output should look like to [ROOT@YOURF5:ACTIVE:IN SYNC] CONFIG # cpcfg --source=MD1.3 MD1.5 INFO: GETTING CONFIGURATION FROM MD1.3 INFO: COPYING CONFIGURATION TO MD1.5 INFO: APPLYING CONFIGURATION TO MD1.5

When the copy is done go to next Step   Step 5. When the restore volume copy is done (about 3 minutes) now update the new code volume so it has the most recent changes. Here is an example of what it looks like when the 11.5.1 code is running in MD1.3 and you need to copy the running config to MD1.2 where the new 11.5.2 code image is. 1st this command shows you where the software is located and the version info.

[userx@YOURF5:Standby:Changes Pending] ~ # tmsh show sys software

Sys::Software Status

Volume Product Version Build Active Status

MD1.2 BIG-IP 11.5.2 1.0.169 no complete MD1.3 BIG-IP 11.5.1 4.8.128 yes complete MD1.5 BIG-IP 11.5.1 4.8.128 no complete

[userx@YOURF5:Standby:Changes Pending] ~ # Here is the command and what the output should look like to copy config to the 11,5,2 volume. [ROOT@YOURF5:ACTIVE:IN SYNC] CONFIG # CPCFG --SOURCE=MD1.3 MD1.2 INFO: GETTING CONFIGURATION FROM MD1.3 INFO: COPYING CONFIGURATION TO MD1.2 INFO: APPLYING CONFIGURATION TO MD1.2

When this is done go to > Step 6

Step 6. Now you are ready to activate the new code Boot into the new Boot Location: a. Navigate to System ›› Software Management : Boot Locations b. Select MD1.2 to activate code. (Should be the volume you updated that has the new code) c. Click on activate and confirm when prompted

This will take up to 25 minutes, when the GUI comes up wait another 5 minutes and then connect and move to next Step Step 7. Verification:
• Verify the code is 11.5.2 hf1 Navigate to System ›› Configuration : Device : General • Verify the version is
Version Is BIG-IP 11.5.2 Build 1.0.169 Hotfix HF1

Now verify the VIPs, nodes and pool counts match the pre upgrade counts using the information collected prior to the upgrade. Navigate the GUI to Local Traffic ›› Virtual Servers Set the partition setting to All, Click on the Status pull down and change to offline Verify the same VIPs and Pools and Nodes that were offline before the change are still offline and no new offline objects are listed. (unless they are down for scheduled maintenance). Step 8. STANDBY COMPLETE – Release from OFFLINE to Online a. Connect to the Offline (now on version 11.5.2 hf1) F5 appliance b. Click on the Forced Offline link,
c. Scroll to bottom of window and Click Release offline d. Confirm NOTE: the device status should change to Online Standby and the other node will remain Online Active. (We have seen in lab the upgraded box becomes active and the non upgraded box goes standby)

Start application Checkouts!!!
*2nd box upgrade starts here after a few successful check outs

Step 9. With the upgrade done on the 1st unit. Upgrade the next device:

From the command line on the standby, from the tmsh shell take the standby offline. From tmsh run /sys failover offline save sys config verify from the GUI the standby is now forced offline

Step 10. Update the restore volume. The restore volume has the same code as what is running now and this process copy’s the running config to the restore volume just in case we need to revert On the stand by from the bash shell. If you are in the tmsh shell the command is run util bash to get to the bash shell. Here is an example of what it looks like when the 11.5.1 code is running in MD1.4 and you need to copy the running config to MD1.5 volume to create the restore volume 1st this command shows you where the software is located and the version info.

[userx@YOURF5:Standby:Changes Pending] ~ # tmsh show sys software

Sys::Software Status

Volume Product Version Build Active Status

MD1.2 BIG-IP 11.5.2 1.0.169 no complete MD1.4 BIG-IP 11.5.1 4.8.128 yes complete MD1.5 BIG-IP 11.5.1 4.8.128 no complete

[userx@YOURF5:Standby:Changes Pending] ~ # Here is the command and what the output should look like to [ROOT@YOURF5:ACTIVE:IN SYNC] CONFIG # cpcfg --source=MD1.4 MD1.5 INFO: GETTING CONFIGURATION FROM MD1.4 INFO: COPYING CONFIGURATION TO MD1.5 INFO: APPLYING CONFIGURATION TO MD1.5 When the copy is done go to next Step

Step 11. When the restore volume copy is done (about 3 minutes) now update the new code volume so it has the most recent changes. Here is an example of what it looks like when the 11.5.1 code is running in MD1.3 and you need to copy the running config to MD1.2 where the new 11.5.2 code image is. 1st this command shows you where the software is located and the version info.

[userx@YOURF5:Standby:Changes Pending] ~ # tmsh show sys software

Sys::Software Status

Volume Product Version Build Active Status

MD1.2 BIG-IP 11.5.2 1.0.169 no complete MD1.4 BIG-IP 11.5.1 4.8.128 yes complete MD1.5 BIG-IP 11.5.1 4.8.128 no complete

[userx@YOURF5:Standby:Changes Pending] ~ # Here is the command and what the output should look like to copy the running config to the 11.5.2 volume. [ROOT@YOURF5:ACTIVE:IN SYNC] CONFIG # cpcfg --source=MD1.4 MD1.2 INFO: GETTING CONFIGURATION FROM MD1.4 INFO: COPYING CONFIGURATION TO MD1.2 INFO: APPLYING CONFIGURATION TO MD1.2 Wait for the copy to finish,

Step 12. Now you are ready to activate the new code Boot into the new Boot Location: d. Navigate to System ›› Software Management : Boot Locations e. Select MD1.2 to activate code. (Should be the volume you updated that has the new code) f. Click on activate and confirm when prompted

This will take up to 25 minutes, when the GUI comes up wait another 5 minutes and then connect and move to next Step   Step 13. Verification:
• Verify the code is 11.5.2 hf1 Navigate to System ›› Configuration : Device : General Verify the version is BIG-IP 11.5.2 Build 1.0.169 Hotfix HF1

Once the node comes back online verify the VIPs, nodes and pool counts match the pre upgrade counts. Using the information collected before the upgrade compare the object status.. Navigate the GUI to Local Traffic ›› Virtual Servers
Set the partition setting to All, Click on the Status pull down and change to offline Verify the VIPs, Pools and Nodes status matches the pre upgrade status for offline and unavailable matches what we saw before the change. Step 14. STANDBY COMPLETE – Release from OFFLINE to Online e. Connect to the Offline (now on version 11.5.2 hf1) F5 appliance f. Click on the Forced Offline link,
g. Scroll to bottom of window and Click Release offline h. Confirm NOTE: the device status should change to Online Standby and the other node will remain Online Active. (We have seen in lab the upgraded box becomes active and the non upgraded box goes standby)

Step 15. Upgrade COMPLETE Notify your customers

0