Forum Discussion
5 Replies
- amolariCirruswhich error? Probably there are some changes to perform in the Network part of the configuration (the vCMP guest doesn't have access to the physical interfaces as the HW BIGIP)
Hi!
We have recently migrated from BIGP 3600 to 5250 VCMP. I have created a deployment guide that shows how we did the migration successfully. Se below:
How to migrate a UCS archive to a different BIG-IP platform type
Before you begin:
- Provision the Plattform as a vCMP host, create a new guest that matches the version for wich you have the 11.x UCS to be migrated. - Sync the config between current Active and Standby devices. - Create an UCS archive from both devices using the GUI and copy the file to a safe place. - Set the Standby device to “Force Offline” and then shutdown the device.
-
Obtain the master key from the platform you want to migrate the configuration. SOL9420
- f5mku -K
-
Create a UCS archive from the platform you want to migrate the configuration and SCP the file to your computer.
- tmsh save /sys ucs /var/local/ucs/MyUCS.ucs
- scp MyUCS.ucs username@yourcomputer:/tmp
-
Excract the bigip_base.conf file from the UCS archive and:
- remove stp configuration
- remove trunk configuration
- remove interface references from vlan configuration
- remove lacp configuration
-
Repack the UCS arhive with the modified bigip_base.conf file.
-
SCP the UCS file to the platform you want to install on. (/var/local/ucs)
- scp MyUCS.ucs root@ip-new-platform:/var/local/ucs
-
Log in to the NEW platform system command line.
-
Install the master key that you copied in step 1 using the following syntax:
- f5mku -r
-
Verify that the master key is the same on the active device and the NEW platform using the following command on both systems:
- f5mku -K
-
Restore the UCS file to the NEW platform using the following syntax:
- tmsh load sys ucs .ucs no-license no-platform-check
-
To save and load the configuration, and to ensure no errors, type the following commands from the NEW platform system command line:
- tmsh save sys config
- tmsh load sys config verify
- tmsh load sys config partitions all
-
Reboot the device
-
Rollback plan
- Shut down the new Devices and enable the switchports for old Devices. We are then back to normal with the solution as before we started.
-
- helyousa_337216Nimbostratus
Hello,
I read that f5mku -r is not recommanded in vcmp environments. Can you confirm please ? Did you have some troubles ?
We had no problem using "f5mku -r", it workd fine.
- helyousa_337216Nimbostratus
Hello, thank you for your answer. I tried and i can say that f5kmu -r worked but tmsh modify sys crypto master-key prompt-for-password didn't work well, but it created some bad behaviors.
What it's surprising, is that there is a kb from f5 that recommends tmsh modify sys for vGuest.