Transport zones and transport nodes are important concepts in NSX-T. About Transport ZonesA transport zone is a container that defines the potential reach of transport nodes. Transport nodes are hypervisor hosts and NSX Edges that will participate in an NSX-T overlay. For a hypervisor host, this means that it hosts VMs that will communicate over NSX-T logical switches. For NSX Edges, this means that it will have logical router uplinks and downlinks. Create an IP Pool for Tunnel Endpoint IP AddressesYou 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 uniquely identify the hypervisor hosts originating and terminating the NSX-T encapsulation of frames. You can use either DHCP or manually configured IP pools for tunnel endpoint IP addresses. Create an Uplink ProfileAn uplink profile is a hostswitch profile, meaning that it defines policies for the links from hypervisor hosts to NSX-T logical switches or from NSX Edge nodes to top-of-rack switches. Create Transport ZonesTransport zones dictate which hosts and, therefore, which VMs can participate in the use of a particular network. A transport zone does this by limiting the hosts that can "see" a logical switch—and, therefore, which VMs can be attached to the logical switch. A transport zone can span one or more host clusters. Create a Host Transport NodeA transport node is a node that is capable of participating in an NSX-T overlay or NSX-T VLAN networking. Create an NSX Edge Transport NodeA transport node is a node that is capable of participating in an NSX-T overlay or NSX-T VLAN networking. Any node can serve as a transport node if it contains a hostswitch. Such nodes include but are not limited to NSX Edges. This procedure demonstrates how to add an NSX Edge as a transport node. Create an NSX Edge ClusterHaving a multi-node cluster of NSX Edges helps ensure that at least one NSX Edge is always available. In order to create a tier-0 logical router or a tier-1 router with NAT, you must associate it with an NSX Edge cluster. Therefore, even if you have only one NSX Edge, it must still belong to an NSX Edge cluster to be useful.