You can use an IP pool for the tunnel endpoints. Tunnel endpoints are the source and destination IP addresses used in the external IP header to identify the hypervisor hosts originating and end the NSX-T Data Center encapsulation of overlay frames. You can also use either DHCP or manually configured IP pools for tunnel endpoint IP addresses.

If you are using both ESXi and KVM hosts, one design option might be to use two different subnets for the ESXi tunnel endpoint IP pool (sub_a) and the KVM tunnel endpoint IP Pool (sub_b). In this case, on the KVM hosts a static route to sub_a must be added with a dedicated default gateway.

An example of the resulting routing table on an Ubuntu host where sub_a = and sub_b = (The management subnet, for example, might be

Kernel IP routing table:
Destination          Gateway          Genmask          Iface              eth0    virbr0    eth0    nsx-vtep0.0    nsx-vtep0.0

The route can be added in at least two different ways. Of these two methods, the route persists after host reboot only if you add the route by editing the interface. Adding a route using the route add command does not persist after a host reboot.

route add -net netmask gw dev nsx-vtep0.0

In /etc/network/interfaces before "up ifconfig nsx-vtep0.0 up" add this static route:

post-up route add -net netmask gw


  1. From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
  2. Select Networking → IP Address Pools → Add IP Address Pool.
  3. Enter the IP pool details.
    Option Parameter Example
    Name and Description Enter the IP pool and optional description.
    IP Ranges IP allocation ranges -

    CIDR Network address in a CIDR notation

    DNS Servers Comma-separated list of DNS servers

    DNS Suffix corp.local


The IPv4 or IPv6 address pool is listed on the IP pool page.

You can also use the GET https://<nsx-mgr>/api/v1/pools/ip-pools API call to view the IP pool list.

What to do next

Create an uplink profile. See Create an Uplink Profile.