After renaming a vSphere Distributed Switch (VDS) in vCenter Server, the NSX-T Manager's Host Details view may display inconsistent or duplicate VDS entries
Initially, two copies of the same VDS appear in the Host Details topology view
After restarting the NSX-T Proton service, only the original VDS name appears in the topology view
To confirm if this issue is occurring, compare the VDS name shown in the NSX-T UI with the API response fromcurl -k -u $NSX_USER:$NSX_PASS -X GET "$NSX_FQDN/api/v1/fabric/virtual-switches"
Where
$NSX_USER
: NSX Manager username$NSX_PASS
: NSX Manager password$NSX_FQDN
: The fully qualified domain name or IP of the NSX ManagerThe API response will show the correct VDS name under the "display_name" field, which should match what is set in vCenter Server. If the NSX-T UI shows a different name or duplicate entries, this issue is occurring.
The issue can be verified in the Host Details overview page topology view, where the visualization may show inconsistent VDS names compared to vCenter Server.
VMware vCenter
VMware NSX-T
Found in NSX-T version 3.2.3.1 and continuing until version 4.1, when a VDS is renamed in vCenter Server, sometimes the NSX-T topology visualization component does not properly sync the updated VDS name, resulting in inconsistent display of VDS names across different views. The underlying data model correctly maintains the new name, as evidenced by API responses, but the visual representation in the Host Details topology view does not update correctly, showing either duplicate entries or retaining the old name after a Proton service restart.
This issue requires an upgrade to NSX-T 4.1.0.0 build 20831298 or later versions to be resolved.
Upgrade to NSX-T 4.1 or later. After the upgrade: