SNMPGET polls device with hardcoded OID and fails to monitor custom MIB

Document ID : KB000114430
Last Modified Date : 27/09/2018
Show Technical Document Details

SNMPGET probe cannot support devices with custom MIBs, or devices that do not follow the SNMP Standards. 
When a new device is registered to SNMPGet, the probe tries to connect to the device and poll standard SNMP oids, like the oid is the standard SNMP System Uptime (sysUpTime) oid.
If the custom MIB does not support the standard OIDs then the device is not registered to the SNMPGet, although connectivity is ok

we see the following in the snmpget probe log

snmpget: (SNMPQueryCreate) - peer:, ver.:2,community:public,options:timeout=1,retries=-1 
snmpget: (SNMPCreateSession) - peername:,args:timeout=1,retries=-1
snmpget: (DoQuery) - called with hostname:, oid:. 
snmpget: (DoQuery) - Name is: 
snmpget: SNMPAgentResponse:,tused=2ms - FAIL 
snmpget: GetSNMPfromProfile: ERROR tused=2ms 
snmpget: GetSNMPfromProfile: SNMPQueryCreate failed retry -1- 
snmpget: Profile: '' retry [1/2]


The probe is expecting that the MIB contains the mandatory system group fields as defined in rfc1213

With the current design of the probe we check for agent response based upon the sysUpTime oid.
If the oid is not available then the probe will generate an alarm.
There is an idea raised on the user community to request this be supported by the probe