A transport node profile captures the configuration required to create a transport node. The transport node profile can be applied to an existing vCenter Server cluster to create transport nodes for the member hosts. Transport node profiles define transport zones, member hosts, N-VDS switch configuration including uplink profile, IP assignment, mapping of physical NICs to uplink virtual interfaces and so on.
Transport node creation begins when a transport node profile is applied to a vCenter Server cluster. NSX Manager prepares the hosts in the cluster and installs the NSX-T Data Center components on all the hosts. Transport nodes for the hosts are created based on the configuration specified in the transport node profile.
To delete a transport node profile, you must first detach the profile from the associated cluster. The existing transport nodes are not affected. New hosts added to the cluster are no longer automatically converted into transport nodes.
- You can add a maximum of four N-VDS switches for each configuration: enhanced N-VDS created for VLAN transport zone, standard N-VDS created for overlay transport zone, enhanced N-VDS created for overlay transport zone.
- There is no limit on the number of standard N-VDS switches created for VLAN transport zone.
- In a single host cluster topology running multiple standard overlay N-VDS switches and edge VM on the same host, NSX-T Data Center provides traffic isolation such that traffic going through the first N-VDS is isolated from traffic going through the second N-VDS and so on. The physical NICs on each N-VDS must be mapped to the edge VM on the host to allow the north-south traffic connectivity with the external world. Packets moving out of a VM on the first transport zone must be routed through an external router or an external VM to the VM on the second transport zone.
- Each N-VDS switch name must be unique. NSX-T Data Center does not allow use of duplicate switch names.
- Each transport zone ID must be unique. NSX-T Data Center does not allow use of duplicate IDs.
- You can add a maximum of 1000 transport zones in the transport node profile.
- To add a transport zone, it must be realized by any N-VDS present in the transport node profile.
- Verify that the hosts are part of a vCenter Server cluster.
vCenter Server must have at least one cluster.
- Verify that a transport zone is configured. See Create Transport Zones.
- Verify that a cluster is available. See Deploy NSX Manager Nodes to Form a Cluster from UI.
- Verify that an IP pool is configured, or DHCP must be available in the network deployment. See Create an IP Pool for Tunnel Endpoint IP Addresses.
- Verify that a compute manager is configured. See Add a Compute Manager.
- From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
- Select .
- Enter a name to identify the transport node profile.
You can optionally add the description about the transport node profile.
- Select the available transport zones and click the > button to include the transport zones in the transport node profile.
Note: You can add multiple transport zones.
- Click the N-VDS tab and enter the switch details.
Option Description N-VDS Name
If the transport node is attached to a transport zone, then ensure the name entered for the N-VDS is the same as the N-VDS name specified in the transport zone. A transport node can be created without attaching it to a transport zone.
Associated 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 N-VDS in the transport node profile.
NIOC Profile Select the NIOC profile from the drop-down menu.
The bandwidth allocations specified in the profile for the traffic resources are enforced.
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.
LLDP Profile By default, NSX-T only receives LLDP packets from a LLDP neighbor.
However, NSX-T can be set to send LLDP packets to and receive LLDP packets from a LLDP neighbor.
IP Assignment Select Use DHCP, Use IP Pool, or Use Static IP List to assign an IP address to virtual tunnel endpoints (VTEPs) of the transport node.
If you select Use Static IP List, you must specify a list of comma-separated IP addresses, a gateway, and a subnet mask. All the VTEPs of the transport node must be in the same subnet otherwise bidirectional flow (BFD) session is not established.
IP Pool If you selected Use IP Pool for an IP assignment, specify the IP pool name. Physical NICs
Add physical NICs to the transport node. You can use the default uplink or assign an existing uplink from the drop-down menu.
Click Add PNIC to configure additional physical NICs to the transport node.Note: Migration of the physical NICs that you add in this field depends on how you configure PNIC only Migration, Network Mappings for Install, and Network Mappings for Uninstall.
- To migrate a used physical NIC (for example, by a standard vSwitch or a vSphere distributed switch) without an associated VMkernel mapping, ensure that PNIC only Migration is enabled. Otherwise, the transport node state remains in partial success, and the fabric node LCP connectivity fails to establish.
To migrate a used physical NIC with an associated VMkernel network mapping, disable PNIC only Migration and configure the VMkernel network mapping.
To migrate a free physical NIC, enable PNIC only Migration.
PNIC only Migration
Before setting this field, consider the following points:
- Know whether the physical NIC defined is a used NIC or a free NIC.
- Determine whether VMkernel interfaces of a host need to be migrated along with physical NICs.
Set the field:
On a host with multiple host switches:
Enable PNIC only Migration if you only want to migrate physical NICs from a VSS or DVS switch to an N-VDS switch.
Disable PNIC only Migration if you want to migrate a used physical NIC and its associated VMkernel interface mapping. A free or available physical NIC is attached to the N-VDS switch when a VMkernel interface migration mapping is specified.
- If all host switches are to migrate only PNICs, then you can migrate the PNICs in a single operation.
- If some hosts switches are to migrate VMkernel interfaces and the remaining host switches are to migrate only PNICs:
- In the first operation, migrate only PNICs.
- In the second operation, migrate VMkernel interfaces. Ensure that PNIC only Migration is disabled.
Both PNIC only migration and VMkernel interface migration are not supported at the same time across multiple hosts.Note: To migrate a management network NIC, configure its associated VMkernel network mapping and keep PNIC only Migration disabled. If you only migrate the management NIC, the host loses connectivity.
For more information, see VMkernel Migration to an N-VDS Switch.
Network Mappings for Install
To migrate VMkernels to N-VDS switch during installation, map VMkernels to an existing logical switch. The NSX Manager migrates the VMkernel to the mapped logical switch on N-VDS.Caution: Ensure that the management NIC and management VMkernel interface are migrated to a logical switch that is connected to the same VLAN that the management NIC was connected to before migration. If vmnic <n> and VMkernel <n> are migrated to a different VLAN, then connectivity to the host is lost.Caution: For pinned physical NICs, ensure that the host switch mapping of physical NIC to a VMkernel interface matches the configuration specified in the transport node profile. As part of the validation procedure, NSX-T Data Center verifies the mapping and if the validation passes migration of VMkernel interfaces to an N-VDS switch is successful. It is also mandatory to configure the network mapping for uninstallation because NSX-T Data Center does not store the mapping configuration of the host switch after migrating the VMkernel interfaces to the N-VDS switch. If the mapping is not configured, connectivity to services, such as vSAN, can be lost after migrating back to the VSS or VDS switch.
For more information, see VMkernel Migration to an N-VDS Switch .
Network Mappings for Uninstall
To revert the migration of VMkernels during uninstallation, map VMkernels to port groups on VSS or DVS, so that NSX Manager knows which port group the VMkernel must be migrated back to on the VSS or DVS. For a DVS switch, ensure that the port group is of the type Ephemeral.Caution: For pinned physical NICs, ensure that the transport node profile mapping of physical NIC to VMkernel interface matches the configuration specified in the host switch. It is mandatory to configure the network mapping for uninstallation because NSX-T Data Center does not store the mapping configuration of the host switch after migrating the VMkernel interfaces to the N-VDS switch. If the mapping is not configured, connectivity to services, such as vSAN, can be lost after migrating back to the VSS or VDS switch.
For more information, see VMkernel Migration to an N-VDS Switch.
- To add another N-VDS switch, click + ADD N-VDS.
- Click Save to complete configuration.
What to do next
Apply the transport node profile to an existing vSphere cluster. See Configure a Managed Host Transport Node.