Forum Discussion

Dazzla_20011's avatar
Icon for Nimbostratus rankNimbostratus
Jul 27, 2011

LTM Upgrade from 10.1.0 to 10.2.2




Next week I'll be upgrading our LTMs from version 10.1.0 to version 10.2.2 Hotfix1. I've not upgraded a Big-IP device before so I'm after an advice users feel would help the upgrade run smoothly. From my understanding the upgrade procedure is as follows.



Download and import the image and hotfix to the device


Install the image and hotfix to a volume. I'm OK to overwrite one of the versions which isn't used.


Go to Boot Locations and Activate version 10.2.2




Before the upgrade I plan to take a ucs backup.



Anything else anyone would recommend?



Many Thanks




3 Replies

  • You can import the image and hotfix through the GUI, otherwise, make sure they are in the /shared/images directory on box.



    Before upgrade, I would use the md5sum command on the CLI to make sure the md5 hashes match the md5 files from the F5 download website. The md5 hashes shown in the GUI are not accurate.
  • Be sure you have console access to the devices before upgrading so that if something goes wrong you can use the console to boot back to the original volume.



    Make sure before you load an image into a volume that you re-activate your licenses. I believe it states this in the upgrade doc, but make sure you do it before loading the image on the volume or you may have troubles booting from it.






  • if u wanna use cli,



    1/ upload 10.2.2 and 10.2.2 hf1 to /shared/images.



    2/ verify whether bigip detects 10.2.2 and 10.2.2 hf1 by running b software images and b software hotfixes



    3/ install 10.2.2 hf1 to another slot e.g. hd1.3


    b software desired HD1.3 product BIG-IP version 10.2.2 build 852.0



    4/ check installation status by running b software or watch b software



    5/ when finishing, active the new slot e.g. hd1.3


    b software desired HD1.3 active enable





    *existing config will be forwarded to new slot automatically


    **unit will be rebooted automatically after running command in step5