When adding the compute manager to the standby global manager it fails.

Products

• VMware NSX

Issue/Introduction

• The compute manager configured in our standby global manager is failing to connect.
• When configuring a federated standby site, attempts to configure the compute manager fail with the following error message.
  
  Compute manager <vCenter IP Address or FQDN> is not registered with the NSX manager. (Error code: 7098)

Environment

Vmware NSX Federated 

Cause

• This is expected behavior.

• This is an example of a topology that will work.
• Note that each site has only a single vCenter that the managers are registered to.
• No compute registration from any manger in the active site has a registration pointing to the Standby Site vCenter.
• No compute registration from any manger in the Standby site has a registration pointing to the Active Site vCenter.

Testing:

• Attempt to re-register to vCenter - FQDN.  It will Fail.
• Attempt to re-register to vCenter - IP.   It will Fail.
• Use curl -kv https:// <vcenter IP>   does it connect yes (port 443 open)   no (port 443 closed)   It will be successful passing traffic using port 443.
• Check configured vCenter thumbprint is correct.  The thumb print will be correct.

Validate the actual topology

• This topology has the active global manager cluster registered to both active and standby vCenter servers (vCenter-1, vCenter-2).
  • Rule: There can only be one global manager cluster registered to any single compute manager (vCenter) per site.
  • The standby site vCenter-2 has the Active Site global manager registered to it.
  • vCenter-2 can only have a single global manager registered, which is presently the active site global manager.
  • When the standby site global manager attempts to register with vCenter-2 it fails.  There is already a global manager registered.
• The Standby Site vCenter has the Active Global manager registered to it. 
• Standby site vCenter-2 cannot have another Global manager cluster registered to it.
• The Standby Site Global manager cannot be registered to it vCenter since vCenter-2 already has the global manager from the active site registered to it.

Resolution

1. Remove the active global manager site compute registration configuration that is pointing to the standby site vCenter-2 server.
   There should only be a single registration seen in its compute manager list.
   
   
2. Register the stand by site global manager cluster with the standby site vCenter-2 server as its compute manager.