If a cluster of ESXi hosts is registered to a vCenter Server, you can apply transport node profiles on the ESXi cluster to automatically prepare all hosts as NSX transport nodes.

Prerequisites

  • Verify that all hosts in the vCenter Server are powered on.
  • Verify that the system requirements are met. See System Requirements.
  • The reverse proxy service on all nodes of the NSX Manager cluster must be Up and running.

    To verify, run get service http. If the service is down, restart the service by running restart service http on each NSX Manager node. If the service is still down, contact VMware support.

  • Verify that a transport node profile is configured. See Add a Transport Node Profile.
  • (Host in lockdown mode) If your exception list for vSphere lockdown mode includes expired user accounts, NSX installation on vSphere fails. Ensure that you delete all expired user accounts before you begin installation. For more information on accounts with access privileges in lockdown mode, see Specifying Accounts with Access Privileges in Lockdown Mode in the vSphere Security Guide.

Procedure

  1. From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address> or https://<nsx-manager-fqdn>.
  2. Select System > Fabric > Hosts.
  3. From the Managed By drop-down menu, select an existing vCenter Server.
    The page lists the available vSphere clusters and/or ESXi hosts from the selected vCenter Server. You may need to expand a cluster to view the ESXi hosts.
  4. Select a cluster and click Configure NSX.
  5. In the NSX Installation pop-up window, from the Transport Node Profile drop-down menu, select the transport node profile to apply to the cluster. If a transport node is not created, click Create New Transport Node Profile to create a new one.
  6. Click Apply to begin the process of transport node creation of all hosts in the cluster.
    See Add a Transport Node Profile.
  7. If you only want to prepare individual hosts as transport nodes, select that host, click Configure NSX.
    The Configure NSX dialog box opens.
    1. Verify the host name in the Host Details panel. Optionally, you can add a description.
    2. Click Next to move to the Configure NSX panel.
    3. Select the available transport zones and click the > button to include the transport zones in the transport node profile.
  8. Verify the host name in the Host Details panel, and click Next.
    Optionally, you can add a description.
  9. In the Configure NSX panel, expand New Node Switch.
  10. In the New Node Switch section, configure the following fields.
    Option Description

    Mode (NSX 4.0.0.1 only)

    Choose between the following mode options:
    • Standard: Is the standard mode that is available to all supported hypervisors by NSX.
    • ENS Interrupt: Is a variant of the Enhanced Datapath mode.
    • Enhanced Datapath: Is the mode that provides accelerated networking performance. This mode requires nodes to use VMXNET3 vNIC enabled network cards. It is not supported on NSX Edge nodes and Public Gateways. The supported hypervisor is ESXi. It is recommended to run ESXi v6.7 U2 and later versions.

    Mode (Starting with NSX 4.0.1.1)

    Choose between the following mode options:
    • Standard: This mode applies to all transport nodes. The data-plane in the transport node automatically selects the host switch mode as per the uplink capabilities.
    • Enhanced Datapath - Standard: This mode is a variant of the Enhanced Data Path mode. It is available only on ESXi hypervisor 7.0 and later versions. Please consult your account representative for applicability.
    • Enhanced Datapath - Performance: This is the Enhanced Data Path switch mode for ESXi host transport node. This mode provides accelerated networking performance. It requires nodes to use VMXNET3 vNIC enabled network cards. It is not supported on NSX Edge nodes and Public Gateways. The supported hypervisor is ESXi. It is recommended to run ESXi v6.7 U2 and later versions.
    • Legacy: This mode was formerly called Standard. It applies to all transport nodes. When the host switch mode is set to Legacy, the packet handler stack is enabled. On NSX Manager UI, you will see this mode set to Standard and the Legacy field to 'Yes'. You can select this mode only through API, since the Legacy field is read-only in NSX Manager UI.
      You can run the following Host Transport Node or Transport Node Profile policy API to set the host switch mode to Legacy:
      • Create or update Host Transport Node:
        PUT https://<NSX-Manager-IP-ADDRESS>/POST/policy/api/v1/infra/sites/<site-id>/enforcement-points/<enforcementpoint-id>/host-transport-nodes/<host-transport-node-id>
      • Create or update policy Host Transport Node Profile:
        PUT https://<NSX-Manager-IP-ADDRESS>/POST/policy/api/v1/infra/host-transport-node-profiles/<transport-node-profile-id>
    Name

    (Hosts managed by a vSphere cluster) Select the vCenter Server that manages the host switch.

    Select the VDS that is created in vCenter Server.
    Transport Zones

    Shows the transport zones that are realized by the associated host switches. You cannot add a transport zone if it is not realized by any host switch.

    Supported transport zone configurations:
    • You can add multiple VLAN transport zones per host switch.
    • You must add only one overlay transport zone per host switch. NSX Manager UI does not allow adding multiple overlay transport zones.
    Uplink Profile Select an existing uplink profile from the drop-down menu or create a custom uplink profile. You can also use the default uplink profile.

    If you keep the MTU value empty, the NSX takes the global default MTU value 1700. If you enter a MTU value in NSX uplink profile, that MTU value will override the global default MTU value.

    Note: Link Aggregation Groups defined in an uplink profile cannot be mapped to VDS uplinks.
    IP Assignment (TEP) Select between Use DHCP and Use IP Pool to assign an IP address to tunnel endpoints (TEPs) of the transport node.

    If you selected Use IP Pool for an IP assignment, specify the IP pool name and the range of IP addresses that can be used for tunnel endpoints.
    CPU Config
    You can configure the CPU Config field only when the Mode is set to Enhanced Datapath.
    1. Click Set.
    2. In the CPU Config window, click Add.
    3. Enter values for the NUMA Node Index and LCores per NUMA Node fields.
    4. To save the values, click Add and Save.
    Teaming Policy Switch Mapping

    Before you map uplinks profiles in NSX with uplinks in VDS, ensure uplinks are configured on the VDS switch. To configure or view the VDS switch uplinks, go to vCenter Server → vSphere Distributed Switch. Click Actions → Settings → Edit Settings.

    Map uplinks defined in the selected NSX uplink profile with VDS uplinks. The number of NSX uplinks that are presented for mapping depends on the uplink profile configuration.

    For example, in the upink-1 (active) row, go to the Physical NICs column, click the edit icon, and type in the name of VDS uplink to complete mapping it with uplink-1 (active). Likewise, complete mapping for the other uplinks.
    Note: Uplinks/LAGs, NIOC profile, LLDP profile are defined in vCenter Server. These configurations are not available in NSX Manager. To manage VMkernel adapters on a VDS switch, go to vCenter Server to attach VMkernel adapters to Distributed Virtual port groups or NSX port groups.
  11. If you have selected multiple transport zones, click + Add Switch again to configure the switch for the other transport zones.
  12. Click Add to complete the configuration.
  13. (Optional) View the ESXi connection status. 
    # esxcli network ip connection list | grep 1235
tcp   0   0  192.168.210.53:20514  192.168.110.34:1234   ESTABLISHED  1000144459  newreno  nsx-proxy
  14. From the Host Transport Node page, verify that the NSX Manager connectivity status of hosts in the cluster is Up and NSX configuration state is Success. During the configuration process, each transport node displays the percentage of progress of the installation process. If installation fails at any stage, you can restart the process by clicking the Resolve link that is available against the failed stage of the process.
    You can also see that the transport zone is applied to the hosts in the cluster.
    Note: If you again configure a host that is part of a cluster that is already prepared by a transport node profile, the configuration state of a node is in Configuration Mismatch state.
    Note: The Host Transport Node page displays TEP addresses of the host in addition to IP addresses. TEP address is the address assigned to the VMkernel NIC of the host, whereas IP address is the management IP address.
  15. (Optional) Remove an NSX VIBs on the host.
    1. Select one or more hosts and click Actions > Remove NSX.
    The uninstallation takes up to three minutes. Uninstallation of NSX removes the transport node configuration on hosts and the host is detached from the transport zone(s) and switch. Similar to the installation process, you can follow the percentage of the uninstallation process completed on each transport node. If uninstallation fails at any stage, you can restart the process by clicking the Resolve link that is available against the failed stage of the process.
  16. (Optional) Remove a transport node from the transport zone.
    1. Select a single transport node and click Actions > Remove from Transport Zone.

What to do next

When the hosts are transport nodes, you can create transport zones, logical switches, logical routers, and other network components through the NSX Manager UI or API at any time. When NSX Edge nodes and hosts join the management plane, the NSX logical entities and configuration state are pushed to the NSX Edge nodes and hosts automatically. You can create transport zones, logical switches, logical routers, and other network components through the NSX Manager UI or API at any time. When the hosts are transport nodes, these entities gets realized on the host.

Create a logical switch and assign logical ports. See the Advanced Switching section in the NSX Administration Guide.