Adding a logical switch on a replacement Secondary NSX Site fails.
book
Article ID: 309121
calendar_today
Updated On:
Products
VMware NSX
Issue/Introduction
Secondary site VC/PSC DB is lost, and in not recoverable state.
Secondary site gets removed from primary.
Secondary sites gets completely rebuilt.
Secondary and primary sites have unique UUIDs.
Running show logical-switch list all from both NSX managers and the VNI, says is in use on the controller does not exist on either the primary or the secondary.
Unable to add a logical switch on a replacement Secondary NSX Site, you see an error similar to:
Logical switch VNI “####” is already with controller. It belongs to the other NSX Manager with UUID ######.######.#######.#######.
The UUID being referenced is neither the primary nor secondary manager UUID and they are indeed both unique.
The UUID ########.########.########.######## was actually for the legacy non-existent secondary.
Environment
VMware NSX for vSphere 6.4.x VMware NSX for vSphere 6.2.x VMware NSX for vSphere 6.3.x
Cause
This issue occurs when the secondary NSX manager is not completely removed from the environment. The Universal Controller cluster was retaining records for the legacy non-existent secondary.
Resolution
To resolve this issue, delete the Universal NSX Controller cluster completely and re-add.
Remove all 3 universal controllers at once, the last controller will need to be removed forcefully.
Create all 3 universal controllers again, one by one, waiting from a "green" status to proceed to the next controller