In this step, you specify the topology that will be migrated. This can be done through the NSX Manager UI or by using a mapping file in JSON format.
This mapping specifies how Edge Service Gateways (ESGs) and Distributed Logical Routers (DLRs) should map to gateways in
NSX-T. Before providing the mapping, evaluate your topology requirements and plan to do the following:
- Determine how you will map the ESGs and DLRs. The northbound ESGs without any L4-L7 services should be skipped. These are usually the ESGs peering with northbound routers and are in ECMP path. If you are using VPN on a northbound ESG, migrating to active-standby tier-0 is recommended. In other cases, migrating the ESGs/DLRs to tier-1 is recommended. An ESG and a DLR can be merged in one mapping entry.
- Create tier-0 and tier-1 gateways and configure dynamic or static routing on the tier-0 gateways towards the northbound routers based on your requirements.
- After configuring the dynamic routing on tier-0 gateways, check that the dynamic routing has converged, that is, BGP sessions are established or OSPF neighborships are FULL as applicable. After this, proceed with providing the mapping.
An example of a mapping file that maps ESGs to a tier-0 gateway:
[
{
"name":"nsxv-to-nsxt-mapping",
"v_edges_to_policy_gateways_mappings":[
{
"v_edges":[
"edge-1",
"edge-2"
],
"policy_gateway_name": "tier0-gateway"
"policy_gateway_path": "/infra/tier-0s/tier0-gateway"
}
]
}
]
