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
AceDawg_204810's avatar
AceDawg_204810
Icon for Cirrus rankCirrus
Jun 07, 2018

Hi Danny,

 

There's one VERY important question that I don't think has been addressed: what modules are you running on the 2000s? In my experience, the modules may dictate the migration path. UCS, SCF or bigip.conf are your basic options. This is the way I've approached similar migrations in the past:

 

LTM: export SSL certificates and SCF file. Edit SCF file keeping LTM objects

 

LTM and GTM/DNS: export SSL certificates and SCF file. Edit SCF file keeping GTM and LTM objects

 

APM: export UCS file. Verify your interfaces are offline on new environment. Import UCS file using "no-platform-check no-license " options

 

ASM: export ASM profiles. Load ASM profiles to new environment then load LTM objects (see LTM procedure above)

 

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

Hi AceDawg1,

 

Good point. We ony use LTM.

 

I've used the UCS and bigip.conf in the past but, I'm not familiar with the SCF file. Can you explain the SCF method?