Forum Discussion
Migrating from BigIP 2000 series to BigIP 2600 series
I Alredy do this stuff for on customer. I propose the following procedure:
- don't connect the new device
- Import the ucs (from old device) to new device:
tmsh load sys ucs platform-migrate no-license: https://support.f5.com/csp/article/K82540512
- Keep the same vlan for internal and external vlan just change selfIP and floating to avoid conflit IP (for both vlan). and change management IP also.
At this momement you retrieve configuration in the new device and all your IP are in the same vlan but with different IP (mgmt, int and ext).
retrieve all your VS IP in order to disable ARP using tmsh like this:
- modify ltm virtual-address 10.1.2.123 arp disabled
- modify ltm virtual-address 10.1.2.119 arp disabled
- modify ltm virtual-address 10.1.2.118 arp disabled
- modify ltm virtual-address 10.1.2.110 arp disabled
- modify ltm virtual-address 10.1.2.109 arp disabled
- ...
And don't forget to save (save sys config), after what you can validate that all your arp in your new device are disabled using GUI (Local Traffic ›› Virtual Servers : Virtual Address List) or CLI, search "arp enabled" in /config/bigip.conf file.
- So now you can connect it to the network.
- connect the other one (2600) set network part with new IP and sync configuration.
At this momement you have your 2 F5 archi (old and new) in your network.
as soon as you want to migrate an application you have just to:
Disable ARP (F5 2000)
modify ltm virtual-address 10.1.2.123 arp disabled
save sys config
Enable ARP (F5 2600)
modify ltm virtual-address 10.1.2.123 arp enabled
save sys config
It's easy to migrate your service and you can go back easly...
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
