When a transport node is configured on a VDS host switch, some network parameters can only be configured in vCenter Server.

The following requirements must be met to install NSX-T on a VDS host switch:

  • vCenter Server 7.0 or a later version
  • ESXi 7.0 or a later version

The created VDS switch can be configured to centrally manage networking for NSX-T hosts.

Configuring a VDS switch for NSX-T networking requires objects to be configured on NSX-T and in vCenter Server.
  • In vSphere:
    • Create a VDS switch.
      • Set MTU to at least 1600
      • Add ESXi hosts to the switch. These hosts are later prepared as NSX-T transport nodes.
      • Assign uplinks to physical NICs.
  • In NSX-T:
    • When configuring a transport node, map uplinks created in NSX-T uplink profile with uplinks in VDS.

For more details on preparing a host transport node on a VDS switch, see the NSX-T Data Center Installation Guide.

The following parameters can only be configured in a vCenter Server on a VDS backed host switch:

Configuration VDS NSX-T Description
MTU

In vCenter Server, set an MTU value on the switch.

Note: A VDS switch must have an MTU of 1600 or higher.

In vCenter Server, select VDS, click Actions → Settings → Edit Settings.

 Any MTU value set in an NSX-T uplink profile is overriden.

As a host transport node that is prepared using VDS as the host switch, the MTU value needs to be set on the VDS switch in vCenter Server.
Uplinks/LAGs In vCenter Server, configure Uplinks/LAGs on a VDS switch.

In vCenter Server, select VDS, click Actions → Settings → Edit Settings.		 When a transport node is prepared, the teaming policy on NSX-T is mapped to uplinks/LAGs configured on a VDS switch.
Note: A transport node prepared on an N-VDS switch, the teaming policy is mapped to physical NICs.

As a host transport node that is prepared using VDS as the host switch, the uplink or LAG are configured on the VDS switch. During configuration, NSX-T requires teaming policy be configured for the transport node. This teaming policy is mapped to the uplinks/LAGs configured on the VDS switch.

NIOC Configure in vCenter Server.

In vCenter Server, select VDS, click Actions → Settings → Edit Settings.

 NIOC configuration is not available when a host transport node is prepared using a VDS switch.

As a host transport node that is prepared using VDS as the host switch, the NIOC profile can only be configured in vCenter Server.
Link Layer Discovery Protocol (LLDP) Configure in vCenter Server.

In vCenter Server, select VDS, click Actions → Settings → Edit Settings.

 LLDP configuration is not available when a host transport node is prepared using a VDS switch. As a host transport node that is prepared using VDS as the host switch, the LLDP profile can only be configured in vCenter Server.
Add or Manage Hosts Manage in vCenter Server.

In vCenter Server, go to Networking → VDS Switch → Add and Manage Host..

 Prepared as transport nodes in NSX-T. Before preparing a transport node using a VDS switch, that node must be added to the VDS switch in vCenter Server.
Note: NIOC profiles, Link Layer Discovery Protocol (LLDP) profile, and Link Aggregation Group (LAG) for these virtual machines are managed by VDS switches and not by NSX-T. As a vSphere administrator, configure these parameters from vCenter Server UI or by calling VDS API commands.

After preparing a host transport node with VDS as a host switch, the host switch type displays VDS as the host switch. It displays the configured uplink profile in NSX-T and the associated transport zones.

In vCenter Server, the VDS switch used to prepare NSX-T hosts is created as an NSX Switch.