Hi, We have successfully downgraded an LTM from 10.2.1 to 9.4.7 in the past. Has anybody completed a similar process from BIG-IP 10.2.3 to 9.4.7? If so, did you run into any issues? Is the following command format still valid? image2disk --format=partitions BIGIP-10.2.3.112.0.iso We cobbled together the process form a couple of knowledge base documents. Is one master document available for this procedure? Thanks in advance!

So, yeah, first bump in the road. when I run image2disk --format=partitions BIGIP-10.2.3.112.0.iso, I receive the following error info: Repository tm_install version/release is 2.7.2/17.0 info: System tm_install version/release is 2.7.1/23.0 info: Updating system tm_install files from BIGIP-10.2.3.112.0.iso .................................................................................... 7362 blocks info: Installer on image is newer, reexec info: Running updated installer. info: Platform id is Mercury Terminal error: Media has multiple products. Install product must be specified. The output from a switchboot -l tells me: Current boot image: HD1.1 - title BIG-IP 10.2.3 Build 112.0 Default boot image: HD1.1 - title BIG-IP 10.2.3 Build 112.0 Available boot image(s): HD1.1 - title BIG-IP 10.2.3 Build 112.0 HD1.2 - title BIG-IP 11.1.0 Build 1943.0 Since we need to downgrade to 9.4.7, can both hd1.1 and hd1.2 be formatted? If so, what tweaks do i nee dot make to that image2disk command? Thanks in advance!

I may have found the solution here: http://support.f5.com/kb/en-us/solutions/public/10000/500/sol10519.html Formatting the file system and installing a base BIG-IP version (10.0.x - 10.2.0) BIG-IP version 10.2.1 onwards image2disk --nosaveconfig --format=volumes For example, the ISO image name is BIGIP-10.2.1.297.0.iso, you would use the following syntax: image2disk --nosaveconfig --format=volumes /shared/images/BIGIP-10.2.1.297.0.iso The current status of the volumes on the unit is: bigpipe software volumes show SOFTWARE - Volumes: +-> SOFTWARE VOLUME HD1.1 Size: default active +-> SOFTWARE VOLUME HD1.2 Size: default inactive +-> SOFTWARE VOLUME HD1.3 Size: default inactive If that works, I'm guessing the next step would be to: * perform an lvscan and expect no output * fix the console if it falls over * scp local-install-9.4.7.320.1.im to /var/tmp/ on the unit * im local-install-9.4.7.320.1.im * manually re-license the unit * configure host name, time zone, etc Has anybody tested that 'image2disk --nosaveconfig --format=volumes /shared/images/BIGIP-10.2.1.297.0.iso' command?

I have done many downgrades from 10.2.x to 9.4.7. both in the lab and in production for various reasons. The easiest way is to create a bootable USB drive with 9.4.7 on it. boot to it and format your HD for version 9 Once the box comes up , re-install the version 9.4.7 UCS file you backed up before going to version 10.x

Hi Nathan, Cheers for the reply. I think I'll brave the non-boot from USB process for now as I cannot get over to the data centre for a while. However, your approach sounds like the cleanest and quickest way to go about this. Thanks!

So, I'm solidering on with formatting the drives to partitions and then downgrading to 9.x via the cli.... and falling at the first hurdle: tmp image2disk --nosaveconfig --format=partitions /shared/tmp/BIGIP-10.2.3.112.0.iso info: Repository tm_install version/release is 2.7.2/17.0 info: System tm_install version/release is 2.7.1/23.0 info: Updating system tm_install files from /shared/tmp/BIGIP-10.2.3.112.0.iso .................................................................................... 7362 blocks info: Installer on image is newer, reexec info: Running updated installer. info: Platform id is Mercury Terminal error: Media has multiple products. Install product must be specified. tmp The device currently has an 11.1.0 image on HD1.2. Could this be the cause fo the above error? switchboot -l Current boot image: HD1.1 - title BIG-IP 10.2.3 Build 112.0 Default boot image: HD1.1 - title BIG-IP 10.2.3 Build 112.0 Available boot image(s): HD1.1 - title BIG-IP 10.2.3 Build 112.0 HD1.2 - title BIG-IP 11.1.0 Build 1943.0

Downgrade from BIG-IP 10.2.3 to 9.4.7

17 Replies

Nathan_Houck_65
Nimbostratus
Jun 06, 2012
I have a few suggestions:

1. To create the 9.4.7 USB drive, I have found that it works best when done from a unit that is already running 9.4.7. Your problem might be the fact you are trying to make a 9.4.7 usb drive on a bigip running 10.x code? Example: In my lab, I would use a box running 9.4.7 to create the 9.4.7 USB drive using the 9.4.7 IM file.

2. Even though its specified that the mkdisk utility is used for version 9.4.7 and up , which in your case, you are going to 9.4.7, so it should work, I would also try the umdinstall utility.

"Beginning in BIG-IP version 9.4.7, the umdinstall utility is no longer supported and has been removed from the BIG-IP installation image files. F5 recommends using the mkdisk utility on a BIG-IP system or a Linux-based system to load a BIG-IP installation image onto a USB mass storage device."

3. I have found that some USB drives work better than others. (I have had good results with kingston)
OttimoMassimo_1
Nimbostratus
Jun 07, 2012
Thanks for the suggestions Nathan.

In the end I rolled the units back to 10.1.0 (booting from USB) and formatted to partitions. I then rolled the units back to 9.4.7 using a .im image uploaded to /var/tmp/.

I found the following documents (amongst others) very useful:

http://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/umd_make_install_9_4_x.html

http://support.f5.com/kb/en-us/solutions/public/10000/800/sol10819.html?sr=21720078

http://support.f5.com/kb/en-us/solutions/public/6000/800/sol6845.htmldownloading

Thanks again for the replies and help!
mbuk2k_59598
Nimbostratus
Nov 28, 2012
Hi,

I know it's been a while but could you let me know if you can remember how you got it to format using partitions when booting from USB? Everytime I try it just forces the disk config to volumes.

Thank you
nitass
Employee
Nov 28, 2012
I know it's been a while but could you let me know if you can remember how you got it to format using partitions when booting from USB? Everytime I try it just forces the disk config to volumes.isn't "diskinit --style partitions" usable?

sol10819: Performing a clean installation of BIG-IP version 10.x or Enterprise Manager version 2.x

http://support.f5.com/kb/en-us/solutions/public/10000/800/sol10819.html
mbuk2k_59598
Nimbostratus
Nov 28, 2012
That worked a treat, thank you.

I've having a similar issue and need to downgrade to 9.4.3, only problem is that the USB made following the instructions for Windows: http://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/umdinstall_9_4_3.html goes through the process, but the BigIP (3400) won't boot from it. It's recognised but nothing gets booted...on with the fun!
OttimoMassimo_1
Nimbostratus
Nov 29, 2012
Hi,

have you followed the instructions here: http://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/umdinstall_9_4_3.htmlrun

Unfortunately, I cannot track down my captures form my work. I was also using 1600 series devices.
nitass
Employee
Nov 29, 2012
have you tried another usb thumb?

sol7088: Hardware requirements for the USB thumb-drive installation

http://support.f5.com/kb/en-us/solutions/public/7000/000/sol7088