Devices get added to the pending list, even though they are correctly discovered and no "DiscoveryError" is shown

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

Devices get added to the pending list in Smarts IP, even though they are correctly discovered and no DiscoveryError is shown

The following error message is found in the Smarts IP debug logs:

ASNM-E-ASNMP_SEND_RECEIVE_ERROR-ASNMP request failure: Error when sending or receiving SNMP data for Host '#.#.#.#' (Maybe bad credentials).
 SNMP-ERESPONSE-No response from #.#.#.#, port 161
 SNMP-ETIMEOUT-Timed out

AD_MSG-*-AD_LOG-at 'discovery/ic-mib2-hyper-data.asl: <thread number>', while discovering '<HOSTNAME>', ASNM-E-ASNMP_SEND_RECEIVE_ERROR-ASNMP request failure: Error when sending or receiving SNMP data for Host '#.#.#.#' (Maybe bad credentials).

Environment

All supported Smarts versions

Cause

The device is in pending list because of ASNM-E-ASNMP_SEND_RECEIVE_ERROR-Error. By default IP domain have ASNMP feature enabled. This feature is used to discover devices as fast as possible. However, some devices may not respond quickly enough, resulting in the errors above and the device getting added to the pending list.

Resolution

1. Open the tpmgr-param.conf configuration file using sm_edit.
2. Add the following line:
   
   

   DoNotUseASNMPPattern <device OID>

   
   
   
3. Save and close the tpmgr-param.conf configuration file.
4. Reload the file to APM/IP domain using the following command:
   
   

   sm_tpmgr -s <IP domain name> --load-conf=<BASEDIR>/smarts/local/conf/tpmgr-param.conf

   
   
   
5. Rediscover the device, now device will be removed from pending list. 

 

Additional Information

Adding the DoNotUseASNMPPattern as described in the preceding steps will only disable the ASNMP feature for devices with the sysOID specified in the tpmgr-param.conf file. If other SysOID has same issue, add entry for each SysOID.