Smarts SAM/Hierarchical: Topology synchronization is not occuring between Presentation and Aggregation SAM levels.

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




Topology Synchronization between Aggregation SAM and Presentation SAM in hierarchical Smarts SAM topology does not occur as desired, and the following message seen in the logs for hierarchical Smarts SAM topology:

FAST-W-DXA_ETOPOCHANGED-ics-topology-sync.asl: [IP7] Topology has not changed

Environment

VMware Smart Assurance - SMARTS

Cause

In a hierarchical Smarts SAM setup, a topology change is only classed if objects and/or relationships are added or removed. In this condition, the Aggregation SAM attribute (lastProbeFinishedAt) used to indicate a topology change may not be updated. However, customized environments may have a requirement to carry out a synchronization of Attributes between SAM domains relating to Topology Objects so that a synchronization is triggered, even though no removal or addition of objects or relationships has occured.

Resolution

The Smarts SAM product is working as designed.  However, if required for your environment, you can carry out a manual update using the lastProbeFinishedAt command on the Aggregation SAM as follows:

1. Run the following command:
   
   <BASEDIR_SAM-AGG>/SAM/smarts/bin/dmctl -s <SAM-AGG>
    
2. Enter username/password at the prompt.
    
3. Run the lastProbeFinishedAt command at the dmctl> prompt as follows:
   
   dmctl> get ICF_TopologyManager::ICF-TopologyManager::lastProbeFinishedAt
   
   13-Apr-2010 13:59:19 IST
    
4. Run the following command at the dmctl> prompt:
   
   dmctl> invoke ICF_TopologyManager::ICF-TopologyManager syncCompleted
    
5. Run the following command at the dmctl> prompt:
   
   dmctl> get ICF_TopologyManager::ICF-TopologyManager::lastProbeFinishedAt 
   
   13-Apr-2010 14:01:38 IST