Smarts IP: Cannot discover additional devices using Add Agent function

Products

• VMware

Issue/Introduction

Symptoms:




Smarts IP cannot discover additional devices using Add Agent function
When selecting Add Agent through the Smarts IP user interface, nothing happens

Smarts IP log file contains the following message:

[07-Oct-2009 13:07:58+400ms IST] t@84 SM_ProtocolEngine-1
ADTM-E-AD_MANAGER_NOTSTARTED-The topology manager is not started. Check if the
InCharge discovery feature is licensed

[07-Oct-2009 13:07:58+400ms IST] t@84 SM_ProtocolEngine-1
ADTM-E-AD_DEBUG_MSG-'xmlCreate' : 'Exception when call create' ; in file
"/work/greencurrent/IP-7.0.3.X/111/smarts/auto-discovery/manager/TopologyM
anager_Impl.c" at line 4627
ADTM-AD_MANAGER_NOTSTARTED-The topology manager is not started. Check if the
InCharge discovery feature is licensed

Environment

VMware Smart Assurance - SMARTS

Cause

This problem occurs because of dual instances were created for the AD_TopologyManager class. The AD_TopologyManager should be singleton and cannot have two instances.
In one environment where this problem was encountered, the following instances were found after the dynamic model was used:

• ICF-TopologyManager
• MR_Object::Router::REPHHC01-re0

Resolution

To resolve this issue, delete the duplicate instance (MR_Object::Router::REPHHC01-re0 in the above Cause statement) of the AD_TopologyManager class. This is done as follows:

1. Start the sm_server and load the appropriate rps file.
2. From the sm_gui, press Ctrl+Alt+m to refresh the tree.
3. Expand the tree to find ICF_TopologyManager class. Expand further to find two instances as follows:
    
4. • ICF-TopologyManager
   • MR_ObjecICF-TopologyManagert::Router::REPHHC01-re0
     
      
5. Remove the duplicate instance (MR_Object::Router::REPHHC01-re0) from the tree.
6. Discover the devices in Smarts IP.