If you want to create gateways and segments that span more than one location, you must configure a remote tunnel endpoint (RTEP) on Edge nodes in each location.
When you configure an RTEP, do it on an Edge cluster basis. All Edge nodes in the cluster must have an RTEP configured. You do not need to configure all Edge clusters with RTEP. RTEPs are required only if the Edge cluster is used to configure a gateway that spans more than one location.
You can configure the TEP and RTEP to use the same physical NIC on the Edge node or use separate physical NICs.
This procedure describes this task starting from your Local Manager. You can also configure RTEPs from your Global Manager by using the Location Manager site selection drop-down to choose the Local Manager.
Prerequisites
- Verify that each location participating in the stretched network has at least one Edge cluster.
- For RTEP networks, determine which layer 3 networks and VLANs to use.
- Intra-location tunnel endpoints (TEP) and inter-location tunnel endpoints (RTEP) must use separate VLANs and layer 3 subnets.
- Verify that all RTEP networks used in a given NSX Federation environment have IP connectivity to each other.
- Verify that external firewalls allow cross-location RTEP tunnels. See VMware Ports and Protocols at https://ports.vmware.com/home/NSX.
- Configure the MTU for RTEP on each Local Manager. The default is 1500. Set the RTEP MTU to be as high as your physical network supports. On each Local Manager, select . Click Edit next to Remote Tunnel Endpoint.
- Optionally, if you do not use DHCP for RTEP, configure the RTEP IP pool for your site to configure the RTEPs for the Edge cluster. For details, go to "Add an IP Address Pool" in the NSX Administration Guide.