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

Important: On a stateless target host:
  • (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 Reference Host Configuration Steps To Auto Deploy Target Hosts
Target host has vmk0 adapter configured.

The host profile extracted from the reference host has vmk0 configured on an N-VDS switch.

In NSX-T, TNP has only vmk0 migration mapping configured.
  1. Attach the host profile to the target host.

    The vmk0 adapter is attached to a vSwitch.

  2. Update host customizations, if required.
  3. Reboot the host. The host profile is applied to the host. vmk0 is attached to a temporary switch.
  4. Apply TNP.

    The vmk0 adapter migrates to N-VDS.

The target host is successfully deployed with ESXi and NSX-T VIBs.
Target host has vmk0 adapter configured.

The host profile extracted from the reference host has vmk0 on vSwitch and vmk1 is on an N-VDS switch.

In NSX-T, TNP has only vmk1 migration mapping configured.
  1. Attach the host profile to the target host.

    The vmk0 adapter is attached to a vSwitch, but vmk1 is not realized on any switch.

  2. Update host customizations, if required.
  3. Reboot the host.

    vmk0 is attached to a vSwitch and vmk1 is attached to a temporary NSX switch.

  4. Apply TNP.

    The vmk1 adapter migrates to N-VDS.

  5. (optional) If the host remains non-compliant with the host profile, reboot the host to make the host compliant.
The target host is successfully deployed with ESXi and NSX-T VIBs.
Target host has vmk0 adapter configured.

The host profile extracted from the reference host has vmk0 is configured on a vSwitch and vmk1 is configured on an N-VDS switch.

In NSX-T, TNP has vmk0 and vmk1 migration mappings configured.
  1. Attach the host profile to the target host.

    The vmk0 adapter is attached to a vSwitch, but vmk1 is not realized on any switch.

  2. Update host customizations, if required.
  3. Reboot the host.

    The vmk0 adapter is attached to a vSwitch and vmk1 is attached to a temporary NSX switch.

  4. Apply TNP.
  5. (optional) If the host remains non-compliant with the host profile, reboot the host to make the host compliant.

The target host is successfully deployed with ESXi and NSX-T VIBs.
Target host has vmk0 and vmk1 adapters configured.

The host profile extracted from the reference host has vmk0 on vSwitch and vmk1 configured on an N-VDS switch.

In NSX-T, TNP has a vmk1 migration mapping configured.
  1. Attach the host profile to the target host.

    The vmk0 and vmk1 adapters are attached to a vSwitch.

  2. Update host customizations, if required.
  3. Reboot the host.
  4. Apply TNP.

    The vmk0 adapter is attached to a vSwitch and vmk1 is attached to an N-VDS switch.

  5. (optional) If the host remains non-compliant with the host profile, reboot the host to make the host compliant.

The target host is successfully deployed with ESXi and NSX-T VIBs.
Target host has vmk0 and vmk1 adapters configured.

The host profile extracted from the reference host has vmk0 and vmk1 configured on an N-VDS switch.

In NSX-T, TNP has vmk0 and vmk1 migration mappings configured.
  1. Attach the host profile to the target host.

    The vmk0 and vmk1 adapters are attached to a vSwitch.

  2. Update host customizations, if required.
  3. Reboot the host.
  4. Apply TNP.

    The vmk0 and vmk1 are migrated to an N-VDS switch.

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