Smarts IP/NPM: Devices were removed from the Smarts IP domain, but alerts from those devices remain in the user consoles in Smarts NPM
search cancel

Smarts IP/NPM: Devices were removed from the Smarts IP domain, but alerts from those devices remain in the user consoles in Smarts NPM

book

Article ID: 304223

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:




Devices were removed from the Smarts IP domain, but alerts from those devices remain in the user consoles in Smarts NPM

Automatic synchronization between Smarts NPM and Smarts IP domains is disabled using the following setting in the Smarts IP domain tpmgr_param.conf configuration file:

enableSynchronization  FALSE



Synchronization between the Smarts IP and Smarts NPM domains is managed using a cron job as follows:
0 20 * * * /opt/InCharge7/NPM/smarts/bin/dmctl -s <NPM DOMAIN NAME> invoke  ICF_TopologyManager::ICF-TopologyManager addManagedElement <AM DOMAIN NAME> AM


Environment

VMware Smart Assurance - SMARTS

Resolution

To resolve this issue, you can use the discoverAll command instead of addManagedElement in the cron job used for domain syncrhonization as in the following example (see Note statement):

dmctl -s <NPM DOMAIN NAME> invoke ICF_TopologyManager::ICF-TopologyManager  discoverAll



Additional Information

Using the discoverAll command will cause Smarts to attempt Open Shortest Path First (OSPF) probing for all existing devices. This will take much longer than just running addManagerElement on Smarts AM domains.