In this step, you migrate the Edge Services Gateways (ESGs).
If you have no Edge Services Gateway appliances in your topology, you must still click Start so that you can proceed to the Migrate Hosts step.
- All configuration issues must be resolved.
- The NSX-V configuration must be migrated to NSX.
- Verify that the migrated configurations are shown in the NSX Manager UI or API of NSX.
- Verify that you have a backup of NSX-V and vSphere since the most recent configuration changes were made.
- If you are using new IP addresses for the NSX Edge node uplinks, you must configure the northbound routers with these new BGP neighbor IP addresses.
- Verify that you have created an IP pool for Edge Tunnel End Points (TEP). See Create an IP Pool for Edge Tunnel End Points.
- Logical router interfaces created in NSX use the global default MTU setting, which is 1500. If you want to ensure that all logical router interfaces have a larger MTU, you can change the global default MTU setting. For more information, see Change the Global MTU Setting.
If MTU setting other than 1500 is used on peering routers, the same should be configured on NSX. In case of OSPF topologies, OSPF adjacencies can get stuck if MTU setting is different from peering routers' MTU setting.
- From the Migrate Edges page, click Start.
All Edges are migrated. The uplinks on the NSX-V Edge Services Gateways are internally disconnected, and the uplinks on the NSX Edge nodes are brought online.
- Verify that routing and services are working correctly in the new NSX environment.
If so, you can migrate the hosts. Before migrating the hosts, see Configuring NSX-V Host Migration.
- Click Continue to go to the next step.
- The routing and service configuration from NSX-V Edge Services Gateway (ESG) are transferred to the newly created NSX Edge nodes.
- The new TEP IP addresses for the newly created NSX Edge nodes are configured from a newly created IP pool for Edge Tunnel End Points.