Connecting a Virtual Machine to a NSX-T Logical Switch/Segment

Posted by


  • The VMs must be hosted on hypervisors that have been added to the NSX-T Data Center fabric.
  • The fabric nodes must have NSX-T Data Center management plane (MPA) and NSX-T Data Center
  • control plane (LCP) connectivity.
  • The fabric nodes must be added to a transport zone.
  • A logical switch must be created.


  • In the vSphere Web Client, edit the VM settings, and attach the VM to the NSX-T Data Center logical
  • Switch called Dev Switch.  Check the box for connect.
  • If you have not already assigned a static IP for the virtual machine then log into the VM and set the IP to (example).

Additional Information:

After attaching a VM to a logical switch, logical switch ports are added to the logical switch. You can view logical switch ports on the NSX Manager in Advanced Networking & Security > Networking >Switching > Ports.

In the NSX-T Data Center API, you can view NSX-T Data Center-attached VMs with the GEThttps://<nsx-mgr>/api/v1/fabric/virtual-machines API call

In the NSX-T Data Center Manager UI under Advanced Networking & Security > Networking >Switching > Ports, the VIF attachment ID matches the ExternalID found in the API call. Find the VIF attachment ID matching the VM’s externalId and make sure that the Admin and Operational status are Up/Up.


If two VMs are attached to the same logical switch and have IP addresses configured in the same subnet, they should be able to ping each other.  From the example above Dev1 should be able to ping Dev4, vice versa. 

One comment

Leave a Reply