V9.2.1 to 10.2.1 active/passive

Hi fellows , I am planning to upgrade pair of bigIp LTM v9.2.1 to v10.2.1 setup in active/passive.

following are steps I consider to perform Please share me your thoughts if some point/step if missing or important to consider

1-Remove the passive unit from Active/Passive setup (HA is setup through serial cable).Disconnect it from active unit. Make sure all traffic still continue through active unit.

2- Copy the following files to /shared/images to passive unit :

-local-install-9.3.1.37.1.im

-local-install-9.3.1.37.1.im.md5

3- Start installation

4- After Installation, from the webGUI check the status of the virtual servers,

pools and pool members and check that the configuration includes any configured iRule,

SSL certificates and profiles those were present prior to the upgrade.

5- Copy the following files to /shared/images on same passive unit:

- BIGIP-10.2.1.297.0.iso

- BIGIP-10.2.1.297.0.iso.md5

6- Start installation

7- After Installation, from the webGUI check the status of the virtual servers, pools and pool members and

check that the configuration includes any configured iRule, SSL certificates and profiles that were present prior to the upgrade.

Once passive unit is upgraded with v10.2.1 replace it with Active unit. will check the flow

of traffic through v10.2.1 for some time if everything goes fine then we will repeat the above similar

steps for second unit (Active one) & after that we will setup both units in similar Active/Passive units.

Please confirm one question:

As unit contain two H.D1.1 & 1.2 Current software is install on H.D1.1, If I install new image on H.D1.2 and keep safe old image.Though this I can achieve dual software on single unit

H.D1.1= v9.2.1

H.D1.2= V10.2.1

Regards

In order to install 10.2.1 you will need to re-format because the v9 partition sizes are not big enough for v10 (this saves config). Here’s an SOL about installing 9 and 10 on a partition formatted system: 404 Page not found | BIG-IP Documentation

If you don’t _need_ to run v9 and v10 on the same device, you should probably just format to volumes (suggested) and just run v10 only.

When you unplug that serial cable, both of your devices are going to go active unless you have network failover configured. Regardless of that though, network failover is not compatible between those versions: 404 Page not found | BIG-IP Documentation

One thing to watch out for issues with change in behaviors from version 9 to version 10. Here are two important ones that I know:

FTP Virtual Servers: 404 Page not found | BIG-IP Documentation

HTTP 1.1 Monitors: 404 Page not found | BIG-IP Documentation

Many thanks , I will try first on our test box then will do live upgrade !!!

if you have irules with datagroups (classes) there is a change between 9.x and 10.x that can potentially get you as well. Please read Colin’s excellent article on the introduction of the class command for details:

http://devcentral.f5.com/Tutorials/TechTips/tabid/63/articleType/ArticleView/articleId/2309/v10\-\-New-class-features-in-iRules.aspx Click Here

1. disconnect unit from pair

2. re-activate license

3. backup config i.e. ucs file

4. upgrade to 9.3.1

im local-install-9.3.1.37.1.im

5. verify if config can be loaded properly. if there is any issue, u may run b load which will display the error.

b load

6. backup config i.e. ucs file

7. upgrade to 10.2.1

im BIGIP-10.2.1.297.0.iso

image2disk --format=volumes BIGIP-10.2.1.297.0.iso

sol12561: Change in Behavior: The image2disk utility --instslot and --format options are now mutually exclusive

8. verify if config can be loaded properly. if there is any issue, u may run b load which will display the error.

b load

as others mentioned, there are some change in behavior in 10.x, these are some.

sol9947: Change in Behavior: The Peer Management Address setting is required for BIG-IP version 10.x systems configured for network failover

sol2167: Constructing HTTP requests for use with the HTTP or HTTPS application health monitor

9. backup config i.e. ucs file

for 9.2.1, i never installed 9.2.x on 10.x partition. pls feel free to test it.

sol7608: Choosing a partition scheme when upgrading BIG-IP software to version 9.3.1 or 9.4.2 through 9.4.8

cheer!

Thanks nitass ,i am getting above error when i tried to upgrade from 9.3.1

on step 7 , when I execute im BIGIP-10.2.1.297.0. ISO I receive following error

/usr/bin/upgrade_rpmdisk: line 12: /tmp/rpmdisk.Nqzvfk/bin/pre-upgrade: No such file or directory

I have already copied BIGIP-10.2.1.297.0 to shared/images folder. And when I run image2disk command I received -bash: image2disk: command not found

I have also test the command image2disk on one unit running 10.2.1 it successfully run test back out procedure

Any thoughts.?

Thanks

[root@abcuk:Active] images ls

BIGIP-10.2.1.297.0.iso local-install-9.3.1.37.1.im

[root@abcuk:Active] images im BIGIP-10.2.1.297.0.iso

/usr/bin/upgrade_rpmdisk: line 12: /tmp/rpmdisk.7UAPxA/bin/pre-upgrade: No such file or directory

[root@abcuk:Active] images

Any thoughts on this error ?

Many thanks

is the iso file corrupted?

is its md5 correct?

cheer!

I found this error as CR116950 which is later on fix but not sure why not working for 10.2.1 anyhow I replace it with BIGIP-10.2.2.763.3 which is working . every thing went well but strange Initially I am able to logged in as default password. but once I restart the hardware admin password is working on default while root password is not working as default so I change the root password ( mount -a ) following procedure save successfully but nor working :frowning: drive me crazy :frowning:

have u tried password which is used in 9.2.1? i understand it should be rolled forward to 10.2.2.

anyway, if it doesn’t work. since admin user works, why won’t u change root password via webui i.e. system->platform?

about CR116950, i understand it’s on v9 iso file but u r using v10 iso file. anyway, glad to hear it worked fine in 10.2.2. :slight_smile:

nitass im surprised I can only see admin password change option in system->platform even have seen many time in 9.x and 10.X system->platform contain both admin/root password change/upgrade option available. May b for this unit root file corrupt ?? im stuck if I need to install different OS how can I copy through winscp as root account is not working

I can only see admin password change option in system->platform

r u using appliance mode?

sol12815: Overview of Appliance mode

Nitas unit is not using appliance mode , I have checked License screen in the Configuration utility , please see below I have reset root password & updated successfully. but when I reboot or exit that terminal it wont take changed password

logname: no login name

sh-3.2 mount -a

sh-3.2 passwd root

Changing password for user root.

New BIG-IP password:

Retype new BIG-IP password:

Changing password for user root.

passwd: all authentication tokens updated successfully.

sh-3.2

Abcuk.com login: root

Password:

Authentication

BIG-IP 10.2.2 Build 763.3

Kernel 2.6.18-164.11.1.el5.1.0.f5app on an i686

How can I do again clean installation ? as not able to login root account ?

Any thoughts ?

Thanks

How can I do again clean installation ?

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

hello I am using this sol for reverting software 10.2.1 to 9.3.1

when I tried to create non LVM partition its give me below error

image2disk --instslot=HD1.2 --format=partitions BIGIP-10.2.1.297.0.iso

Terminal error: You cannot specify the target location when using the format option.

or If I use volume instead target location

image2disk --format=volumes BIGIP-BIGIP-10.2.1.297.0.iso

It formate and install 10.2.1

But for moving back to 9.3.1 ( non LVM )

I execute im local-install-9.3.1.37.1.im

receive this message.

This system is using logical volumes for disk management,

but the media you are using (/shared/images/local-install-9.3.1.37.1.im) does not contain an LVM-aware product.

If you need to install non LVM-aware products, please refer to SOL9745.

This system will first need to be reformatted into a partitioned layout.

Note that the ‘image2disk’ utility cannot be used to install releases

earlier than 10.0.0 or 9.6.1.

Any thoughts how can I move back ( reverting ) 10.2.1 to 9.3.1 and then 9.3.1 to 9.2.1 please suggest.

Thanks

you cannot just format a single volume in LVM to be a partition, if going back to the partitions of 9.x, you must format the whole disk.

Jason image2disk --format=volumes BIGIP-BIGIP-10.2.1.297.0.iso does format the whole disk ?

Is there other way to format whole disk ?

If you want 9.x and 10x images, you have to use partitions, not volumes. As sol 9745 indicates, this requires formatting the entire disk as partitions instead of volumes. You cannot specify a destination (--instslot=HD1.2) when choosing a partition format. Remove that and that should eliminate the terminal error.

Hi all thanks for support upgrade remain well without any issue following are steps used for activity…

Passive unit:

1)save the config using: bigpipe config save /config.ucs

2)Copy v9.3.1 (local-install-9.3.1.37.1.im ) image file to /var/tmp

3)Execute installation using: im local-install-9.3.1.37.1.im

4)Verify config files using: ‘bigpipe load’ once V9.3.1 installation completed successfully

5)Copy v10.2.1 (local-install-9.3.1.37.1.im ) image file to /var/tmp

6)save the config using: bigpipe config save /config.ucs

7)Execute installation using: image2disk --format=volumes BIGIP-10.2.1.297.0.iso

8)Verify config files using: ‘bigpipe load’ once V10.2.1 installation completed successfully

Similar steps used for Active unit…