Smarts IP: Devices will not add to EIGRP topology
search cancel

Smarts IP: Devices will not add to EIGRP topology


Article ID: 327760


Updated On:





Devices will not add to EIGRP topology in Smarts IP Manager


VMware Smart Assurance - SMARTS


There are four possible causes for a device not adding to the EIGRP_TopologyCollection in Smarts IP Manager:

  • EIGRP protocol discovery is not enabled.
  • The Device does not meet the MIB OID requirement to be discovered as EIGRP.
  • The discovery of the EIGRP criteria is timing out.


The following sections of this Fix statement present the fixes for each of the above causes.

EIGRP protocol discovery has not been enabled on the domain:
To determine if this is the cause of the EIGRP topology issue, run the following command:

./dmctl -s <AM PM Domain> invoke ICF_TopologyManager::ICF-TopologyManager findParameter DisableProtocolDiscovery. 

If this command returns FALSE then your problem is one of the other three reasons outlined in the following sections. If this command returns a value of TRUE, then you need to modify the tpmgr-param.conf file to enable EIGRP protocol discovery as follows:

  1. Locate the <BASEDIR>/IP/smarts/conf/tpmgr-param.conf OR <BASEDIR>/IP/smarts/local/conf/tpmgr-param.conf file (see Note statement).
  2. Open the tpmgr-param.conf file for editing using sm_edit.
  3. Locate the line that reads DisableProtocolDiscovery TRUE.
  4. Modify this line to read DisableProtocolDiscovery FALSE.
  5. Save and close the tpmgr-param.conf file.
  6. Reboot the Smarts IP domain and rediscovery the EIGRP device.
    1. NOTE: Use this command to reload the file, rather than reboot the domain.
      1. ./sm_tpmgr -s M<IP Domain>  --load-conf=tpmgr-param.conf

MIB OID requirement to discover object as EIGRP:
There is an instance of the OID .*.*, where the last two OID indices can be any valid index values that contain the text "EIGRP". This text is not case sensitive.

Discovery of EIGRP is timing out:
If you have completed all the steps above and confirmed that the device meets the requirement for discovering as EIGRP, then the device might be timing out ion its discovery.  You will need to increase your default timeouts for discovery and autodiscovery. This should be done as follows:

  1. Locate the discovery.conf configuration file. This file will be in either of the following locations:


    <BASE DIR>/IP/smarts/local/conf/discovery
  2. Open the discovery.conf file for editing using sm_edit.
  3. In the discovery.conf file, locate the settings for defaultTimeout and defaultSNMPAutoTimeout.
  4. Double the values of these settings. The default value for these settings is 1000, so set them to 2000 if you are using the default settings.
  5. Save and close the discovery.conf file.
  6. Reboot your Smarts IP domain.
  7. Rediscover the device that would not add to the EIGRP Topology Collection.
  8. Confirm the device has added to the EIGRP Topology Collection. If it is still not added, double the defaultTimeout and defaultSNMPAutoTimeout settings as described in the preceding step.
  9. If there are still issues douibling the defaultTimeout and defaultSNMPAutoTimeout settings twice, it may be wise to start up a test domain and discover the problematic device there. This way, you will be rebooting your test domain while finding the best timeout values for discovering the EIGRP protocol, instead of continually rebooting your production domain.

Additional Information

The <BASEDIR>/IP/smarts/local/ directory is ALWAYS given precedence by Smarts over any other directory. 

When modifying any file, it is best practice to save the modified file in this directory. 

For example, when editing the <BASEDIR>/IP/smarts/conf/discovery/discovery.conf file, you should save the changed file to the <BASE DIR>/IP/smarts/local/conf/discovery directory.
If this folder does not exist, you should create it.