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

Sonicwall VPN Traffic Sensor Not Working Correctly

Votes:

0

I am using the Sonicwall VPN Traffic Sensor against a Sonicwall NSA 2400, but most of the VPN tunnels do not show any traffic. I am using PRTG ver 13.4.6.3374.

Here is a set of OID's I pulled from the Sonicwall for one of the tunnels I'm trying to monitor (I edited the IP's):

11/12/2013 12:54:34 PM (1237 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.1.3414248772 = "94612"
11/12/2013 12:54:37 PM (3642 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.2.3414248772 = "10.10.10.10"
11/12/2013 12:54:39 PM (6148 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.3.3414248772 = "192.168.2.0"
11/12/2013 12:54:42 PM (8644 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.4.3414248772 = "192.168.2.255"
11/12/2013 12:54:44 PM (11102 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.5.3414248772 = "192.168.1.0"
11/12/2013 12:54:47 PM (13670 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.6.3414248772 = "192.168.1.255"
11/12/2013 12:54:49 PM (16266 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.7.3414248772 = "11/12/2013 12:24:37"
11/12/2013 12:54:52 PM (18868 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.8.3414248772 = "18354"
11/12/2013 12:54:55 PM (21426 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.9.3414248772 = "16115646"
11/12/2013 12:54:57 PM (24129 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.10.3414248772 = "13991"
11/12/2013 12:55:00 PM (26620 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.11.3414248772 = "1428264"
11/12/2013 12:55:02 PM (29101 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.12.3414248772 = "0"
11/12/2013 12:55:05 PM (31665 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.13.3414248772 = "0"
11/12/2013 12:55:08 PM (34361 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.14.3414248772 = "Office"

Though, the Sensor shows no traffic going through it.

prtg sonicwall vpn

Created on Nov 12, 2013 6:29:04 PM

Last change on Nov 13, 2013 11:58:16 AM by Greg Campion [Paessler Support]



5 Replies

Votes:

0

What this could be is that the counters in the Sonicwall are not going up anymore possibly due to an issue with the Sonicwall. I checked the output that you posted against a simulator and raised the values and it worked in my PRTG installation to show the difference that I had put into the values.

Can you run a few of these scans and see if the values for the counters are going up? If they are, then this may be a different issue but the output here looks fine. If the values are not going up for these counters, then you may have to reboot the Sonicwall and if that does not work, try contacting Sonicwall to see why these counters are not working properly.

Created on Nov 13, 2013 12:07:14 PM by Greg Campion [Paessler Support]



Votes:

0

Which counters in the Sonicwall? If you are referring to being able to see the traffic, i.e. packets in/out etc, within the Sonicwall GUI go up for each tunnel, then yes, I see that occurring on the Sonicwall, but not within PRTG.

Created on Nov 13, 2013 6:14:03 PM



Votes:

0

I was speaking more specifically about the SNMP walk that you did when you first opened this question. If you do multiple walks on the same OID, do you see the values in SNMP going up?

Created on Nov 14, 2013 9:53:37 AM by Greg Campion [Paessler Support]



Votes:

0

I ran a walk on it every 15 seconds, and though there was not a lot of traffic, just the pings I ran on it, it did increment, yet not in PRTG. Here is my results.

11/14/2013 1:51:33 PM (1249 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.8.3022802244 = "438" 11/14/2013 1:51:51 PM (1530 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.8.3022802244 = "478" 11/14/2013 1:52:06 PM (1997 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.8.3022802244 = "494" 11/14/2013 1:52:22 PM (2309 ms) : 1.3.6.1.4.1.8741.1.3.2.1.1.1.8.3022802244 = "534"

Created on Nov 14, 2013 7:04:47 PM



Votes:

0

This may be related to another bug that we found with this sensor this week. We think we have resolved it and it's going through testing currently and will hopefully be out in the next stable release. If the next release does not solve the issue, please let me know and we can do some further testing.

Created on Nov 14, 2013 9:49:57 PM by Greg Campion [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.