V2T migration of esxi host transport nodes fail with error "uplink name is not found in the list of UplinkHostSwitchProfile" when active uplinks in DVPG's do not match with VDS uplink profile.

Products

• VMware NSX

Issue/Introduction

Symptoms:
During Host migration stage of V2T with VDS of 7.0 and newer versions, migration fails with error "uplink name is not found in the list of UplinkHostSwitchProfile"

Similar logs as below will be observed in  /var/log/migration-coordinator/v2t/cm.log

 2022-09-11 03:02:33,800 32235 CM.clients.base_client ERROR Failed to POST [http://localhost:7440/nsxapi/api/v1/fabric/discovered-nodes/########-####-####-####-##########0e:host-1405554?action=create_transport_node](http://localhost:7440/nsxapi/api/v1/fabric/discovered-nodes/########-####-####-####-##########0e:host-1405554?action=create_transport_node "http://localhost:7440/nsxapi/api/v1/fabric/discovered-nodes/########-####-####-####-##########0e:host-1405554?action=create_transport_node") with status: 400 and reason: { 
 "httpStatus" : "BAD_REQUEST", 
 "error_code" : 8217, 
 "module_name" : "NsxSwitching service", 
 "error_message" : "The uplink name Uplink 3 is not found in the [Uplink 2, Uplink 1] list of UplinkHostSwitchProfile BaseHostSwitchProfile/########-####-####-####-##########0e." 
} 
2022-09-11 03:02:33,801 32235 CM.engine.xlate_engine INFO --------------- Stage runtime: error

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX-T Data Center 3.x
VMware NSX-T Data Center

Cause

This issues occurs in environments where any VDS uplink is not used by any DVPG's uplink teaming policy of "explicit failover order" with only one active uplink and is not among the active uplinks of all other DVPG's uplink teaming policy in the VDS.

In such a case, the host-switch uplink profile generated by V2T Migration Coordinator for the VDS does not have that VDS uplink, but the profile-uplink to vds-uplink map in the transport-node spec created by V2T Migration Coordinator for a host has all uplinks of the VDS. This fails the transport node creation API.


For example :

• If customer has a VDS uplink profile with 4 uplinks as below:

• If the customer modified the Failover order and changed the active uplinks in all DVPGs' uplink teaming policy in the VDS as below, then "Uplink 3" and "Uplink 4" won't appear in the host-switch uplink profile generated by V2T Migration Coordinator for the VDS, and any host joins this VDS will fail to migrate because of this issue during V2T migration.

Resolution

NA

Workaround:

Before starting the V2T Migration, perform one of the below actions as workaround

 1. Change an existing DVPG's uplink teaming policy to use all uplinks of the VDS in the active uplink list.

 2. Create a new DVPG with the default VDS uplink teaming which has all uplinks in the active uplink list before starting the V2T migration.
 

If migration started and failed during host migration stage, perform the below steps as workaround

1. Copy the UplinkHostSwitchProfile UUID in the error message, e.g. "########-####-####-####-##########0e" in error message

 "The uplink name dvUplink3 is not found in the [dvUplink2, dvUplink1] list of UplinkHostSwitchProfile BaseHostSwitchProfile/########-####-####-####-##########0e.".

2. Using above copied UID find the UplinkHostSwitchProfile in NSXT UI elastic search.
3. Edit the UplinkHostSwitchProfile to add a named teaming policy with type "LOADBALANCE_SRCID" and all uplinks (Uplink 1, Uplink 2, Uplink 3, Uplink 4 in this bug case) of the VDS that are not in the UplinkHostSwitchProfile.


4. If the name of the UplinkHostSwitchProfile contains "-VXLAN" (e.g. VDS1-UplinkProfile-VXLAN_0), find the UplinkHostSwitchProfile whose name is the same except the "-VXLAN" sub string (e.g. VDS1-UplinkProfile_0), and add the same named teaming policy in this UplinkHostSwitchProfile.



5. Retry the host migration.

 

Additional Information

Impact/Risks:
Migration of hosts from NSX-V to NSX-T will fail.
This issue is found on NSX-T 3.1.x, NSX-T 3.2.x  and above releases.