VMware Aria Automation NSX-V to NSX-T migration enables you to take advantage of the NSX Data Center Migration Coordinator (was NSX-T Data Center Migration Coordinator) from within the constructs of VMware Aria Automation. While the migration process is primarily run in the VMware Aria Automation environment, there are several interconnected actions within the process that involve both the VMware Aria Automation administrator and the NSX administrator working together to share information.

You can migrate your NSX-V Manager (NSX-V) to NSX Manager (NSX-T) by using the prescriptive VMware Aria Automation NSX-V to NSX-T migration assistant in VMware Aria Automation. The migration assistant consists of a getting started page and sequential migration plan pages.

Each source NSX-V cloud account requires a separate migration plan in the VMware Aria Automation NSX-V to NSX-T migration assistant.

By migrating your NSX-V cloud accounts and their related objects to NSX-T, you can take advantage of the many enhanced features and functions of NSX-T itself and as integrated within VMware Aria Automation.

While you work with the migration plan in VMware Aria Automation, there is a point in the process where the VMware Aria Automation administrator and the NSX administrator must share files with one another as input to, and output from, the NSX Data Center Migration Coordinator (was NSX-T Data Center Migration Coordinator) utility. The migration plan on-screen help informs you when you and the NSX administrator need to communicate with one another to share the needed files.

The VMware Aria Automation NSX-V to NSX-T migration assistant is available for migrating NSX-V cloud accounts and their related objects to NSX-T within your current VMware Aria Automation release. It is not available for migrating NSX cloud accounts from one VMware Aria Automation release to another.

This guide is meant for use with the VMware Aria Automation NSX-V to NSX-T migration assistant and its prescriptive migration plans. Use this guide to supplement the on-screen instructions provided in the VMware Aria Automation NSX-V to NSX-T migration plan on-screen guidance.

For information about the related NSX Data Center Migration Coordinator (was NSX-T Data Center Migration Coordinator) utility, see NSX-T Data Center Migration Coordinator Guide in VMware NSX product documentation.

For more information about the benefits of migrating to NSX-T, see the Migrate to VMware NSX-T product page.

Supported topologies

VMware Aria Automation supports migration of NSX-V objects to NSX-T release 3.1.1 or later objects, including NSX-T release 3.1.3. It does not support migration of NSX-V objects to NSX-T release 3.1.0 or earlier objects.

Note: The VMware Aria Automation NSX-V to NSX-T migration process is currently designed to work with the Migration Coordinator in NSX-T 3.1.x and later. The expectation is that the process will also work, in future VMware Aria Automation releases, with NSX Fixed Mode. VMware Aria Automation does not currently support either NSX Fixed Mode or NSX User-Defined Mode.

The NSX-V to NSX-T migration process migrates to NSX-T Policy API. It does not migrate to NSX-T Manager API.

vCenter 6.7 associations are migrated to vCenter 6.7. vCenter 7.0 or greater associations are migrated to vCenter 7.0 or greater.

The NSX-V to NSX-T migration process supports NSX-V to NSX-T migration for deployments that were migrated from VMware vRealize Automation 7.x to VMware vRealize Automation 8.x or VMware Aria Automation and for deployments that originated in VMware vRealize Automation 8.x or VMware Aria Automation.

In the following scenario, workloads are migrated from VMware vRealize Automation 7.x to VMware Aria Automation and then NSX objects are migrated from NSX-V to NSX-T in VMware Aria Automation.
  1. Deploy your current VMware Aria Automation release.
  2. Migrate your workloads to your current VMware Aria Automation release by using the migration wizard. Reference the VMware Aria Automation Transition Guide for your release that is available on the VMware Aria Automation product documentation page.
  3. Deploy the NSX-T application.
  4. Add an NSX-T cloud account to your current VMware Aria Automation environment and map it to an NSX-T endpoint.
  5. Create and run an NSX-V to NSX-T migration to move your workloads from NSX-V to NSX-T, as described in this documentation and in the on-screen migration assistant.
  6. When a new VMware Aria Automation release is made available, you can upgrade to it normally by using the VMware Aria Suite Lifecycle application.

The following topologies are supported and available for migration:

  • Existing networks (Static and DHCP)
  • Routed networks (Static and DHCP)
  • Private networks (Static and DHCP)
  • Existing security groups
  • On-demand security groups
  • On-demand one armed load balancers on existing networks
  • Outbound networks (Static and DHCP) with or without shared gateway
    • User-defined DNAT rules are not supported
    • Load balancers with outbound networks are not supported
  • Machine (DHCP IP) connected to an outbound network
  • Multiple outbound networks connected through a gateway
  • Deployments that contain outbound or private networks that use isolation policy as an on-demand security group
  • Private networks that are isolated by a security group
  • Outbound networks that are isolated by a security group
  • On-demand routed networks with DHCP and one-armed load balancer
  • On-demand and existing security groups and load balancer
  • On-demand outbound networks with DHCP and load balancer
The following topologies are also supported:
  • NSX-V networks associated with vCenter 6.7 and CVDS 6.7. Migration is to NSX-T 3.1.1 or greater with vCenter 6.7 and NVDS or vCenter 7.0 and NVDS.
  • NSX-V networks associated with vCenter 7.0 and CVDS. Migration is to NSX-T with vCenter 7.0 and NVDS.

For related information about supported topologies, see Topologies Supported for Integration with VMware Aria Automation in VMware NSX product documentation.

Unsupported topologies

The following topologies are not supported for migration:

  • Deployments that contain NAT or DNAT rules configured on the NAT or gateway component
  • Routed networks with shared T1
  • One-arm load balancer or inline load balancer on any on-demand network
  • On-demand inline load balancers on existing networks
  • Deployments that use the public network type
  • Deployments that reference vSphere network types.

Manager API to Policy API migration is not supported.

If the assessment step in the migration plan encounters an unsupported topology, it generates a validation error.

Running data collection if NSX-V and vCenter objects were migrated from vRealize Automation 7.x

If any deployments in your VMware Aria Automation environment were migrated from vRealize Automation 7.x, you must run data collection on their NSX-V and vCenter cloud accounts before you create your VMware Aria Automation NSX-V to NSX-T migration plan. This step is needed to collect information about migrated resources such as load balancers and security groups.

Accessing the VMware Aria Automation NSX-V to NSX-T Migration Assistant

This section provides and overview of the migration process.

Open the VMware Aria Automation NSX-V to NSX-T migration assistant from the cloud services console.
  1. Using your VMware Aria Automation administrator credentials and migration role privileges, log in to your VMware Aria Automation console and click the VMware Aria Automation Migration Assistant service tile.
  2. Click Getting Started from the NSX V2T Migration menu. To gain an overview of the process, review the information on the Getting Started page. For more information, see Getting started with VMware Aria Automation NSX-V to NSX-T migration.
  3. When you are ready to start the migration, click Migration Plan from the NSX V2T Migration menu and then click New Plan.
  4. The migration plan wizard provides the sequential instruction you need to advance through each step in the process. For more information, see Creating and running the VMware Aria Automation NSX-V to NSX-T migration plan.