Shared Edge and Compute Cluster Switches

The shared edge and compute cluster uses a single N-VDS with a certain configuration for handled traffic types, NIC teaming, and MTU size.

Figure 1. Virtual Switch Design for ESXi Hosts in the Shared Edge and Compute Cluster

Table 1. Virtual Switches for the Shared Edge and Compute Cluster

N-VDS Switch Name	Function	Number of Physical NIC Ports	Teaming Policy	MTU
sfo01-w-nvds01	ESXi Management vSphere vMotion vSAN NFS Geneve Overlay (TEP) Uplink trunking (2) for the NSX-T Edge instances	2	Load balance source for ESXi traffic Failover order for edge VM traffic	9000
sfo01-w-uplink01	Uplink to enable ECMP	1	Failover order	9000
sfo01-w-uplink02	Uplink to enable ECMP	1	Failover order	9000

Table 2. Virtual Switches in the Shared Edge and Compute Cluster by Physical NIC

N-VDS Switch	vmnic	Function
sfo01-w-nvds01	0	Uplink
sfo01-w-nvds01	1	Uplink

Figure 2. Segment Configuration on an ESXi Host That Runs an NSX-T Edge Node

Table 3. Segments in the Shared Edge and Compute Cluster

N-VDS Switch	Segment Name
sfo01-w-nvds01	sfo01-w-nvds01-management
sfo01-w-nvds01	sfo01-w-nvds01-vmotion
sfo01-w-nvds01	sfo01-w-nvds01-vsan
sfo01-w-nvds01	sfo01-w-nvds01-overlay
sfo01-w-nvds01	sfo01-w-nvds01-uplink01
sfo01-w-nvds01	sfo01-w-nvds01-uplink02
sfo01-w-nvds01	sfo01-w-nvds01-nfs
sfo01-w02-uplink01	sfo01-w02-uplink01
sfo01-w02-uplink02	sfo01-w02-uplink02

Table 4. VMkernel Adapters for the Shared Edge and Compute Cluster

N-VDS Switch	Segment Name	Enabled Services
sfo01-w-nvds01	sfo01-w-nvds01-management	Management Traffic
sfo01-w-nvds01	sfo01-w-nvds01-vmotion	vMotion Traffic
sfo01-w-nvds01	sfo01-w-nvds01-vsan	vSAN
sfo01-w-nvds01	sfo01-w-nvds01-nfs	--

Note:

When the NSX-T Edge appliance is on an N-VDS, it must use a different VLAN ID and subnet from the ESXi hosts overlay (TEP) VLAN ID and subnet.

ESXi host TEP VMkernel ports are automatically created when you configure an ESXi host as a transport node.