Un-stretching vSAN Cluster fails with following errors in SDDC UI
| Description | Gather the AZ2 uplink profile for removal |
| Progress Messages | Unable to get input for NSX configuration |
|
Error |
Message: Unable to get input for NSX configuration |
|
Description |
Remove AZ2 NSX uplink profiles |
|
Progress Messages |
Invalid parameter: uplinkProfileId cannot be null |
| Error |
Invalid parameter: uplinkProfileId cannot be null |
|
Error |
Message: Invalid parameter: uplinkProfileId cannot be null Remediation Message:
|
VCF 5.2
The failure is caused by mismatched uplink and portgroup profile names, resulting from code differences between VCF versions 4.x and 5.x.
In VCF 5.x, the changes to profile naming conventions are hardcoded, which leads to failures if the expected naming pattern is not present.
Un-Stretch Failure – Workaround
Issue 1: Portgroup Not Found (Unable to get input for NSX configuration)
Log in to vCenter.
Navigate to the affected host and go to the Network tab.
Identify all connected portgroups on the impacted host.
Rename each portgroup by adding the prefix az_ to the existing name.
(Example: az_<existing-portgroup-name>)
Retry the Un-Stretch Workflow from SDDC Manager.
Issue 2: Uplink Profile Not Found (uplinkProfileId cannot be null)
Log in to the NSX Manager.
Navigate to: System > Fabric > Hosts, and locate the AZ2 hosts.
Click Configure on one of the hosts and click Next to view the current uplink profile name.
Then go to: System > Fabric > Profiles > Uplink Profiles.
Rename the relevant uplink profile by adding the prefix az2_ to the existing name.
(Example: az2_<existing-profile-name>)
Retry the Un-Stretch operation in SDDC Manager.