For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Danny_Arroyo's avatar
Danny_Arroyo
Icon for Cirrus rankCirrus
Jun 07, 2018

Migrating from BigIP 2000 series to BigIP 2600 series

We currently have a BigIP 2000 LTM HA pair running v12.1.3.3 (we will be upgrading to 13.x soon). We purchased a comparable BigIP 2600 LTM HA pair. We are planning a migration to the 2600.   ...
application delivery
BIG-IP
LTM
Lee_Sutcliffe's avatar
Lee_Sutcliffe
Icon for Nacreous rankNacreous
Jun 07, 2018

Hi Danny,

 

If you wish to migrate to a device but change some of the configuration I would probably not use an archive of SCF to restore the new device.

 

I would build the new device pair in isolation, configure your VLANS, trunks, self IPs, gateways, configure HA etc Then take a copy of the bigip.conf file from your existing device. Take this file offline to edit the IPs and VLANs and anything else that may change when deployed on the new kit.

 

Copy the edited file to one of your new devices and run a merge verify command to see if there are any errors.

 

tmsh load sys config file /var/tmp/edited-bigip.conf merge verify

 

Work through any errors if there are any, if all is good - run the same command without the verify and sync to the peer.

 

When you're ready, you can enable the VLANS on the F5 or local switch to cut over when you migrate.

 

Lee