You must provide inputs on various configuration issues, including Maintenance Mode migration options and configuration details for the new NSX-T Edge nodes.

Migrating Hosts in vCenter Server 7.0 Using Automated Maintenance Migration Mode

Consider the following scenario:
  • NSX for vSphere environment uses vSphere Distributed Switch 7.0.
  • On the Resolve Configuration page, Host Maintenance mode is set to Automated.
  • vSphere DRS is not enabled on the clusters that are being migrated.

In this scenario, the following blocking issue messages are displayed on the Resolve Configuration page:

Incorrect DRS Configuration for Maintenance Mode migration.
Vmotion vmknics not configured on host for Maintenance mode migration.

To resolve the DRS configuration issue, go to the vSphere Client, and enable DRS on each cluster that is being migrated. Ensure that the DRS Automation Level is set to Fully Automated.

To resolve the second blocking issue, go to the vSphere Client, and enable vMotion on the VMkernel adapter of each host in the cluster. For detailed steps about enabling vMotion on the VMkernel adapter, see the vSphere 7.0 product documentation.

After fixing the blocking configuration issues in the NSX for vSphere environment, roll back the current migration, and import the configuration again.

Edge Node Networking Configuration

During Resolve Configuration, you provide information about the NSX Edge nodes that you have created to replace your NSX for vSphere Edge Services Gateways. The configuration might have to change to work correctly on NSX-T. You might need to use a different IP address and VLAN than you used in NSX for vSphere.

Migrating Edge Services Gateway with L4-L7 Services

Using the same interface for the router uplink and services such as VPN is supported in NSX for vSphere. This configuration is not supported in NSX-T. You can assign new IP addresses for the NSX Edge node uplinks so that you do not need to change the IP address for the services running on the NSX Edge node.

Migrating Edge Services Gateway in a High Availability Configuration

The NSX for vSphere topology that contains Edge Services Gateways in a high availability configuration can contain an Edge Services Gateway with two uplinks connected to two different distributed port groups on different networks.

In NSX-T, this configuration is replaced by two NSX Edge nodes, both of which must have their uplinks on the same network.

For example, an Edge Services Gateway with HA might have this configuration:
  • vnic1 has IP address 192.178.14.2/24 and is attached to port group Public-DVPG which uses VLAN 11.
  • vnic4 has IP address 192.178.44.2/24 and is attached to port group Public-DVPG-2 which uses VLAN 15.

To work after migration, at least one of these IP addresses has to change, as they both must be on the same network.

Here is an example of the information that might be provided during Resolve Configuration.

For the first NSX Edge node:
  • ID is fa3346d8-2502-11e9-8013-000c2936d594.
  • IP address is 192.178.14.2/24.
  • VLAN is 11.
For the second NSX Edge node:
  • ID is fa2de198-2502-11e9-9d7a-000c295cffc6.
  • IP address is 192.178.14.4/24.
  • You do not need to provide the VLAN because the same VLAN configured for the first NSX Edge node is assumed for the second node.

Both NSX Edge nodes must have connectivity to this network.