NSX-T N-VDS to VDS Migration applying Topology Fails with "APPLY_TOPOLOGY_FAILED"

Products

• VMware NSX

Issue/Introduction

• In NSX-T 3.2.x environments, when attempting to perform NVDS to VDS migration, the following API call may return a failed status:
  
GET https://<nsx-mgr>/api/v1/nvds-urt/status-summary/<precheck-id>
  
  The output may include an error similar to:
  
  { "precheck_id": "########-####-####-####-########1ade", "precheck_status": "FAILED", "precheck_issue": [ { "component": "Uplink profile", "objid": "N-VDS-###", "error": "Found inconsistent profiles: [########-####-####-####-########faf2, ########-####-####-####-########ab9d]. Uplink profile mismatch. Teaming mismatch.", "recommendation": "Keep profiles consistent among transport nodes in the same NVDS", "_protection": "NOT_PROTECTED" } ] }
  
  
• You may also find related errors in the /var/log/syslog and in /var/log/proton/nsxapi.log indicating APPLY_TOPOLOGY_FAILED and missing required properties like precheck_issue or migration_state:

<Timestamp>  INFO http-nio-127.0.0.1-7440-exec-55 NvdsUpgradeReadinessCheckServiceImpl 15103 FABRIC [nsx@6876 >comp="nsx-manager" level="INFO" reqId="######" subcomp="manager" username="admin"] NVDS-UPGRADE >getNvdsUpgradeSummary precheckId ####### upgradeState APPLY_TOPOLOGY_FAILED
<Timestamp> WARN http-nio-127.0.0.1-7440-exec-55 FacadeInterceptorHelperImpl 15103 - [nsx@6876 comp="nsx-manager" >level="WARNING" reqId="#######" subcomp="manager" username="admin"] API result did not pass >validationField level validation errors: {required property precheck_issue is missing}, {required property migration_state is missing}

Environment

NSX-T Data Center 3.2.x

Cause

The failure is caused by a mismatch in Uplink Profiles applied to transport nodes within the same NVDS. Specifically, the teaming policies configured in the Uplink Profiles are not consistent with the teaming configuration required by the Transport Zone associated with the TNP attached to the cluster.

Resolution

Workaround:

1. Create a New Uplink Profile:

   • Ensure it has the correct teaming policy to match the Transport Zone configuration attached to the TNP.

2. Modify the Affected TNP:

   • Navigate to System > Fabric > Hosts > Transport Node Profiles

   • Edit the TNP attached to the affected cluster.

   • Under Host Switch, click the number shown and then click Edit.

   • Remove the old Uplink Profile.

   • Add the newly created Uplink Profile with correct teaming.

   • Ensure all vmnics, uplinks, and configurations match the original setup.

   • Click Add, then Apply, then Save the TNP.

3. Clean Up NVDS to VDS Migration State:

   • Run the following cleanup API:

      

     POST https://<NSX_manager>/api/v1/nvds-urt?action=cleanup

4. Rerun Prechecks and Migrate Hosts:

   • Re-run the NVDS to VDS prechecks.

   • Ensure all hosts show as UPGRADE_READY.

   • Place each host in Maintenance Mode.

   • Proceed with migrate-to-vds API for each host.

Additional Information

• Ensure uplink and teaming settings are identical across all hosts in the same NVDS.

• Any mismatch in the number of uplinks, names, or teaming policies will cause applying the topology to fail.

• Related log entries may be found in nsxapi.log on the NSX Manager:

   

  upgradeState APPLY_TOPOLOGY_FAILED validation errors: {required property precheck_issue is missing}, {required property migration_state is missing}

   
   

Other relevant KB for VDS migration Failure: NSX-T N-VDS to VDS Migration pre-check fails: "Keep profiles consistent among transport nodes in the same NVDS"