Forum Discussion
CirrusMigrating from BigIP 2000 series to BigIP 2600 series
NimbostratusHi 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)
CirrusHi AceDawg1,
Your assumptions are correct. Our F5 is not the default gateway for any of our devices, but good point. I like your approach, but just so I understand correctly, your approach will start after I run the initial config of the 2600's, correct?
From what you are describing, the SCF file is very similar to the bigip.conf file. Why choose the SCF file and not the bigip.conf file to make the changes?
When merging the SCF file, I would rather not change the VS ips because I don't want them to atart ARPing (on the new F5s) and causing havoc. I would like to change the IPs of our VS one by one until we are done with them all. Would that work?
