Forum Discussion
NimbostratusUpgrading from version 11.3 HF8 to 11.5.1 HF 5
We are upgrading our LTMs from 11.3 HF8 to 11.5.1 HF5. Under the "installed images" section in Software Management, there are three boot locations (MD1.1, MD1.2, and MD1.3). If I add the base image for 11.5.1 and the Hotfix to two of the three boot locations, I am overwriting 11.3's base image or hotfix. Is there a way to quickly back out if there are issues with 11.5.1 once we have cut over into production? From my understanding, I would have to reinstall the 11.3 hotfix onto one of the 11.5.1 boot locations and boot into that location. My concern is additional downtime outside the maintenance window if we had to back out due to bugs/unexpected results in the application after the upgrade.
Thanks.
15 Replies
shaggyYou need only install 11.5.1 HF5 into one of the non-active volumes, leaving the 11.3 HF8 volume untouched. A back-out is as simple as selecting the 11.3.1 HF8 volume as your boot location and rebooting.
Hi Mnb, The problem isn't entirely clear. Let me offer the following and see if this fits?
Currently your LTM's volumes are:
MD1.1 = 11.3.0-HF8 MD1.2 = ? MD1.3 = ?Future install would appear as:
MD1.1 = 11.3.0-HF8 MD1.2 = 11.5.1-HF5 MD1.3 = 11.3.0-HF10With this configuration, if any issues arise while running on MD1.2 or MD1.3, you could simply boot back to original MD1.1.
Hope this helps, Kevin
Another thing to consider, you may be able to simply add additional volumes depending on your disk size:
tmsh list sys software volume status | grep vol sys software volume HD1.1 { sys software volume HD1.2 { sys software volume HD1.3 { tmsh install sys software image BIGIP-11.5.0.0.0.221.iso volume 1.4 create-volume
mnb_63148Thanks Shaggy and Kevin. Below is what I currently have installed. tmsh show sys software -------------------------------------------------- Sys::Software Status Volume Product Version Build Active Status -------------------------------------------------- MD1.1 BIG-IP 11.3.0 2806.0 no complete MD1.2 BIG-IP 11.3.0 3144.0 yes complete MD1.3 BIG-IP 10.2.0 1707.0 no complete I was previously told by an F5 rep when installing version 11.3, that I needed an 11.3.0 base image installed first before I could apply a Hotfix. It seems that what you are saying is that I do not need a base image for 11.5.1 and that I only need to install 11.5.1 HF5? Thanks.
- boneyard
MVP
you can install a hotfix directly to a volume, it will first install the base image and then the hotfix over it.
Hi MNB, You won't really be upgrading the 10.2 software per say. If you kick off the install from the 11.3.0, it will simply overwrite the 10.2 volume using the 11.3.0 config and the 11.5.0 software. Hope this makes sense. You should end up with:
MD1.1 BIG-IP 11.3.0 2806.0 no complete MD1.2 BIG-IP 11.3.0 3144.0 yes complete MD1.3 BIG-IP 11.5.0 0.0.221 no complete- mnb_63148I should probably clarify. I have LTMs on version 11.3HF8, which is what my first question was regarding. Everyone answered my question in that the base image is rolled into the Hotfix and I do not need to install the base image to a separate volume. The second question was regarding a different LTM that has version 10.2 as the active volume. It looks like this: Sys::Software Status Volume Product Version Build Active Status -------------------------------------------------- MD1.1 BIG-IP 10.2.3 112.0 yes complete MD1.2 BIG-IP 11.1.0 1943.0 no complete MD1.3 none none none no complete I am guessing I can make the same changes and just apply 11.5.1 HF5 to MD1.3 and not have to install a base image for 11.5.1 to MD1.1 or MD1.2 in order for 11.5.1 HF5 on MD1.3 to work. Thanks.
- boneyardon itself that is correct yes. you do need 11.5.1 and 11.5.1 hotfix on the system, the images that is. not installed, but available. and again 10.2.3 to 11.5.1 is big jump, be careful.
- shaggyNote to mnb - the base image is NOT rolled into the Hotfix. If you try to apply a Hotfix to an empty volume, the F5 will automatically install the associated base image IF the base image has been imported into the image list. If the base image is not there, the Hotfix install will hang or error out. So, as boneyard said - you do need 11.5.1 and 11.5.1 hotfix on the system, the images that is. not installed, but available.
Hi MNB, if the install of 11.1.0 is from the 10.2.3 and things went well, I'd recommend kicking off the 11.5.0 install from the 11.1.0 volume. Hope this makes sense.
Kevin
- mnb_63148Thanks, Kevin. The config is actually on the 10.2.3 volume. The box came with 11.1.0, but we downgraded to 10.2.3 at the time because 11.1.0 was still new. Thanks everyone for answering my questions.
- mnb_63148
I just tried installing Hotfix-BIGIP-11.5.1.5.0.147-HF5.iso onto the LTM with 11.3. I received the error below. It looks as though I will need a base image after all which leaves me back to my original concerns of backing out to version 11.3 if I have application issues on 11.5.1. Any thoughts?
- boneyard
not sure how this is going to turn out, it don't see anything except for your original question.
anway, two things are important
the software, you need the base images and hotfix uploaded to your big-ip. you need both.
the volume, you install a base image or hotfix in a volume. you can install a hotfix, the system will first install the base image and then the hotfix in the same volume. this can be done on any volume except the active one. at this stage nothing changes to your big-ip, everything keeps on running.
once you reboot in that other volume only then it becomes active. if you have issues you can always boot back in the previously active one.
that is all that should matter in my opinion.
- mnb_63148
That worked. I had assumed that the base image had to be installed to a volume in order to apply a Hotifx. However, I only had to import the base image so that it showed under the Available Images section and not install it. After importing the base image, I was able to install the Hotfix.
Thanks everyone for the quick responses!
Hi MNB, Glad this went well for you and thanks for letting us know!
Have a great weekend, Kevin
