An NSX Manager can have roles, such as primary, secondary, standalone, or transit. Special synchronization software runs on the primary NSX Manager, synchronizing all universal objects to secondary NSX Managers.
It is important to understand what happens when you change an NSX Manager's role.
- Set as primary
- This operation sets the role of an NSX Manager to primary and starts the synchronization software. This operation fails if the NSX Manager is already the primary or already a secondary.
- Set as standalone (from secondary)
- This operation sets the role of NSX Manager to standalone or transit mode. This operation might fail if the NSX Manager already has the standalone role.
- Set as standalone (from primary)
This operation resets the primary NSX Manager to standalone or transit mode, stops the synchronization software, and unregisters all secondary NSX Managers. This operation might fail if the NSX Manager is already standalone or if any of the secondary NSX Managers are unreachable.
- Disconnect from primary
When you run this operation on a secondary NSX Manager, the secondary NSX Manager is unilaterally disconnected from the primary NSX Manager. This operation should be used when the primary NSX Manager has experienced an unrecoverable failure, and you want to register the secondary NSX Manager to a new primary. If the original primary NSX Manager does come up again, its database continues to list the secondary NSX Manager as registered. To resolve this issue, include the force option when you disconnect or unregister the secondary from the original primary. The force option removes the secondary NSX Manager from the original primary NSX Manager's database.