Topology is not being synchronized between different SAM layers

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

Devices synchronized from the underlying domains or created synthetically are not being synchronized on the Top Layer SAM domains

SAM Domain Logs present this kind of information:

[<date and time>] t@1969137216 Underlying-Domain_Topo-Driver
DXA_MESSAGE-E-DXA_ETOPOMGRSUSPENDED-ics-topology-sync.asl: ICF_TopologyManager has suspendTopologyManager set to TRUE.

[<date and time>] t@1969137216 Underlying-Domain_Topo-Driver
DXA_MESSAGE-C-DXA_EDRIVERSTOPPED-ics-topology-sync.asl: [Underlying-Domain] Driver stopped due to errors posted

Environment

Smarts 10.1.X, 24.3.X

Cause

Check for the following flag, which when set to TRUE, the topo-drivers fail to pull the topology from the underlying domain managers.

dmctl -s <SAM> get ICF_TopologyManager::ICF-TopologyManager::suspendTopologyManager

Resolution

If syspendTopologyManager = TRUE, then this must be set to false in-order to achieve the topo-sync functionality:

• Check the <Base-Dir>SAM/smarts/conf/ics/bootend.conf (local copy if this has been modified in the past) and validate the parameter suspendTopologyManager

ICF_TopologyManager::ICF-TopologyManager {
# suspendTopologyManager
# Suspends all topology manager operations
# Set this to TRUE if you are using the SAM Server in a failover configuration
# Default value is FALSE
    suspendTopologyManager = FALSE
}

This edit will ensure that the settings are picked on an event of restart of SAM. 

Additionally, to apply the settings on runtime (without SAM restart), commands to achieve this are:

• First set -  suspendTopologyManager = FALSE

dmctl -s <SAM> put ICF_TopologyManager::ICF-TopologyManager::suspendTopologyManager FALSE

• Once set to FALSE, please initiate topo-sync again by running:

dmctl -s <SAM> invoke GA_DaemonDriver::<Underlying Domain Name>_Topo-Driver start