I have set up a custom SNMP sensor using a valid OID confirmed using MIB Browser. However, PRTG Network Monitor v13.1.2.1462 is unable to get this reading from the network device. All I get is "No Such Name (SNMP error # 2).
Infact, all but a a couple of custom sensors to this remove device are reporting the aforementioned error, despite confirmed existence of their respective OIDs.
I have tried changing the SNMP Version of the device, underneath "Inherit Credentials for SNMP Devices", from v2c to v1. I also tried using 32-bit counters only, under SNMP Compatibility Options. With both these changes in place, I still get error # 2.
With MIB Browser, I do get a valid response from these OIDs as follows;
Name/OID: cpqSeCpuStatus.0; Value (Integer): ok (2) Name/OID: cpqDaCntlrCondition.2; Value (Integer): ok (2) Name/OID: cpqDaLogDrvStatus.2.1; Value (Integer): ok (2)
Ideas?
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.
Greg, thanks for the response. I was not supplying the full path when configuring sensors to read data from SNMP tables. So instead of creating a custom sensor with OID .1.3.6.1.4.1.232.6.2.9.3.1.5.0.2, I needed to use .1.3.6.1.4.1.232.6.2.9.3.1.5.0.2.0.x where x is the number of entries in the SNMP table.
May, 2013 - Permalink
Have you tried testing the OID to see what value is returned with the SNMP tester? Please try running this and sending the results as well as a screenshot of the configuration to support@paessler.com and reference this article in the ticket. Since this is a specific issue, it will be better solved through our ticketing system.
Thanks!
May, 2013 - Permalink