A transport node prepared with VDS as a host switch ensures that segments created in NSX-T is realized as an NSX Distributed Virtual port group on a VDS switch and Segment in NSX-T.

In earlier versions of NSX-T Data Center , a segment created in NSX-T are represented as an opaque network in vCenter Server. When running NSX-T on a VDS switch, a segment is represented as an NSX Distributed Virtual Port Groups.

Any changes to the segments on the NSX-T network are synchronized in vCenter Server.

In vCenter Server, an NSX Distributed Virtual Port Group is represented as .

Any NSX-T segment created in NSX-T is realized in vCenter Server as an NSX-T object. A vCenter Server displays the following details related to NSX-T segments:

  • NSX Manager

  • Virtual network identifier of the segment

  • Transport zone

  • Attached virtual machines

The port binding for the segment is by default set to Ephemeral. Switching parameters for the switch that are set in NSX-T cannot be edited in vCenter Server and conversely.

Important: In a vCenter Server, an NSX Distributed Virtual port group realized does not require a unique name to differentiate it with other port groups on a VDS switch. So, multiple NSX Distributed Virtual port groups can have the same name. Any vSphere automations that use port group names might result in errors.
In vCenter Server, you can perform these actions on an NSX Distributed Virtual Port Group:
  • Add VMkernel Adapters.
  • Migrate VMs to Another Network.
However, NSX-T objects related to an NSX Distributed Virtual port group can only be edited in NSX Manager. You can edit these segment properties:
  • Replication Mode for the segment
  • VLAN trunk ID used by the segment
  • Switching Profiles (for example, Port Mirroring)
  • Ports created on the segment

For details on how to configure a vSphere Distributed Virtual port group, refer to the vSphere Networking Guide.