What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Issue with multiple channels in SNMP Custom Advanced sensor

Votes:

0

I want to use this sensor to monitor multiple values from a table (but not all of them). When i configure the sensor with just one channel it works fine, but when i configure one with more than one channel i get the error " '' is not a valid integer value". I use the same configuration and value type and lookup for all the channels. What could be the cause of this error?

best regards,

Daniela

snmp-custom-sensor snmp-sensor snmpadvancedsensor

Created on Oct 29, 2015 4:19:09 PM



Best Answer

Accepted Answer

Votes:

0

Hello Daniela,
thank you very much for the additional walk and screenshots.

The walk confirms that the values are numerical.
Based on your screenshot, the issue is the way(format) in which you're entering the SNMP OID's.

PRTG requires you to enter complete OID's without the leading . (dot) which is very common in other applications.

When setting up any SNMP sensors within PRTG which query oid's, you should always enter them in the following pattern:

1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.4

And this should be avoided:

.1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.4

Best Regards,

Created on Oct 29, 2015 9:05:25 PM by Luciano Lingnau [Paessler]



6 Replies

Votes:

0

Hello Daniela,
thank you for your contact.

  • Which version of PRTG are you using?
  • Are the monitored OID's numerical or are they Strings?

Please use our SNMP Tester and perform a Walk of the SNMP table who contains the values you wish to query. The tool will also identify the datatype of the queried OID's. Which results do you get from the walk?

When pasting the Walk result kindly use the Bad Image src (triple curly brackets) to pre-format the code correctly.

Created on Oct 29, 2015 5:42:24 PM by Luciano Lingnau [Paessler]

Last change on Oct 29, 2015 5:42:57 PM by Luciano Lingnau [Paessler]



Votes:

0

Thanks so much for your soon response.

The version is PRTG Network Monitor 15.4.20.4491

The OIDs are numerical, 1 or 2.

Here is the result:

Paessler SNMP Tester 5.1.3
10/29/2015 12:53:25 PM (2 ms) : Device: 172.21.0.4
10/29/2015 12:53:25 PM (3 ms) : SNMP V2c
10/29/2015 12:53:25 PM (4 ms) : Walk 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110
10/29/2015 12:53:25 PM (27 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.1 = "2"
10/29/2015 12:53:25 PM (50 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.2 = "2"
10/29/2015 12:53:25 PM (76 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.3 = "2"
10/29/2015 12:53:25 PM (102 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.4 = "2"
10/29/2015 12:53:25 PM (127 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.5 = "2"
10/29/2015 12:53:25 PM (152 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.6 = "2"
10/29/2015 12:53:25 PM (176 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.1 = "2"
10/29/2015 12:53:25 PM (200 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.2 = "2"
10/29/2015 12:53:25 PM (225 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.3 = "2"
10/29/2015 12:53:25 PM (251 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.4 = "2"
10/29/2015 12:53:25 PM (277 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.5 = "2"
10/29/2015 12:53:25 PM (304 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.6 = "2"
10/29/2015 12:53:25 PM (329 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.1 = "2"
10/29/2015 12:53:25 PM (353 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.2 = "2"
10/29/2015 12:53:25 PM (381 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.3 = "2"
10/29/2015 12:53:25 PM (407 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.4 = "2"
10/29/2015 12:53:25 PM (434 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.5 = "2"
10/29/2015 12:53:25 PM (460 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.6 = "2"
10/29/2015 12:53:25 PM (485 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.1 = "2"
10/29/2015 12:53:25 PM (511 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.2 = "2"
10/29/2015 12:53:25 PM (539 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.3 = "2"
10/29/2015 12:53:25 PM (566 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.5 = "2"
10/29/2015 12:53:25 PM (591 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.6.1 = "2"
10/29/2015 12:53:25 PM (618 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.6.2 = "2"
10/29/2015 12:53:25 PM (645 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.6.3 = "2"
10/29/2015 12:53:25 PM (672 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.6.4 = "1"
10/29/2015 12:53:25 PM (699 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.6.5 = "1"

I also tested with another mib browser from iReasoning and the value is integer (1 or 2)

regards,

Daniela

Created on Oct 29, 2015 7:01:27 PM



Votes:

0

Hello Daniela,

I'm afraid that's not our latest version of the SNMP Tester. You need to download (and perform the walk) using the version released after (August 13th 2015):

  • SNMP Tester can now show the data type of an SNMP value

Are you able to upload an screenshot from the sensor's settings somewhere and link it here?

Best Regards,

Created on Oct 29, 2015 7:23:59 PM by Luciano Lingnau [Paessler]



Votes:

0

Hello Luciano,

here are the screenshot and the walk with the new version.

http://i.imgur.com/ITWUR4z.png

Paessler SNMP Tester 5.2.1
10/29/2015 2:45:55 PM (2 ms) : Device: 172.21.0.2
10/29/2015 2:45:55 PM (3 ms) : SNMP V2c
10/29/2015 2:45:55 PM (5 ms) : Walk 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110
10/29/2015 2:45:55 PM (36 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.1 = "1" [ASN_INTEGER]
10/29/2015 2:45:55 PM (63 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.2 = "1" [ASN_INTEGER]
10/29/2015 2:45:55 PM (90 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.3 = "2" [ASN_INTEGER]
10/29/2015 2:45:55 PM (117 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.4 = "2" [ASN_INTEGER]
10/29/2015 2:45:55 PM (146 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.5 = "2" [ASN_INTEGER]
10/29/2015 2:45:55 PM (175 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.6 = "2" [ASN_INTEGER]
10/29/2015 2:45:55 PM (202 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.1 = "2" [ASN_INTEGER]
10/29/2015 2:45:55 PM (230 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.2 = "2" [ASN_INTEGER]
10/29/2015 2:45:55 PM (259 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.3 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (288 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.4 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (318 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.5 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (347 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.2.6 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (377 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.1 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (406 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.2 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (438 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.3 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (478 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.4 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (510 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.5 = "1" [ASN_INTEGER]
10/29/2015 2:45:56 PM (547 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.3.6 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (579 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.1 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (612 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.2 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (646 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.4 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (677 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.5 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (721 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.4.6 = "2" [ASN_INTEGER]
10/29/2015 2:45:56 PM (755 ms) : 1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.6.3 = "1" [ASN_INTEGER]

best regards,

Da

Created on Oct 29, 2015 8:52:04 PM



Accepted Answer

Votes:

0

Hello Daniela,
thank you very much for the additional walk and screenshots.

The walk confirms that the values are numerical.
Based on your screenshot, the issue is the way(format) in which you're entering the SNMP OID's.

PRTG requires you to enter complete OID's without the leading . (dot) which is very common in other applications.

When setting up any SNMP sensors within PRTG which query oid's, you should always enter them in the following pattern:

1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.4

And this should be avoided:

.1.3.6.1.4.1.7465.20.2.9.6.3.1.2.1.110.1.4

Best Regards,

Created on Oct 29, 2015 9:05:25 PM by Luciano Lingnau [Paessler]



Votes:

0

Indeed that was the problem! Thank you very much Luciano!

Created on Oct 29, 2015 9:28:53 PM




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.