What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Simple custom OID returning #N SNMP_EXCEPTION_NOSUCHINSTANCE223

Votes:

0

Your Vote:

Up

Down

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.

custom-sensor error snmp

Created on Jun 8, 2021 12:35:36 AM by  ridgeside (0) 1

Last change on Jun 8, 2021 5:48:22 AM by  Florian Lesage [Paessler Support]



4 Replies

Accepted Answer

Votes:

1

Your Vote:

Up

Down

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.

Created on Jun 8, 2021 11:41:08 AM by  Florian Lesage [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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!

Created on Jun 8, 2021 12:32:11 PM by  ridgeside (0) 1



Votes:

1

Your Vote:

Up

Down

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.

Created on Jun 8, 2021 1:14:20 PM by  Florian Lesage [Paessler Support]



Votes:

0

Your Vote:

Up

Down

wow. TIL! Thanks.

Created on Jun 8, 2021 1:15:34 PM by  ridgeside (0) 1



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.