The state of HCX manager in deactivate state and site pairing state as disconnected

Products

• VMware HCX

Issue/Introduction

 

This behavior was observed on  HCX UI  in 'Connector' site though the cloud site was showing site pairing connected.  

The 'Connector' site app.log contains following entries

[NetworkStretchService_SvcThread-1166, Ent: HybridityAdmin, , TxId: ########-####-####-####-##########] WARN  c.v.v.h.inventory.InventoryAdapter- Can not collect resources from the cloud: https://##.##.##.##
java.lang.Exception: Remote cloud registration record is invalid
        at com.vmware.vchs.hybridity.inventory.InventoryAdapter.getRemoteCloudResources(InventoryAdapter.java:2188)
        at com.vmware.vchs.hybridity.inventory.InventoryAdapter.collectCloudResources(InventoryAdapter.java:1648)
        at com.vmware.vchs.hybridity.inventory.InventoryAdapter.collectCloudResources(InventoryAdapter.java:1522)
        at com.vmware.vchs.hybridity.networkstretch.SyncDestinationSiteInfoJob.fetchRemoteResources(SyncDestinationSiteInfoJob.java:215)
        at com.vmware.vchs.hybridity.networkstretch.SyncDestinationSiteInfoJob.syncDestinationEndpointNameAndResourceName(SyncDestinationSiteInfoJob.java:180)
        at com.vmware.vchs.hybridity.networkstretch.SyncDestinationSiteInfoJob.run(SyncDestinationSiteInfoJob.java:127)
        at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 

 

 

Environment

VMware HCX 4.x

Cause

The root cause is an inconsistent activation state within the HCX metadata, this leads to HCX Manager be placed into "Deactivated" and orphan state.

The status of HCX manager will lead to disconnection of site pairing.

 

Resolution

A specialized cleanup script package to be executed on both the HCX Connector (on-premises) and the HCX Cloud Manager. The execution of the script will purge the stale entries and reset the C&C state. Once Deactivate status is force-clear from HCX data based the site pairing will restore. 

Contact Broadcom Support to get assistance to purge the stale entry from the database.