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

Sokol_69126's avatar
Sokol_69126
Icon for Nimbostratus rankNimbostratus
Jun 23, 2018

Copy Virtuals, pools, nodes, into new environment. Update Ip's

We have been purchased by a new company who wants to migrate all our virtuals into their environment. We have hundreds of these and little time. Is there a good way to export all our virtuals, pools,...
BIG-IP
devops
Jer_O__175899's avatar
Jer_O__175899
Icon for Nimbostratus rankNimbostratus
Jun 23, 2018

Run tmsh sys config file /var/tmp/backup.scf, which generates a single file with all configurations.

 

Set up your new F5 with appropriate routes, VLANS, SNAT pools etc.

 

Install all new SSL certs on the new F5 for every VIP. Don't try to import old ones.

 

Copy any objects you need from backup.scf to a new file, then edit file with needed changes.

 

To test if it will merge correctly with the new F5, run "tmsh load /sys config merge verify /var/tmp/bigip.conf.new". Using verify is crucial, because it doesn't commit the merge. It only tests it.

 

Once merge verify passes, you can run "tmsh load /sys config merge /var/tmp/bigip.conf.new" to commit.

 

Do the same thing for config/partitions/name/bigip.conf if you use them.

 

Jer-O's avatar
Jer-O
Icon for Cirrus rankCirrus
Jun 25, 2018

The other answer recommending the use of the complete config file is a good one if you don't mind configuring your F5 from scratch by editing the system, network and other settings in the config that is generated. If your F5 is already built (sounds like it is), I'd take the more cautious approach I suggested. That said, there's no better method than save /sys config for backing up and restoring to the same F5. I agree with the comment about migrations requiring a lot of knowledge. Your statement about being stuck in a partition gave me some feelings of concern.