This section discusses use cases when a stateless host exists outside of the target cluster.

Important: On stateless hosts:
  • (On an N-VDS switch) Migration of vmk0 adapter from VSS/DVS to N-VDS is not supported on NSX-T 2.4 and NSX-T 2.4.1.
  • (On an N-VDS switch) Migration of vmk0 adapter from VSS/DVS to N-VDS is supported on NSX-T 2.5.
  • (On a VDS switch) Migration of VMkernel adapters is not supported.
.
Target Host State Reference Host Configuration Steps To Auto Deploy Target Hosts

Host is in powered-off state (first-time start). It is later added to the cluster.

The default auto-deploy rule is configured for the target cluster and associated with the host profile.

The TNP is applied on the cluster.

The host profile extracted from the reference host has VMkernel adapter 0 (vmk0) on vSwitch and VMkernel adapter 1 (vmk1) configured on an N-VDS switch.

In NSX-T, TNP has only vmk1 migration mapping configured.
  1. Power on the host.
    After the host is powered on.

    • The host gets added to cluster.

    • The host profile is applied on the target host.

    • The vmk0 adapter is on vSwitch and vmk1 adapter is on a temporary switch.
    • TNP is triggered.
    • After TNP is applied to cluster, the vmk0 adapter is on vSwitch and vmk1 is migrated to the N-VDS switch.
  2. (Optional) If the host remains non-compliant with the host profile, reboot the host to make the host compliant.

    The host is successfully deployed with ESXi and NSX-T VIBs.

Host is in powered-off state (first-time start). It is later added to the cluster.

The default auto-deploy rule is configured for the target cluster and associated to the host profile.

The TNP is applied on the cluster.

The host profile extracted from the reference host has VMkernel adapter 0 (vmk0) and VMkernel adapter 1 (vmk1) configured on an N-VDS switch.

In NSX-T, TNP has vmk0 and vmk1 migration configured.
  1. Power on the host.
    After the host is powered on.

    • The host gets added to cluster.

    • The host profile is applied on the target host.

    • The vmk0 and vmk1 adapters are on a temporary switch.
    • TNP is triggered.
    • After TNP is applied to cluster, the vmk0 and vmk1 are migrated to the N-VDS switch.

The host is successfully deployed with ESXi and NSX-T VIBs.

Host is in powered-on state. It is later added to the cluster.

The default auto-deploy rule is configured for the target cluster and associated to the host profile.

Target host only has a vmk0 adapter configured on it.

The host profile extracted from the reference host has VMkernel adapter 0 (vmk0) on vSwitch and VMkernel adapter 1 (vmk1) configured on an N-VDS switch.

In NSX-T, TNP has a vmk1 migration mapping configured.
  1. Move the host to be part of the cluster.
  2. Reboot the host.

    After the host is rebooted the host profile is applied on the target host.

    • The vmk0 adapter is attached to a vSwitch, whereas the vmk1 adapter is attached to a temporary NSX switch.
    • TNP is triggered.
    • vmk1 is migrated to the N-VDS switch.
  3. (Optional) If the host remains non-compliant with the host profile, reboot the host to make the host compliant.

The host is successfully deployed with ESXi and NSX-T VIBs.

Host is in powered-on state. It is later added to the cluster.

The default auto-deploy rule is configured for the target cluster and associated to the host profile.

Target host only has a vmk0 adapter configured on it.

The host profile extracted from the reference host has VMkernel adapter 0 (vmk0) and VMkernel adapter 1 (vmk1) configured on N-VDS.

In NSX-T, TNP has vmk0 and vmk1 migration configured.
  1. Move the host to be part of the cluster.
  2. Reboot the host.

    After the rebooting the host, the host profile is applied to the target host.

    • The vmk0 and vmk1 adapters are attached to a temporary NSX switch.
    • TNP is triggered.
    • vmk0 and vmk1 are attached to an N-VDS switch.

The host is successfully deployed with ESXi and NSX-T VIBs.

Host is in powered-on state. It is later added to the cluster.

The default auto-deploy rule is configured for the target cluster and associated to the host profile.

Target host has vmk0 and vmk1 network mapping configured.

The host profile extracted from the reference host has VMkernel adapter 0 (vmk0) on vSwitch and VMkernel adapter 1 (vmk1) configured on an N-VDS switch.

In NSX-T, TNP has a vmk1 migration configured.
  1. Move the host to be part of the cluster.
  2. Reboot the host.

    After the host is rebooted the host profile is applied on the target host.

    • The vmk0 adapter is attached to a vSwitch, whereas the vmk1 adapter is attached to a temporary NSX switch.
    • TNP is triggered.
    • vmk1 is migrated to the N-VDS switch.
  3. (Optional) If the host remains non-compliant with the host profile, reboot the host to make the host compliant.

The host is successfully deployed with ESXi and NSX-T VIBs.

Host is in powered-on state. It is later added to the cluster.

The default auto-deploy rule is configured for the target cluster and associated to the host profile.

Host has vmk0 and vmk1 network mapping configured.

In the reference host, the host profile has VMkernel adapter 0 (vmk0) and VMkernel adapter 1 (vmk1) configured on an N-VDS switch.

In NSX-T, TNP has vmk0 and vmk1 migration configured.
  1. Move the host to be part of the cluster.
  2. Reboot the host.

    After the host is rebooted the host profile is applied on the target host.

    • The vmk0 and vmk1 adapters are attached to a temporary NSX switch.
    • TNP is triggered.
    • The vmk0 and vmk1 adapters are migrated to the N-VDS switch.

The host is successfully deployed with ESXi and NSX-T VIBs.