A transport node is a node that is capable of participating in an NSX-T overlay or NSX-T VLAN networking.

About this task

For a KVM host, you can preconfigure the host switch, or you can have NSX Manager perform the configuration. For an ESXi host, NSX Manager always configures the host switch.


If you plan to create transport nodes from a template VM, make sure that there are no certificates on the host in /etc/vmware/nsx/. The netcpa agent does not create a new certificate if a certificate already exists.


  • The host must be joined with the management plane, and MPA connectivity must be Up on the Fabric > Hosts page.

  • A transport zone must be configured.

  • An uplink profile (also called a hostswitch profile) must be configured, or you can use the default uplink profile.

  • An IP pool must be configured, or DHCP must be available in the network deployment.

  • At least one unused physical NIC must be available on the host node.


  1. From a browser, log in to an NSX Manager at https://<nsx-mgr>.
  2. Select Fabric > Nodes > Transport Nodes and click Add.
  3. Enter a name for the transport node.
  4. Select a node from the drop-down menu.
  5. (Optional) Select a transport zone from the drop-down menu.
  6. (Optional) For a KVM node, select a host switch type.




    NSX Manager creates the host switch. This option is selected by default.


    The host switch is already configured.

    For a non-KVM node, the host switch type is always Standard.

  7. For a standard host switch, enter or select the following host switch information:
    • The host switch name. This name must be the same as the host switch name of the transport zone that this node belongs to.

    • The uplink profile.

    • The IP assignment. You can select Use DHCP, Use IP Pool, or Use Static IP List. If you select Use Static IP List, you must specify a list of comma-separated IP addresses, a gateway, and a subnet mask.

    • Physical NIC information


      Make sure that the physical NIC is not already in use (for example, by a standard vSwitch or a vSphere distributed switch). Otherwise, the transport node state will be partial success, and the fabric node LCP connectivity will fail to establish.

  8. For a preconfigured host switch, enter the following host switch information:
    • The host switch external ID. This ID must be the same as the host switch name of the transport zone that this node belongs to.

    • The VTEP name.


After adding the host as a transport node, the host connection to NSX Controllers changes from the "CLOSE_WAIT" status to the "Established" status. You can see this with the esxcli network ip connection list | grep 1234 command.

# esxcli network ip connection list | grep 1234
tcp   0   0   ESTABLISHED  1000144459  newreno  netcpa

For KVM, the command is netstat -anp --tcp | grep 1234.

user@host:~$ netstat -anp --tcp | grep 1234
tcp  0   0   ESTABLISHED -

You can view the transport node with the GET https://<nsx-mgr>/api/v1/transport-nodes/<node-id> API call:

  "resource_type": "TransportNode",
  "description": "",
  "id": "95c8ce77-f895-43de-adc4-03a3ae2565e2",
  "display_name": "node-comp-01b",
  "tags": [],
  "transport_zone_endpoints": [
      "transport_zone_id": "efd7f38f-c5da-437d-af03-ac598f82a9ec",
      "transport_zone_profile_ids": [
          "profile_id": "52035bb3-ab02-4a08-9884-18631312e50a",
          "resource_type": "BfdHealthMonitoringProfile"
  "host_switches": [
      "host_switch_profile_ids": [
          "value": "8abdb6c0-db83-4e69-8b99-6cd85bfcc61d",
          "key": "UplinkHostSwitchProfile"
          "value": "9e0b4d2d-d155-4b4b-8947-fbfe5b79f7cb",
          "key": "LldpHostSwitchProfile"
      "host_switch_name": "overlay-hostswitch",
      "pnics": [
          "device_name": "vmnic1",
          "uplink_name": "uplink-1"
      "static_ip_pool_id": "c78ac522-2a50-43fe-816a-c459a210127e"
  "node_id": "c551290a-f682-11e5-ae84-9f8726e1de65",
  "_create_time": 1460051753373,
  "_last_modified_user": "admin",
  "_system_owned": false,
  "_last_modified_time": 1460051753373,
  "_create_user": "admin",
  "_revision": 0

When the transport node creation is successful, LCP Connectivity changes to Up on Fabric > Nodes > Hosts. To see the change, refresh the browser screen.

What to do next

Create an NSX Edge transport node. See Create an NSX Edge Transport Node.