vSphere Distributed Switch name mismatch between SDDC Manager and vCenter causing NSX sync failure in VCF

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

This article addresses an issue where renaming a vSphere Distributed Switch (vDS) in vCenter causes synchronization failures in SDDC Manager and NSX Manager. This typically occurs when an "out-of-band" change is made without reconciling the SDDC Manager inventory.

• SDDC Manager displays a "Configuration Drift" warning or "Out of Sync" status for the vDS.
• NSX Manager does not reflect the new vDS name in Transport Node Profiles.
• Cluster expansion or removal tasks fail with the error: Expected 1 but did not find any MORs of a type DistributedVirtualSwitch and name vds-####.

Environment

• VMware Cloud Foundation 5.2 and higher
• Corresponding vCenter 8.0 U3a build 24091160 and higher
• Corresponding NSX 4.2.0.0.0 build 24105817 and higher

Cause

Renaming a vDS directly in vCenter modifies the name attribute but preserves the UUID. If the change is not synced to SDDC Manager, the internal PostgreSQL database (platform DB) retains the old name, leading to a mismatch when the workflow attempts to locate the Managed Object Reference (MOR) by name.

Resolution

Resolution for VCF 5.2 or later only.

1. Verify the current recorded name in SDDC Manager by navigating to Inventory > Workload Domains > [Domain] > Clusters > [Cluster] > Network.
2. In vCenter, navigate to the Networking view.
3. Right-click the vDS and select Rename.
4. Change the name to match the value recorded in SDDC Manager or the desired name.
5. Wait approximately 5 minutes for the change to propagate to NSX Manager.
6. Refresh NSX Manager UI to reflect changes.
7. Refresh SDDC Manager UI to reflect changes.

Additional Information

Renaming VCF SDDC manager objects

To speak with a customer representative or a Support Engineer, see Contact Support.