The uplink name <Name> is not found error during workload cluster stretch in SDDC on stage Update NSX TransportNode Profile with SubCluster configuration.

Products

• VMware NSX

Issue/Introduction

When attempting to stretch a workload cluster in SDDC Manager, the task Update NSX TransportNode Profile with SubCluster configuration fails.
You may observe the following error message in the SDDC Manager UI:

Transport Node Collection update with subCluster failedCause: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) (statusCode:400) => { messages = [], data = => {error_message=Error while validating sub-Configuration with name <POOL_NAME> and Host Switch with Id <ID>., httpStatus=BAD_REQUEST, details=The uplink name uplink2 is not found in the [Uplink-1, Uplink-2] list of UplinkHostSwitchProfile BaseHostSwitchProfile/<PROFILE_ID>., error_code=9857, module_name=NsxSwitching service}, errorType = INVALID_REQUEST }

 

Cause

This issue occurs because of a naming mismatch between the uplink placeholders expected by SDDC Manager and those defined in the NSX Uplink Profile. For example, SDDC Manager may be looking for uplink2 while the NSX profile uses Uplink-2.

Resolution

To resolve this issue, you must modify the Uplink Profile in NSX to match the configuration expected by SDDC Manager:

• Log in to the NSX Manager UI.
• Navigate to System > Fabric > Profiles > Uplink Profiles.
• Locate the profile referenced in the error message.
• Edit the profile and update the Uplink Names (placeholders) to match the exact strings reported in the SDDC Manager error (e.g., change Uplink-2 to uplink2).
• Save the changes.
• Return to SDDC Manager and Restart the failed task.

 

Additional Information

For detailed steps on managing profiles, see Create an Uplink Profile.