Smarts IP: During IP discovery with Smarts NPM shows SWFE-E-EGETNEXT-While getting next of OID .1.3.6.1.2.1.138.1.6.3.1.3

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


The full message seen is:

Nexus-5596UP;SWFE-E-EGETNEXT-While getting next of OID .1.3.6.1.2.1.138.1.6.3.1.3, SNMP-ERESPONSE-No response from 10.207.0.11, port 161 SNMP-ETIMEOUT-Timed out; in file "/work/redcurrent/DMT-9.4.2.0/10/smarts/snmp/lib/SNMP_RequestsSender.c" at line 1337

Please see in the screen shot below:

 

 

Environment

VMware Smart Assurance - SMARTS

Cause

During discovery in Smarts NPM , the domain does probing of OIDs to all the devices in the topology to check to see they are qualified to be imported into the NPM domain .

Resolution

Please see the two provided work arounds below:

• set the value of  DisableProtocolDiscovery  to TRUE if you are not using NPM domain to pull device from the IP topology. That way the OID will not be polled.
  • This can be done in BASEDIR/IP/smarts/bin/sm_edit conf/discovery/tpmgr-param.conf
• Modify the ic-protocol-discovery.asl to exclude these devices being probed and that will avoid the reported asl error. This is considered custom work and not supported, so it is recommended to perform these changes in a test environment. as it might impact discovery of other devices. 

Per the SNMP protocol implementation, if the specific OID is not available with the device agent, then it should return  NoSuchInstance  which is considered to be a valid response but not timing out. Timing out on an OID is considered to be a discovery error and SMARTS will flag those.