During the Migrate Edges step, north-south traffic is cut off from the NSX-V Edge Services Gateways and traffic passes through the NSX-T Edges.

Prerequisites

  • All NSX-V logical configurations including routing and Layer 3 networking service configurations must either be migrated or manually created in NSX-T before the Edge cutover.
  • Verify the migrated or manually created configurations in the NSX-T NSX Manager UI, or use the NSX-T APIs to verify the logical configurations.
  • The DPDK fast path uplink interfaces (fp-eth0, fp-eth1, and fp-eth2) on the NSX-T Edge nodes must be down.
  • All configuration issues must be resolved.
  • Verify that either you have either created an IP pool for Edge Tunnel End Points (TEP) or configured static IP addresses for the Edge TEPs. For information about creating an IP pool, see Create an IP Pool for Edge Tunnel End Points.

Procedure

  1. From the Migrate Edges page, click Start.
    Caution: North-south traffic is temporarily interrupted during the Migrate Edges step.
    The migration coordinator takes the following actions during the Edge cutover:
    • The uplinks on the NSX-V Distributed Logical Router are internally disconnected from the Transit Logical Switch to which the Edge Services Gateways are also connected. The uplink interfaces on the NSX-T Edge nodes are brought online. The DPDK fast path uplink interfaces on the NSX-T edges (fp-eth0, fp-eth1, and fp-eth2) are enabled (admin_status: up). All north-south traffic that was previously passing through the Edge Services Gateways now moves through the NSX-T Edges.
    • If DHCP service was configured on NSX-V Edge Services Gateway before the migration, the DHCP leases of the workload VMs are migrated to the NSX-T Edge.
    • Scenario: Let us consider that in the NSX-V environment, a DHCP relay service is configured on the Distributed Logical Router (DLR). The uplink of the DLR is connected to an ESG and a DHCP server is configured on the ESG. Before the Edge cutover, this relay service forwards the DHCP requests to the DHCP server on the ESG. That is, before the Edge cutover, the relay service contains the DHCP server IP address that is configured on the ESG. When an Edge cutover occurs, the migration coordinator automatically updates the server IP in the DLR relay with the DHCP server IP in the DHCP profile that is attached to the NSX-T tier-0 or tier-1 gateway. In other words, after the Edge cutover, the DHCP requests are relayed to the Gateway DHCP server in the NSX-T environment.

    If necessary, you can roll back the Migrate Edges step. When you roll back the migration, the north-south traffic switches back to the NSX-V ESGs. In addition, the migration coordinator brings down the fast path interfaces on the NSX-T Edge nodes. The DHCP leases are removed from the NSX-T Edges, and the workload VMs start receiving the DHCP leases from the DHCP server on the ESG.

  2. Click Finish.
    A dialog box appears to confirm finishing the migration. If you finish the migration, all migration details are cleared. You can no longer review the settings of this migration. For example, which inputs were made on the Resolve Configuration page.

What to do next

  1. Verify that the north-south traffic is flowing successfully. Run ping commands on the NSX-V workload VMs to check connectivity to the machines in the external physical network.
  2. If DHCP service is running on NSX-T Edges, log in to the NSX-T Edge CLI, and run the get dhcp leases command. Observe that the DHCP leases are retained on the NSX-V workload VMs.