Question regarding F5 Viprion Configuration Migration to VE.

I am not able to find relevant documents , Can anyone please share link here ?
I am planning to do parallel setup - Both F5 Viprion Guest & F5 VE will be active at the same time . Will configure F5 VE with different self , floating IP during parallel setup .

Exporting UCS from Viprion & importing on F5 VE . 
Disabling VS on Viprion Guest & Enabling it on F5 VE as per maintenance window .

Is this approach correct ?

There are documents detailing best practices for migrating from vCMP (Virtual Clustered Multiprocessing) to F5 VE. The process typically involves exporting the configuration, installing F5 VE, and re-importing the configuration to the new virtual instance.

snaptube  vidmate   

Hello Avi, 

There's not a "right way" to do it and the answers to your points (more often than not, in my experience) depend on how the customer wants to perform the activity. The way I used to like the most for performing this type of activity was preparing the new unit (VM), planning a maintenance window and migrate the whole appliance at once. 

So, preparation will be:

• discussing with customer if IP addresses (expecially management and vlan-based self-ips) will be moved from old hardware or new one wll be assigned
• deploying and licensing the new unit
• with shut-down traffic interfaces, moving the configuration to the new unit. I used to work directly on the bigip.conf and (eventually) bigip_base.conf because I liked to have more control on which objects I was importing. 
• if you need to import SSL certificates and other files that were importad on the unit (such as external monitors), you will also need an ucs archive from the original appliance.

When performing the activity,

• shut down traffic interfaces on old unit
• clear ARP tables on neighboring devices
• enable traffic interfaces on new unit. you can force a GARP on all interfaces by creatng and removing a dummy vlan with a dummy self-ip. 
• of course, check that traffic levels are consistent with the previous environment, and that service monitors succesfully mark your objects "green" (or red if they were red before)

After the activity,

• if you chose to operate the way I did, it will be faster to rollback/restore services on the old unit if any issue was observed

Hope this helps

CA

As you are in the same DC, one easy option is to create a cluster between vCMP Guest and VE. Then you can sync the configuration and do a failover during a MW.

Another way is to create a ucs file on vCMP Guest
Get master key with "f5mku -K" command

Then on VE run "f5mku -r key_value" command and then import ucs with "no-platform-check" option
check this https://my.f5.com/manage/s/article/K14906