A transport node is a node that is capable of participating in an NSX-T Data Center overlay or NSX-T Data Center VLAN networking. Any node can serve as a transport node if it contains an N-VDS. Such nodes include but are not limited to NSX Edges. This procedure demonstrates how to add an NSX Edge as a transport node.

An NSX Edge can belong to one overlay transport zone and multiple VLAN transport zones. If a VM requires access to the outside world, the NSX Edge must belong to the same transport zone that the VM's logical switch belongs to. Generally, the NSX Edge belongs to at least one VLAN transport zone to provide the uplink access.


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 NSX Edge must be joined with the management plane, and MPA connectivity must be Up on the Fabric > Edges page. See Join NSX Edge with the Management Plane.

  • Transport zones must be configured.

  • An uplink profile must be configured or you can use the default uplink profile for bare-metal NSX Edge nodes.

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

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


  1. From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
  2. Select Fabric > Nodes > Transport Nodes > Add.
  3. Type a name for the NSX Edge transport node
  4. Select an NSX Edge fabric node from the drop-down list.
  5. Select the transport zones that this transport node belongs to.

    An NSX Edge transport node belongs to at least two transport zones, an overlay for NSX-T Data Center connectivity and a VLAN for uplink connectivity.

  6. Click the N-VDS tab and provide the N-VDS information.



    N-VDS Name

    Must match the names that you configured when you created the transport zones.

    Uplink Profile

    Select the uplink profile from the drop-down menu.

    The available uplinks depend on the configuration in the selected uplink profile.

    IP Assignment

    Select Use IP Pool or Use Static IP List for the overlay N-VDS.

    If you select Use Static IP List, you must specify a list of comma-separated IP addresses, a gateway, and a subnet mask.

    IP Pool

    If you selected Use IP Pool for IP assignment, specify the IP pool name.

    Physical NICs

    Unlike a host transport node, which uses vmnicX as the physical NIC, an NSX Edge transport node uses fp-ethX.

  7. (Optional) View the transport node with the GET https://<nsx-mgr>/api/v1/transport-nodes/<transport-node-id> API call.
    GET https://<nsx-mgr>/api/v1/transport-nodes/78a03020-a3db-44c4-a8fa-f68ad4be6a0c
      "resource_type": "TransportNode",
      "id": "78a03020-a3db-44c4-a8fa-f68ad4be6a0c",
      "display_name": "node-comp-01b",
      "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": 1459547122893,
      "_last_modified_user": "admin",
      "_last_modified_time": 1459547126740,
      "_create_user": "admin",
      "_revision": 1
  8. (Optional) For status information, use the GET https://<nsx-mgr>/api/v1/transport-nodes/<transport-node-id>/status API call.
      "control_connection_status": {
        "degraded_count": 0,
        "down_count": 0,
        "up_count": 1,
        "status": "UP"
      "tunnel_status": {
        "down_count": 0,
        "up_count": 0,
        "status": "UNKNOWN",
        "bfd_status": {
          "bfd_admin_down_count": 0,
          "bfd_up_count": 0,
          "bfd_init_count": 0,
          "bfd_down_count": 0
        "bfd_diagnostic": {
          "echo_function_failed_count": 0,
          "no_diagnostic_count": 0,
          "path_down_count": 0,
          "administratively_down_count": 0,
          "control_detection_time_expired_count": 0,
          "forwarding_plane_reset_count": 0,
          "reverse_concatenated_path_down_count": 0,
          "neighbor_signaled_session_down_count": 0,
          "concatenated_path_down_count": 0
      "pnic_status": {
        "degraded_count": 0,
        "down_count": 0,
        "up_count": 4,
        "status": "UP"
      "mgmt_connection_status": "UP",
      "node_uuid": "cd4a8501-0ffc-44cf-99cd-55980d3d8aa6",
      "status": "UNKNOWN"

What to do next

Add the NSX Edge node to an NSX Edge cluster. See Create an NSX Edge Cluster.