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 18.104.22.168.22.214.171.124.0 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:10.34.36.110:1161, ver.:2,community:public,options:timeout=1,retries=-1 snmpget: (SNMPCreateSession) - peername:10.34.36.110:1161,args:timeout=1,retries=-1 snmpget: (DoQuery) - called with hostname:10.34.36.110:1161, oid:.126.96.36.199.188.8.131.52.0 snmpget: (DoQuery) - Name is: 184.108.40.206.220.127.116.11.0 snmpget: SNMPAgentResponse: 10.34.36.110:1161,tused=2ms - FAIL snmpget: GetSNMPfromProfile: ERROR tused=2ms snmpget: GetSNMPfromProfile: SNMPQueryCreate failed retry -1- snmpget: Profile: '10.34.36.110' 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 that this be supported by the probe.