Working together with NSX Migration Coordinator for V2T Migration, the Workload Migrations for NSX V2T service supports the lift-and-shift of virtual machine workloads from NSX for vSphere environments to more flexible and feature rich NSX environments.

Workload Migrations for NSX V2T combines the wave orchestration and operational capabilities of HCX with the performance and the concurrency characteristics of HCX Assisted vMotion to expedite virtual machine migration. Workload Migrations for NSX V2T supports the lift and shift of NSX for vSphere workloads.

HCX Integration with NSX Migration Coordinator for V2T Migration

Workload Migrations for NSX V2T integrates with NSX Migration Coordinator to migrate seamlessly virtual machines and correctly maintain their security state. This integration is applicable when running User Defined Topology Configuration and Edge Migration mode from an NSX for vSphere cluster to an NSX cluster.
Note: In clustered NSX environments, you must register HCX Connector with the node where NSX Migration Coordinator has been initiated.

Workload Migrations for NSX V2T leverages the bridging capability created by NSX Migration Coordinator for virtual machine connectivity on the logical segment during the transition from NSX for vSphere.

vCenter Server Topologies

The Workload Migrations for NSX V2T service is designed for specific migration topologies within the data center:

  • Single vCenter Server cluster to cluster migrations (NSXv-cluster to NSXT-cluster).
  • Cross-vCenter Server migration (NSXv-VC to NSXT-VC).
  • Federated NSX architectures.

In the single vCenter Server migration topology, the HCX Connector Compute Profile configuration must contain the NSX-V prepared source cluster while the HCX Cloud Manager Compute Profile configuration contains the NSX-T prepared cluster.

For all topologies, HCX registration with the vCenter Server and local NSX Manager remains the same for both the HCX Connector and HCX Cloud Manager. This registration is done during HCX Manager installation.

For Federated NSX architectures, apart from registering the HCX Manager with the local NSX-T manager at installation, you explicitly configure HCX Cloud with the Global Manager that is running the V2T Migration Coordinator in addition to the Local Manager. See Configure NSX V2T Migration for Federated NSX Architectures.

How it works

The Workload Migrations for NSX V2T service workflow has three general phases: pre-migration workload configuration, HCX migration, and post migration clean-up. NSX Migration Coordinator for V2T Migration handles the pre-migration and the post-migration operations, which are outside the scope of this document. For information regarding the NSX Migration Coordinator configuration, refer to the section "End-to-end Workflow of Configuration and Edge Migration," in Configuration and Edge Migration Workflow.

The migration phase for Workload Migrations for NSX V2T is similar to other HCX migration types except that no target network mapping in the HCX UI is necessary for the workloads. One exception is standard port groups, which require the network mapping to be done manually in the HCX Migration wizard. Workload Migrations for NSX V2T obtains the network mapping information through API calls to NSX Migration Coordinator.
Note: All API calls to Migration Coordinator are at the group level. For example, a request for mapping information gets the information for all VMs in the group. Any changes to individual VMs in the group after this API request are not allowed.

You initiate the Workload Migrations for NSX V2T service from the HCX Connector migration interface by selecting V2T-Migration at the group level.

The Workload Migrations for NSX V2T service has the following high-level workflow:

  1. Complete the pre-migration configuration steps using NSX Migration Coordinator for V2T Migration.
  2. In the HCX Connector migration interface, create Mobility Groups for the selected workloads.
  3. Select the V2T-Migration for the Mobility Group and configure available Transfer, placement, and extended options.
  4. Validate the configuration. At this point, Workload Migrations for NSX V2T makes API calls to Migration Coordinator to identify the source and target network mapping and identify the incoming groups of VMs.
  5. Start the migration.
  6. HCX begins consuming the pre-configuration migration settings for the VMs and begins migrating VMs.
  7. HCX makes post migration API calls to the NSX Migration Coordinator to perform the post-migration clean-up.
Note: If at any point the NSX Migration Coordinator fails or restarts, you must re-enter the NSX for vSphere configuration details on the NSX Migration Coordinator before continuing with Workload Migrations for NSX V2T migrations.

If the NSX Migration Coordinator fails or restarts prior to completing post migration operations, then you must manually run the post-migrate NSX Migration Coordinator API call using the group ID from the migration dashboard. See VMware KB article.

Requirements and Limitations

  • NSX for vSphere and NSX environments must be explicitly joined using NSX bridging before migrating workloads. HCX Network Extensions cannot be used between NSX for vSphere and NSX environments. Bridge set up is through the NSX Migration Coordinator.
  • NSX for vSphere and NSX environments must be accessible to HCX Manager.
  • A dedicated vSphere vMotion data path must be set up between the source and the target ESXi hosts.
  • Any changes to the source environment after the NSX V2T migration can affect Workload Migrations for NSX V2T.
  • The Distributed Virtual Switch version at the source and the destination sites must be the same.
  • Workload Migrations for NSX V2T works in one direction. Reverse migration is not possible using Workload Migrations for NSX V2T.
    Note: After Workload Migrations for NSX V2T has completed, you can use Bulk migration to move the VMs back to the source site. For reverse migration using Bulk in single vCenter environments, you must specify a different folder name as the Destination Folder.
  • Standard switches at the source and target clusters must have matching security policies and the teaming and failover policies.
  • For Federated NSX environments, the HCX Cloud Manager must be configured with the Global Manager that is running the V2T Migration Coordinator, in addition to the Local Manager.

Restrictions

Workload Migrations for NSX V2T does not support:

  • HCX WAN Optimization.
  • HCX Network Extension.
  • Adding VMs to an HCX Mobility Group after initiation of Workload Migrations for NSX V2T.
  • Adding, deleting, or editing a network from a VM after the initiation of Workload Migrations for NSX V2T.
  • Retry of failed or canceled Workload Migrations for NSX V2T migration using the Edit Mobility Group wizard is not supported. A new mobility group must be created for these VMs.
  • Migration of suspended VMs.
  • Migration from HCX vCenter plug-in. Use the HCX standalone UI to trigger Workload Migrations for NSX V2T.
  • Encrypted VMs.