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

N__197982's avatar
N__197982
Icon for Nimbostratus rankNimbostratus
Jul 17, 2017

Migration of configuration from Physical F5 to a VE F5.

Folks, Can someone provide some guidelines on migrating the entire configuration from a physical F5 device to a VE device? Both the devices are running version "BIG-IP 11.4.1 Build 608.0 Final" as of...
application delivery
LTM
Jad_Tabbara__J1's avatar
Jad_Tabbara__J1
Icon for Cirrostratus rankCirrostratus
Jul 17, 2017

Hello,

I've done it last friday. I got many issues so I recommand you to :

1) Generate a SCF (Single Configuration File) of your physical BIG-IP

2) The SCF will generate a .tar archive, and another file. Copy both file to your VE to /var/local/scf The .tar contains all certificates, keys and other static files.

3) Create manually the network and system configuration on your new VE BIG-IP (Keep exactly same name for VLAN and other objects)

Note: Disconnect all NICs adapters of your VM, to avoid having duplicate IP address when setting the SELF IP or Management IP (or use a different management IP address)

4) Create a backup or a snapshot of the VE. If needed, you will use it to return to this state.

5) Launch the command 

tmsh load sys config file "name_scf_file" verify

6) Correct errors and launch the command again. Repeat this step... Once you have done with all errors, you can launch the same command without "verify"

Hope it helps