This sections describes about the DHCP environment.

Important:

The migration operation is not officially supported on the DHCP based environment. Carefully execute the following approach. Before migration, ensure that the backup is taken and safely stored for all the TCA appliances including TCA-M and TCA-CPs.

As migration retains IP address of source VM (2.3), DHCP makes it difficult to retain the IP as old appliance may not have released the IP even if the VM is powered off. Usually, the DHCP assigns a different IP for the new VM (3.0.0). Therefore, you need to manually perform the following steps:

  1. Do not use e2e-migrate CLI to begin with.

  2. Use deploy CLI to deploy new appliances (not yet powered on).

  3. Note the MAC Address of the new VM.

  4. Create an IP binding rule on the DHCP server to ensure the new VM gets the same IP.

  5. Repeat the step 4 for each VM that is migrated.

  6. Use e2e-migrate CLI without -i option to backup and migrate.

In case revert is needed:

  1. Note the MAC Address of old VM.

  2. Create an IP binding rule on the DHCP server to ensure that the old VM gets the same IP.

  3. Repeat the step 2 for each VM that is being reverted.

  4. Use revert CLI to revert.