If you have a vCenter Server cluster, you can automate the installation and creation of transport nodes on all the NSX-T hosts in single or multiple clusters instead of configuring manually.

About this task

Note:

Automated NSX-T transport node creation is supported only on vCenter Server 6.5 Update 1 and 6.5 GA.

If the transport node is already configured, then automated transport node creation is not applicable for that node.

Prerequisites

  • The host must be part of a vCenter Server cluster.

  • 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.

  • vCenter Server should have at least one cluster.

  • A compute manager must be configured.

Procedure

  1. From your browser, log in to an NSX Manager at https://nsx-manager-ip-address.
  2. Select Fabric > Nodes > Hosts.
  3. From the Managed by drop-down menu select an existing compute manager.
  4. Select a cluster and click Configure Cluster.
  5. Complete the configure cluster details.

    Option

    Description

    Automatically Install NSX

    Toggle the button to enable the installation of NSX-T on all the hosts in the vCenter Server cluster.

    Automatically Create Transport Node

    Toggle the button to enable the transport node creation on all the hosts in the vCenter Server cluster.

    Note:

    This is a required setting.

    Transport Zone

    Select an existing transport node from the drop-down menu.

    Uplink Profile

    Select an existing uplink profile from the drop-down menu or create a custom uplink profile.

    Note:

    The hosts in a cluster must have the same uplink profile.

    You can also use the default uplink profile.

    IP Assignment

    Select either Use DHCP or Use IP Pool from the drop-down menu.

    If you select Use IP Pool, you must allocate an existing IP pool in the network from the drop-down menu.

    Physical NICs

    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 is partially successful, and the fabric node LCP connectivity fails to establish.

    You can use the default uplink or assign an existing uplink from the drop-down menu.

    Click Add PNIC to increase the number of NICs in the configuration.

    NSX-T installation and transport node creation on each host in the cluster starts in parallel. The entire process depends on the number of hosts in the cluster.

    When a new host is added to the vCenter Server cluster, NSX-T installation and transport node creation happens automatically.

  6. (Optional) : View the ESXi connection status.
    # esxcli network ip connection list | grep 1234
    tcp   0   0  192.168.210.53:20514  192.168.110.34:1234   ESTABLISHED  1000144459  newreno  netcpa
     
    
  7. (Optional) : Remove an NSX-T installation and transport node from a host in the cluster.
    1. Select a cluster and click Configure Cluster.
    2. Toggle the Automatically Install NSX button to disable the option.
    3. Select one or more host and click Uninstall NSX.

    The uninstallation takes up to three minutes.