Migrating VMware Telco Cloud Automation appliances

Docs

Docs
(current)
VMware Communities

Twitter Facebook LinkedIn 微博

The VMware Telco Cloud Automation versions prior to 2.3 are not supported for the migration. You must first upgrade to 2.3 and then migrate to 3.0.

What to read next

Plan for Migration
When you migrate to VMware Telco Cloud Automation version 3.0, it does not impact your existing 2.3 appliances. The migration deploys 3.0 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.0 appliances. Because the 2.3 setup is untouched, you can revert in case you encounter any errors.
Migration Workflow Diagram
This section describes the flow of migration using the following diagram.
Setup Migration Container
You can choose either of the following two approaches to setup the migration container.
Prepare Input for Migration
The Migration tool requires following inputs for each appliance (TCA-M or TCA-CP) in the given TCA topology.
Run Migration
Once the input is prepared, you can easily migrate an entire TCA deployment topology.
Run Migration without VC Details
It is recommended to use the migration tool for deploying or powering on the appliances. However, you can also manually perform these actions in case the VC is unapproachable or there are firewall issues from the migration container and so on.
Check Status of the Migration
You can check the status of the migration after any phase using the following status CLI command.
Post Migration
After the migration operation is completed, perform the following steps.
Cleaning up after Migrating Appliances
After you migrate your appliances, it is important to perform clean up.
Test
You can manually test the migrated setup or fully migrated setup from TCA-M to see if all the functions are working fine.
Retry Failed Migration
The migration operation is idempotent and re-entrant. If the migration operation fails, you can fix the error and retry the migration using the failed CLI command. If you press ctrl+c or cancel the migration accidentally, retry the migration operation with the same CLI command. When you retry the migration, tool tries to use the new appliance (if already deployed) and performs migration operation on such appliance. In case the issue persists, you can redeploy (delete and deploy new one) appliance by setting forceDeploy field value to True for in the input.json and retry the same CLI command.
Revert
This section describes about the Revert operation.
IPv6
Ensure that the docker is configured with proper stack (IPv6 or IPv4 or both) and the docker container is running on --net host to reach IPV6 addresses.
FTP based OVA Url Path
The OVA URL can accept the FTP path. For reference, see the following sample input json.
DHCP Environment
This sections describes about the DHCP environment.
VMC
If the migration is performed in VMC environments, sometimes OVA upload times out. In this case, you can follow either of the following approaches.

Parent topic: Migrating TCA 2.3.x to TCA 3.0

Resources

Blogs
Careers
Communities
Customer Stories

News and Stories
Topics
Trust Center

Support

Broadcom Support
Documentation
Hands-On Labs
Licensing

Twitter
YouTube
Facebook
LinkedIn
Contact Sales

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries. Accessibility Privacy Supplier Responsibility Terms Of Use

Share on Social Media?

:

|

x

" "?