Migration of VMkernel adapters is supported on transport nodes using an N-VDS or VDS host switch. In the scenario illustrated in this section, VMkernel-1 (vmk1) adapter is migrated to an N-VDS switch on a host where host profile is applied. The vmk1 adapter supports infrastructure traffic for vMotion, Fault Tolerance, and other infrastructure services.
Scenario | Error | Workaround |
---|---|---|
vmk1 migration on a standalone target host by applying reference host profile. | The target host is not configured as a transport node. As the target host does not know about any NSX-T objects, host profile application fails. Remediation of host profile on the target host fails. Error: Received SOAP response fault : generate HostConfigTask Spec.. |
|
vmk1 migration on target hosts in a stateful cluster. | Before applying the host profile to the target host, if you prepare the cluster by applying TN profile configured with vmk1 mapped to the logical switch, then vmk1 migration fails.Error: vmk1 missing on the host. |
|
vmk0 and vmk1 migration on a standalone host. | When configuring NSX-T on the standalone host, if the Network Mapping for Install field does not specify vmk0 or vmk1 mappings, then migration fails. | When configuring NSX-T on the target host, ensure that the Network Mapping for Install field is specified with vmk0 and vmk1 mapped to the same logical switch on the N-VDS. |
vmk0 and vmk1 migration on a cluster host. | When applying TN profile to a cluster, if the Network Mapping for Install field does not specify vmk0 or vmk1 mappings, then migration fails. | Apply TN profile to the cluster. When configuring TN profile to the cluster, ensure that Network Mapping for Install field is specified with vmk0 and vmk1 mapped to a logical switch on the N-VDS. |