NSX Transport Nodes are configured with tunnel endpoint (TEP pool) IP addresses. 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 encapsulation of overlay frames. You can also use either DHCP or manually configured IP pools for tunnel endpoint IP addresses.
An example of the resulting routing table on an ESXi host where sub_a = 192.168.140.0 and sub_b = 192.168.150.0. (The management subnet, for example, might be 192.168.130.0).
Destination Gateway Genmask Iface 0.0.0.0 192.168.130.1 0.0.0.0 eth0 192.168.122.0 0.0.0.0 255.255.255.0 virbr0 192.168.130.0 0.0.0.0 255.255.255.0 eth0 192.168.140.0 192.168.150.1 255.255.255.0 nsx-vtep0.0 192.168.150.0 0.0.0.0 255.255.255.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 192.168.140.0 netmask 255.255.255.0 gw 192.168.150.1 dev nsx-vtep0.0
In /etc/network/interfaces before "up ifconfig nsx-vtep0.0 up" add this static route:
post-up route add -net 192.168.140.0 netmask 255.255.255.0 gw 192.168.150.1
Procedure
Results
The IPv4 or IPv6 address pool is listed on the IP pool page.
You can also use the GET https://<nsx-mgr>/policy/api/v1/infra/pools/ip-pools API call to view the IP pool list.
What to do next
Create an uplink profile. See Create an Uplink Profile.