Forum Discussion

JustCooLpOOLe's avatar
JustCooLpOOLe
Icon for Cirrocumulus rankCirrocumulus
Apr 07, 2017

Upgrade Question for HA Pair

We currently have a pair of 1600 F5s in a HA configuration. We are looking to purchase either a pair of i2600 or i2800 boxes. My question is really about the easiest way to migrate the configuration. The current 1600s have LTM/APM while the new boxes will have LTM/ASM. We are not really using APM so we aren't going to purchase with the new boxes. If we don't have any Virtual Servers using an APM policy or any other APM functionality, I thought we could turn the primary 1600 into a standalone configuration. Then bring the i2800 online and add it to the 1600 in a HA configuration allowing us to sync the config from 1600 to i2800. Then make the i2800 a primary and convert it to a standalone configuration so we could bring the second i2800 online. Really my questions would be:

 

In a HA configuration, do both boxes need to be the same model? In a HA configuration, do both boxes need to be provisioned with the same modules?

 

In the end, the would have the exact same configuration but just curious about if this a possible route to go?

 

  • The things you need to be careful of is the information NOT in the bigip.conf file. I.e. Things that are specific to each box.

     

    This includes, but is not limited to: Interface Configuration VLAN configuration Config Sync Addresses Management Addresses

     

    HA Models should be of the same model, and ideally have the same modules provisioned.

     

    Having completed a box upgrade previously on a HA Pair, it was actually quite easy to. Force offline Break Trust/Traffic group Down Standby Box Unplug standby box Plug new box in Reestablish Trust/Sync config (You need to have all your VLAN info configured etc.) Failover to new box, test. Rinse repeat etc.

     

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    A HA Group does need the same modules provisioned but can be different platform types. F5's Device Service Clustering also supports n+1 HA groups so you can realistically add the two new devices to the same sync group and then phase out the legacy ones. That being said, things to bear in mind is they will both need a base setup, as Iain mentioned, plus the TMOS versions would need to be the same and, finally, they will have different host names and mgmt IP addresses - so it depends on if this is a requirement.