Global Manager connectivity to compute manager fails after configuring multi site on Local Manager's compute manager

Products

• VMware NSX

Issue/Introduction

• NSX-T Version up to and including 3.2.3 
• Global Manager (GM) to Compute Manager (CM) shows Registration Status as "Not Registered" with Connection Status as "Down".

 

• You may see the following or similar entries in the NSX Manager log file /var/log/cm-inventory/cm-inventory.log

 

2024-03-28T10:41:35.052Z INFO task-executor-4 CmValidationService 73939 FABRIC [nsx@6876 comp="global-manager" level="INFO" subcomp="cm-inventory"] Custom extension found for server x.x.x.x returning true
2024-03-28T10:41:35.194Z WARN task-executor-4 CmInventoryService 73939 FABRIC [nsx@6876 comp="global-manager" level="WARNING" subcomp="cm-inventory"] Registration failed for compute manager xxxxxxxxxxxxxxxxxxxxxxxxxxxxx , issue Compute manager might be already registered in another NSX with Multi NSX enabled. Please resolve the error to register again and unregister compute manager from another NSX if already registered.
com.vmware.nsx.management.cminv.exceptions.CmPluginRegistrationFailedException: Compute manager might be already registered in another NSX with Multi NSX enabled. Please resolve the error to register again and unregister compute manager from another NSX if already registered.
        at com.vmware.nsx.management.cminv.vcplugin.VcPlugin.validateExtensionForMultiNsx(VcPlugin.java:292) ~[libcm-inv-container.jar:?]
        at com.vmware.nsx.management.cminv.vcplugin.VcPlugin.register(VcPlugin.java:218) ~[libcm-inv-container.jar:?]
        at com.vmware.nsx.management.cminv.vcplugin.VcPlugin.register(VcPlugin.java:363) ~[libcm-inv-container.jar:?]
        at com.vmware.nsx.management.cminv.service.CmPluginManagerImpl.register(CmPluginManagerImpl.java:84) ~[libcm-inv-container.jar:?]
        at com.vmware.nsx.management.cminv.computemanager.service.CmInventoryService.registerWithComputeManager(CmInventoryService.java:384) ~[libcm-inv-container.jar:?]
        at com.vmware.nsx.management.cminv.computemanager.service.CmRegistrationTask.run(CmRegistrationTask.java:49) ~[libcm-inv-container.jar:?]
        at com.vmware.nsx.management.common.executor.TaskExecutorImpl$TaskWrapper$1.run(TaskExecutorImpl.java:238) ~[libmp_common.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_372]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_372]
        at com.vmware.nsx.management.common.executor.TaskExecutorImpl$TaskWrapper.run(TaskExecutorImpl.java:271) ~[libmp_common.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_372]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_372]
        at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_372]

Environment

VMware NSX-T Data Center

Cause

Registration or modification to the compute manager of Global Manager is not permitted when the same Compute Manager is registered with multiple NSX instances enabled on the Local Manager.

Resolution

This issue is resolved in VMware NSX 4.1.0 and above.

Additional Information

Impact/Risks:
The disruption in global manager connectivity to compute manager, resulting from configuring multi-site on Local Manager's compute manager, significantly impacts several functionalities within NSX.