Hello

I am trying out the free version of PRTG. One of the basic tests I am doing is to check if SNMP polling is working from the PRTG station. The OID I am polling is 1.3.6.1.2.1.1.5 for sysName.

I can get a result using snmpwalk from CLI

snmpwalk -c public -v 2c x.x.x.x 1.3.6.1.2.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (25303833) 2 days, 22:17:18.33

However, if I create a new probe with this OID (custom string), I get no responses. I know the IP address and community values are correct. I downloaded SNMPTester and it too fails to work. The failure code is "Value: No such instance (SNMP error # 223)". Any idea why I am not able to pull this OID from PRTG or from SNMPTester when snmp walk from CLI works fine?

Thanks,

Swami

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello,

can you read the SNMP Uptime with the SNMP Tester (not a specific OID)?

Best Regards.


Oct, 2010 - Permalink

Is there any access-list active on the switch / device? Are you polling from the same IP / management range ?


Oct, 2010 - Permalink

I also have this issue. I add new sensor : SNMP Disk Free After some time i see : No such instance (SNMP error # 223) Can you provide me the info about it? The snmpd.conf on my Linux server is configured and if i use zabbix it can view the disk usage but zabbix no!


Dec, 2011 - Permalink

If the sensor works but then later on ceases to work with the error "No such instance (SNMP error # 223)", that means that for reasons unknown to us the interface number did change. I'm afraid then there is very little we can do.


Dec, 2011 - Permalink

I'm afraid I'm seeing this same issue, except that it works via snmpwalk/get and PRTG 9, but not from SNMP Tester 3.2.

From SNMP Tester:

3/29/2012 8:02:26 AM TRANGO-APEX-RF-MIB|target|rf target rssi int 1.3.6.1.4.1.5454.1.60.3.8.2.0
3/29/2012 8:02:26 AM TRANGO-APEX-RF-MIB|rssi|rf rssi int 1.3.6.1.4.1.5454.1.60.3.9.2.0
3/29/2012 8:02:26 AM TRANGO-APEX-RF-MIB|rf pll|rf rfm rfpll 1.3.6.1.4.1.5454.1.60.3.10.1.0
3/29/2012 8:02:26 AM Found: 1

From linux in the same subnet:

# snmpwalk -v2c -c public 10.14.0.161 1.3.6.1.4.1.5454.1.60.3.9.2.0
SNMPv2-SMI::enterprises.5454.1.60.3.9.2.0 = INTEGER: -70
# snmpget -v2c -c public 10.14.0.161 1.3.6.1.4.1.5454.1.60.3.9.2.0 
SNMPv2-SMI::enterprises.5454.1.60.3.9.2.0 = INTEGER: -70
# snmpwalk -v2c -c public 10.14.0.161 1.3.6.1.4.1.5454.1.60.3.9    
SNMPv2-SMI::enterprises.5454.1.60.3.9.1.0 = Opaque: Float: -70.50
SNMPv2-SMI::enterprises.5454.1.60.3.9.2.0 = INTEGER: -70

And PRTG 9 is able to poll the OID from the MIB or if I manually enter the OID.

As you can see from above, other OIDs from the MIB work fine in SNMP Tester 3.2.

I don't believe there are any ACLs between devices on the same subnet - and even if there were, is it possible for it to restrict what OIDs could be polled?


Mar, 2012 - Permalink

The SNMP Tester and PRTG use the same functions and libraries. Just to check, is this a library scan? And in PRTG both the library scan and the individual OIDs work (with SNMP Custom Sensors)?


Mar, 2012 - Permalink