Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

portoalegre's avatar
portoalegre
Icon for Nimbostratus rankNimbostratus
Oct 25, 2018

BigIP migration tool

I intend using F5's Migration tool to migrate a new F5 hardware LTM pair into my current F5 LTM pair cluster in order to migrate configurations with ease and bring new hardware online, old hardware o...
application delivery
LTM
Andy_McGrath's avatar
Andy_McGrath
Icon for Cumulonimbus rankCumulonimbus
Oct 25, 2018

You will need to configure local Self-IP addressing yourself as the migration method you have shared is to create a new device service clustering (DSC) between the devices.

However, you can simply configure the VLANs and a single Self-IP to be used as the Config Sync address to get the configuration copied/synced over to the new device then break the DSC (making sure the new device is offline in some way) then take the Self-IP configuration from the 

bigip_base.conf
configuration file and do a configuration merge in TMSH.

Then you migration cut over can be to simply take the old F5 off-line (recommend off the network by shutting down the interfaces) and bring the new F5 BIG-IP online.

I also highly recommend looking at running the BIGdiff (https://devcentral.f5.com/codeshare/bigdiff-1160) tool to assist with checking the status of Virtual Servers and Pools etc during the migration.