Scenario 1. Receiving error when trying to remove NSX backed host from unwanted VDS.
Scenario 2. To fix the VDS out of sync issue , need to remove the ESXi from cluster and re-add it back to VCSA Cluster / VDS.
Error that we see from VDS " The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server."
and when try to remove the host from cluster you may see "The operation is not supported on the object. Not allowed to remove nsxBacked host XXXX from dvs XXXX"
NSX 4.X
NSX 3.X
Scenario 1. For 'Security Only' deployment , this error occurs because this NSX cluster which is deployed via Quick Start wizard with automation. This type of NSX deployment is limited in that by design and it cannot be customized after deployment.
Scenario 2. NSX Configured cluster wont let remove the ESXi unless the NSX is uninstalled from the ESXi
Scenario 1. For 'Security Only' - The recommendation is to un-deploy NSX from the hosts, then remove the unneeded VDS, and redeploy NSX Security Only.
Scenario 2. Below Steps needs to be followed to fix VDS out of sync if its part of NSX cluster
Step 1 : In vCenter Server, put the ESXi host that needs to be removed from NSX into maintenance mode.
Step 2 : Move the ESXi host from the cluster to Datacenter object in the vCenter inventory. This will trigger the un-install of NSX from the ESXi host.
Step 3 : Check in the NSX UI if the ESXi host goes into 'Not Configured' state. Also make sue the host no longer has any nsx vibs using : "esxcli software vib list | grep nsx " in an ssh for the host.
Step 4 : Disconnect the ESXi and remove from Inventory.
Step 5 : Re-add the ESXi to Datacenter object in the vCenter inventory and add it back to respective VDS.
Step 6 : Drag and Drop the ESXi back to NSX Cluster and this will trigger installation of NSX.
Step 7 : Verify the status to see if VIBs / VTEPs are configured and check if there are any errors from NSX UI and proceed accordingly.