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

Can't get SNMP traffic sensor to work

Votes:

0

I'm trying to add an SNMP traffic sensor to one of our Linux web servers, but Step 2 of the add process shows "No Interface Number available". I tried checking the server with SNMP Tester, and running that with "Scan Interfaces" shows:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
1/8/2015 4:00:13 PM (2 ms) : Device: ******
1/8/2015 4:00:13 PM (3 ms) : SNMP V1
1/8/2015 4:00:13 PM (4 ms) : Scaninterfaces
Scanning Standard Interfaces...
1/8/2015 4:00:13 PM Start Scan
1/8/2015 4:00:13 PM Host: ******
1/8/2015 4:00:13 PM Community: ******
1/8/2015 4:00:13 PM SNMP Version: V1
1/8/2015 4:00:13 PM Delay: 0
1/8/2015 4:00:13 PM Force32: No
1/8/2015 4:00:13 PM Single Get: No
1/8/2015 4:00:13 PM GET: 1.3.6.1.2.1.2.1.0
1/8/2015 4:00:13 PM Try 1
1/8/2015 4:00:13 PM DoRequest 0
1/8/2015 4:00:13 PM Init Session
1/8/2015 4:00:13 PM Host: ******:161
1/8/2015 4:00:13 PM Timeout: 2000000
1/8/2015 4:00:13 PM Version: 1
1/8/2015 4:00:13 PM Open Session
1/8/2015 4:00:13 PM Send Request
1/8/2015 4:00:13 PM Send Done
1/8/2015 4:00:13 PM Start 47226400
1/8/2015 4:00:13 PM Done 47226400 Status=0
1/8/2015 4:00:13 PM GET NEXT: 1.3.6.1.2.1.2.2.1.2
1/8/2015 4:00:13 PM DoRequest 0
1/8/2015 4:00:13 PM Init Session
1/8/2015 4:00:13 PM Host: ******:161
1/8/2015 4:00:13 PM Timeout: 2000000
1/8/2015 4:00:13 PM Version: 1
1/8/2015 4:00:13 PM Open Session
1/8/2015 4:00:13 PM Send Request
1/8/2015 4:00:13 PM Send Done
1/8/2015 4:00:13 PM Start 47226232
1/8/2015 4:00:13 PM Done 47226232 Status=0
1/8/2015 4:00:13 PM 0 ASN_INTEGER,ASN_GAUGE: 1
1/8/2015 4:00:13 PM Current: 1.3.6.1.4.1.2021.2.1.1.1
1/8/2015 4:00:13 PM GET NEXT: 1.3.6.1.4.1.2021.2.1.1.1
1/8/2015 4:00:13 PM DoRequest 0
1/8/2015 4:00:13 PM Init Session
1/8/2015 4:00:13 PM Host: ******:161
1/8/2015 4:00:13 PM Timeout: 2000000
1/8/2015 4:00:13 PM Version: 1
1/8/2015 4:00:13 PM Open Session
1/8/2015 4:00:13 PM Send Request
1/8/2015 4:00:13 PM Send Done
1/8/2015 4:00:13 PM Start 47226304
1/8/2015 4:00:13 PM Done 47226304 Status=0
1/8/2015 4:00:13 PM 0 ASN_INTEGER,ASN_GAUGE: 2
1/8/2015 4:00:13 PM GetNext=1.3.6.1.4.1.2021.2.1.1.2
Result: 

Found standard interfaces:
: ,Undefined,,(not defined),, 64 Bit

Testing standard interfaces...
Test  (1.3.6.1.2.1.31.1.1.1.6.,1.3.6.1.2.1.31.1.1.1.10.): in=Error converting OID (SNMP error # -2007)  out=Error converting OID (SNMP error # -2007)

---------------------------------------------------------

SNMP is running on the server, Port 161 is open through the firewall, and the same server has already existing SNMP sensors for Disk Free, Load Average, and Meminfo, which all work fine.

We're running PRTG 14.3.11.2750+.

Thanks for any help you can offer!

Dave

prtg14 snmp snmp-traffic

Created on Jan 8, 2015 9:06:42 PM

Last change on Jan 9, 2015 1:10:00 PM by  Konstantin Wolff [Paessler Support]



4 Replies

Votes:

0

Hi Dave,
what distribution is the server running on?
How do the lines in your snmpd.conf look which are starting with view.
Additionally, please use the SNMP Tester and do a walk over the OIDs 1.3.6.1.2.1.2.1 and 1.3.6.1.2.1.31.1. What are the results?
Best regards

Created on Jan 9, 2015 1:13:27 PM by  Konstantin Wolff [Paessler Support]



Votes:

0

Thanks. This is Red Hat Enterprise Linux 5.11.

Originally there were no view lines active in snmpd.conf. I uncommented the following lines and restarted snmpd:

com2sec notConfigUser  default       public
group   notConfigGroup v2c           notConfigUser
view    systemview    included   .1.3.6.1.2.1.1
access  notConfigGroup ""      any       noauth    exact  systemview none none

but there was no effect -- SNMP Tester shows the same error.

When I do an SNMP walk with SNMP Tester, I get:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1.3
1/9/2015 9:59:11 AM (2 ms) : Device: ********
1/9/2015 9:59:11 AM (3 ms) : SNMP V2c
1/9/2015 9:59:11 AM (4 ms) : Walk .1.3.6.1.2.1.2.1

and it stops there. It does the same thing for 1.3.6.1.2.1.2.1, .1.3.6.1.2.1.2.1, 1.3.6.1.2.1.31.1, and .1.3.6.1.2.1.31.1.

Dave

Created on Jan 9, 2015 3:01:00 PM

Last change on Jan 12, 2015 8:52:38 AM by  Konstantin Wolff [Paessler Support]



Votes:

0

Dave,
please try replacing the line starting with view, with the following

view    systemview    included  .1.3.6.1

and restart your snmp services. Additionally, please check (if used) your iptables configuration.
Does that help?

Created on Jan 12, 2015 8:55:49 AM by  Konstantin Wolff [Paessler Support]

Last change on Jul 2, 2019 7:19:15 AM by  Sebastian Kniege [Paessler Support]



Votes:

0

I found the problem. It wasn't in the view line of snmpd.conf, but changing that helped me find where the problem was. When I made that change, snmpwalk worked, but it only found OIDs in the .1.3.6.1.4 tree. So I went back to the snmpd.conf file and found that the rocommunity line had been set to:

rocommunity <community string> <IP address>/16 .1.3.6.1.4

I removed the ".4" from the end, and everything now works.

Thanks for the help.

Created on Jan 12, 2015 4:36:24 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.