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

HarishSolanki's avatar
HarishSolanki
Icon for Altostratus rankAltostratus
Dec 06, 2019

Migration from F5-VE to F5 Hardware i2000 series

I am a novice with F5 BigIP. I am looking for a procedure as to how I can migrate my config from my existing configuration to the hardware appliance. F5-VE has interface names as 1.1,1.2,1.3... and...
application delivery
BIG-IP
bigip_base
F5-VE
migration
TMSH
Stanislas_Piro2's avatar
Stanislas_Piro2
Icon for Cumulonimbus rankCumulonimbus
Dec 11, 2019

The best solution is to :

 

  • Create an archive on VE
  • Configure i2000 with different IP address than VE
  • switch i2000 to OFFLINE mode
  • Configure VE and hardware with sync and failover network on one self IP
  • move Self IP (used for sync) to Allow default on both systems
  • add i2000 in VE trust peers --> Master key is synchronized to new peer
  • create a device group sync-failover with both systems
  • Sync VE to i2000 --> all cluster configuration is synced, including routes, dns, vs, pools
  • failover to i2000
  • disconnect VE vNICs (to fallback, you can restore archive... it will remove cluster configuration)
  • remove VE and i2000 from Device group
  • Remove the VE from i2000 device trust
  • The i2000 is now in Standalone mode
  • move Self IP (used for sync) to Allow None

 

This solution requires both system to be in same TMOS version, same release Point.