V2T Migration Edge Cutover Checklist

Products

• VMware NSX

Issue/Introduction

This KB is to provide a checklist of items to verify before and after an NSX V2T Edge Migration.

Environment

VMware NSX-T Data Center 4.x
VMware NSX-T Data Center
VMware NSX-T Data Center 3.x
VMware NSX-T

VMware NSX

Resolution

1. Ensure connectivity between NSX-v and NSXT Edge TEPs via MTU pings
2. For user defined topology modes, ensure Tier0 routing is set up properly and northbound dynamic routing, established routes learned on Tier0.
3. For Federation Primary Secondary environments, ensure that setup does not have asymmetric routing. Advertise routes with higher AS path on secondary site Tier0.
4. For nested environments, ensure that NSXT Edge VTEP VLAN is different from ESXi VTEP VLAN on which it is hosted.
5. Ensure that NSX-v and NSXT Edges are on different ESXi hosts.
6. Ensure workload VMs directly connected to NSX-v ESG are on a different ESXi host than ESG.
7. For versions prior to 3.2.4 , for non VRA user defined topology modes, set Edge nodes in V2T Config mode using Node API: /api/v1/transport-nodes/<tn_uuid>/node/v2t-migration-config
8. For versions prior to 3.2.4, for non VRA user defined topology modes, ensure VDR MAC is set to a different value on NSXT. Change the MAC Address of NSX-T Virtual Distributed Router
9. In case of packet drops post cutover, take packet captures on the relevant NSX-v ESX hosts and NSXT edges and determine the drop point. Check if the drop is due to a missing route, ARP not being resolved or due to RPF or firewall.

Additional Information

Impact/Risks:
If these items are overlooked or missed, traffic may fail to flow properly through the NSX-T Edges after the cutover, or datapath performance may negatively be affected.