PRTG and Juniper

Please, help. If we can figure this out, we will purchase a full version of PRTG. Without it, we will need to look for other solutions. VPN monitoring is one of the top priorities for us. PRTG works great for policy based VPNs on Cisco ASAs, but for route-based VPNs on Juniper, it is not quiet the same. I wish there would be a dedicated sensors for SSGs, just like ASAs. Those work great. Sensors based on MIBs need to be better configurable.

Hello,

I'm very much afraid we do not have Juniper VPN Sensors planned for PRTG in the near future. Can you please upload some screenshot showing the SNMP Library Sensors monitoring the VPNs on your Juniper device? Do they show traffic on the VPN, or just the VPN State?

best regards

Hello,

Thanks for reply.

Im just using the sensor that shows status. I do not care about how much traffic goes through it. http://s30.postimg.org/orh2eib0h/ssg.png

Thank you, Torsten. That's exactly what I needed.

And congratulations to you and the whole Germany on winning World Cup.

Ok, another question for same topic. We are in last stages of testing PRTG on our network, if this works correctly, we will be making purchase.

I'm using MIB for testing STP Status. One device should be forwarding, all others should be blocking. How to setup so that "forwarding" be green for that one device and when it changes state to any other to be red (Error) and for other devices reverse: If it is "blocking" to be green and if it changes to "forwarding" to show error. I'm using: oid.bridge-mib.dot1dstpport.dot1dstpportstate.ovl from BRIDGE-MIB.

Thanks.

I really hope there is solution to this!

I'm sorry, such an inverted logic is not directly possible in the SNMP Sensors themselves. Technically you could use additional Senosor Factor Sensors to provide this functionality, but it will mean additional sensors.

Im trying to use sensor factor sensor for my setup. Im using channel definition:

#1: Status must be forwarding
Channel(6297,0) = 5

If it is correct, it shows 10,000. if it is not correct it shows 0. But it is still always green. I need it to be red if it is 0 and green if 10,000

To change the state of the sensor, you could use Error/Warning-Limits on the Channel-Settings. Or use the "Status Definition"-Field of the Factory Sensor.

Well, I edited lookups that both "forwarding" and "blocking" are OK states. I do not like red sensors unless there is an issue. So, my devices switch around forwarding and blocking, it won't change status to down. How do I setup in Error/Warning-Limits on the Channel-Settings or the "Status Definition" to have "down" red sensor when it is not what it is supposed to be?

Please, help figure it out...

I'm afraid it does not make sense to use Lookups & Limits at the same time. Both intend the same here, to alarm if a certain value is matched or exceeded (the Lookup additionally displays a String in the sensor message).
Both are for static "resolution", it seems you need a dynamic / logical relation if A then not B. This can only be achieved with the Sensor Factory.