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 220.127.116.11.18.104.22.168.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:.22.214.171.124.126.96.36.199.0
snmpget: (DoQuery) - Name is: 188.8.131.52.184.108.40.206.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]