Discovery Errors with while getting next OID

Products

• VMware Smart Assurance

Issue/Introduction

Several discovery error is observed for devices post discovery.

Error in domain log:

<DEVICE_NAME>, <DEVICE_IP>, Model=ciscoFpr4115SM24, SysOID=.1.3.6.1.4.1.9.1.2774, Error=SWFE-E-EGETNEXT-While getting next of OID .1.3.6.1.4.1.9.9.439.1.1.1,
 SNMP-ERESPONSE-No response from <DEVICE_IP>, port 161
 SNMP-ETIMEOUT-Timed out; in file "/work/redcurrent/DMT-10.1.12.0/16/smarts/snmp/lib/SNMP_RequestsSender.c" at line 1337

Environment

Smarts - 10.1.x/24.3.x

Cause

VoIP OID was not disabled in user environment, with default installation, it is disabled. 

Resolution

1. Navigate to <IP_BASE>/smarts/bin, run 

   ./sm_edit conf/discovery/tpmgr-param.conf

   1. This will create local copy of tpmgr-param.conf.
2. Open file and look for DisableVOIPDiscovery, by default it will be TRUE.
3. In case it is FALSE, change it to TRUE. 
   1. If value is FALSE, then all OIDs in voip-topo-oid.conf will be polled which is causing discovery error. 
4. Save the file. 
5. Load changes as 

   ./sm_tpmgr -s <IP Manager> --load-conf=tpmgr-param.conf.

6. Perform rediscovery of device, discovery error VoIP CCME MIB should not been seen. 

Additional Information

To enable device SNMP debug - Enable/disable SNMP tracing/debug on a single device in Smarts IP