I have a simple custom SNMP OID sensor setup that returns the error

  1. N SNMP_EXCEPTION_NOSUCHINSTANCE223

When I do an snmp walk for that OID it returns the proper value ( 1)

~ user1$ snmpwalk -v2c -c mypassword 192.168.2.3 1.3.6.1.4.1.25461.2.1.2.5.1.3
SNMPv2-SMI::enterprises.25461.2.1.2.5.1.3.0 = INTEGER: 1

The Sensor is added to an existing device that has many other sensors which work fine so the community and permissions are correct.

Article Comments

Hello,

Thank you for your message.

To monitor this value you must provide the entire OID in the settings of the SNMP Custom sensor otherwise it won't be able to get it.

Therefore, I invite you to configure the OID "1.3.6.1.4.1.25461.2.1.2.5.1.3.0" in the sensor settings and then check if the sensor gets data.

If you have questions, let us know.

Regards.


Jun, 2021 - Permalink

This worked. Does that mean every custom OID on PRTG needs that trailing .0? You can see from my SNMP walk I did not include the trailing .0 and it returned the right value.

Anyway thanks for the help!


Jun, 2021 - Permalink

Thank you for your feedback.

If you use an invalid/not complete OID, the GET request executed by the SNMP Custom sensor will automatically fails as it requires a valid identification number that returns a value. Whereas a WALK use GETNEXT requests which gets all available OIDs/values from the one you provide, hence the result you got.

Here is an article on this matter: https://www.ionos.com/digitalguide/server/know-how/snmp-tutorial/

Regards.


Jun, 2021 - Permalink

wow. TIL! Thanks.


Jun, 2021 - Permalink