When you migrate to VMware Telco Cloud Automation version 3.2, it does not impact your existing 2.3 appliances. The migration deploys 3.2 VMs and configures the new appliances with the same 2.3 configuration including the IP. The migration tool uses 2.3 appliances to read the configuration. The version 2.3 appliances are powered off before bringing up 3.2 appliances. Because the 2.3 setup is untouched, you can revert in case you encounter any errors.
If you are using DHCP based environment, migration is not officially supported because the newly deployed VM does not get the same IP. However, you can migrate to new environment using other methods. For more information, see DHCP environment section.
Before migration, ensure that the backup is taken and safely stored for all the TCA appliances including TCA-M and TCA-CPs.
As the new appliances are deployed on the same host or resource pool and data store of the original appliance, ensure that there is enough CPU, Memory or Disk capacity (depending on the deployment size (Small/Medium/Large/X-Large) of the new appliance.
