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

Custom SNMP variable output

Votes:

0

Hey,

I run Linux VM with net-snmp on it

here is the output of custom variable that I have added

[root@linxuph53 ~]# snmpwalk -v 1 127.0.0.1 -c public .1.3.6.1.4.1.2021.8

UCD-SNMP-MIB::extIndex.1 = INTEGER: 1
UCD-SNMP-MIB::extNames.1 = STRING: sessionsweb
UCD-SNMP-MIB::extCommand.1 = STRING: /bin/sh
UCD-SNMP-MIB::extResult.1 = INTEGER: 0
UCD-SNMP-MIB::extOutput.1 = STRING: 70
UCD-SNMP-MIB::extErrFix.1 = INTEGER: noError(0)
UCD-SNMP-MIB::extErrFixCmd.1 = STRING:

this is the value that interest me:
UCD-SNMP-MIB::extOutput.1 = STRING: 70

however when I try to create a custom SNMP Sensor adding this line: 1.3.6.1.4.1.2021.8 in OID value in settings I'm getting this error

No Such Name (SNMP error # 2)

any ideas?

thanks, Dmitry

custom-snmp-sensor linux net-snmp

Created on Feb 9, 2012 2:02:31 AM

Last change on Feb 9, 2012 4:19:53 PM by Torsten Lindner [Paessler Support]



5 Replies

Votes:

0

Hello,

does the OID work in our SNMP Tester? If not, does it if you add a .1 to it?

best regards.

Created on Feb 9, 2012 4:32:00 PM by Torsten Lindner [Paessler Support]



Votes:

0

Yes, I tested it with SNMP Tester and got the same message - 

----------------------- New Test -----------------------
Paessler SNMP Tester 3.2
Device: 192.168.2.25

2/9/2012 4:32:05 PM (13 ms) : Start using SNMP V1
2/9/2012 4:32:05 PM (19 ms) : -------
2/9/2012 4:32:05 PM (22 ms) : Value: No Such Name (SNMP error # 2)
2/9/2012 4:32:05 PM (26 ms) : Done

I also added .1 to the end and it didn't help, however if I query from any Linux machine

snmpwalk -v 1 <IP> -c public .1.3.6.1.4.1.2021.8

does give me output

UCD-SNMP-MIB::extIndex.1 = INTEGER: 1
UCD-SNMP-MIB::extNames.1 = STRING: sessionsweb
UCD-SNMP-MIB::extCommand.1 = STRING: /bin/sh
UCD-SNMP-MIB::extResult.1 = INTEGER: 0
UCD-SNMP-MIB::extOutput.1 = STRING: 70
UCD-SNMP-MIB::extErrFix.1 = INTEGER: noError(0)
UCD-SNMP-MIB::extErrFixCmd.1 = STRING:

this is in my config list

# Make at least  snmpwalk -v 1 localhost -c public system fast again.
# name           incl/excl     subtree         mask(optional)
#view    systemview    included   .1.3.6.1.2.1.1
#view    systemview    included   .1.3.6.1.2.1.25.1.1
view     systemview    included   .1

maybe I need expose 1.3.6.1.4.1.2021.8 here in a VIEW here?

Created on Feb 10, 2012 12:35:04 AM

Last change on Feb 10, 2012 10:30:06 AM by Torsten Lindner [Paessler Support]



Votes:

0

.1.3.6.1.4.1.2021.8 is only the base OID (basically a table OID). You need the oids of the counters below:

 extTable	1.3.6.1.4.1.2021.8
 extEntry	1.3.6.1.4.1.2021.8.1
 extIndex	1.3.6.1.4.1.2021.8.1.1
 extResult	1.3.6.1.4.1.2021.8.1.100
 extOutput	1.3.6.1.4.1.2021.8.1.101
 extErrFix	1.3.6.1.4.1.2021.8.1.102
 extErrFixCmd	1.3.6.1.4.1.2021.8.1.103
 extNames	1.3.6.1.4.1.2021.8.1.2
 extCommand	1.3.6.1.4.1.2021.8.1.3

From http://www.oidview.com/mibs/2021/UCD-SNMP-MIB.html

Please try those individual OIDs

Created on Feb 10, 2012 10:31:16 AM by Torsten Lindner [Paessler Support]



Votes:

0

It does work on my Linux machine

[root@linxuph53]# snmpwalk -v 1 localhost -c public .1.3.6.1.4.1.2021.8.1.101 UCD-SNMP-MIB::extOutput.1 = STRING: 210

but it doesn't work on SNMPTester, I tried all the OIDs you mentioned - and got the same error, system doesn't see it.

What else can I do? From any Linux machine in network, I can query the SNMP tree 2021.8 without any issues but SNMPTester - says

/10/2012 12:17:05 PM (22 ms) : Value: 2 (No Such Name (SNMP error # 2))

Created on Feb 10, 2012 8:18:19 PM



Votes:

0

Maybe it's blocked then from PRTG/the Tester.

Created on Feb 13, 2012 2:30:38 PM by Torsten Lindner [Paessler Support]




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.