NSX Lab – Create Transport Zones

Next up is the transport zone.

Configure the Transport Zone
The Transport Zone is a collection of ESXi hosts that can communicate with each other through VTEP interfaces.
A Transport Zone can extend across ESXi clusters, and across multiple dVSwitches, it defines the extension of a Logical Switch

Although configuring the Transport Zone is easy,  it needs a bit of thought beforehand, namely how will the vxlan traffic move across the transport zone;

  • Multicast
  • Unicast
  • Hybrid (mixed)

In previous versions of vxlan only multicast was available, requiring multicast group IP addresses, and the enabling of PIM routing or IGMP snooping features on physical switches or routers.
The use of NSX controller clusters in managing vxlan eliminates the need for multicast support from the physical network infrastructure.


Configure VNI (vxlan network identifier)
Think of this as similar to vlan encapsulation, the VNI or Segment ID is carried inside the vxlan header in the form of a vxlan tag, resulting in a logical layer 2 domain.
I will do like most and use 5000-5999 for the lab
As you can see this can be a lot more than 999 layer 2 domains – segment ids is how the vxlan exceeds the 4096 layer 2 domain limitation of vlan

Networking & Security > Installation > Logical Network Preparation > Segment ID



Configure the Transport Zone
Clearly this is not complicated, but take note of the dvSwitches as well as the clusters, we are aggregating elements to form the layer 2 transport zone

> Logical Network Preparation > Transport Zones


Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.