PRTG - SNMP Trap Receiver
Hello and welcome to the video about Paessler's new PRTG SNMP trap receiver sensor.
The trap receiver works quite differently from most of the other PRTG sensors. The other sensors are very active sensors that are polling the end devices so the other types of sensors send out monitoring queries to collect the data and send it to the core server for analysis.
The trap receiver sensor works, like I said, quite differently. It is a passive sensor. It does not send out queries rather it sits back and waits for devices to send it traps.
So the first step in configuring the trap receiver sensor is to actually configure the devices to send the traps to PRTG. Unfortunately I can't show you how to do this because it's different for every device but usually you just need to put in the IP address and maybe the port number and the target trap receiver - in this case your PRTG server.
Then you need to configure PRTG to receive the traps and to do that you need to create a trap receiver sensor. So let me do that right now by going to sensors and add sensor. And I'm gonna put it for now on my probe device and the type of sensor I'm looking for is trap receiver.
There it is. I'll name it our video trap receiver and for now I'm just gonna leave the defaults how they are and we'll come back to the settings in a minute. And there's my sensor now on the sensors first created is all grey because I still initializing. While its initializing I can explain one thing you have a fundamental decision to make when you're creating one of these trap receiver sensors. And that is at what level in your tree do you want the sensor to be.
You can either put it at the pro level and then it will receive all the traps for all the devices on that probe or if you'd like to you can put it on an individual device and then it receives only the traps for that device. You can also choose to have individual sensors on multiple devices or you could trap receiver sensors on it. And with different type of filter walls. The granularity that you work with is entirely up to you. So to get our trap receiver working I'll send you to send us some traps and so I got a little the pretest to hear contraption. That was send traps.
So let me send a few and let's see as a first step that we actually get some traps arriving at our sensor. There we go. Our sensor has gone green but it's not showing me the actual track messages that have been received yet. Let's give it a second. There we go. There are the traps I just sent. So first step accomplished we are receiving traps in our trap receiver. Now if all you want to do is receive the traps so that you can save them somewhere for later analysis then you could stop now, you're done. The messages themselves will be logged under this messages tab and you can go back and look at them anytime you want.
However you probably want to be a little more active than that, not just logging them but doing some kinda warnings and alarms based on the traps. So now we're gonna go back and look at those settings that we had. In the settings for the trap receiver sensor there's a tag the default a strap sensor.
The priority you can change here if you'd like the same as you can with any sensor. You can configure which port the trap should be received on and this is fairly important if you're getting a lot of traps. You configure here how long you want PRTG to keep the traps on the desk.
Because if you're getting a lot of messages you'll be filling this quite quickly. So pay a little bit of attention here and be careful how long you keep the messages. Than the most important part of the sensor is the filter and the filter walls. Now I know you can't really see these on the video but when you create your own sensor you'll be able to read them. These are options that you can use to filter traps.
So by default every trap that arrives will be recorded and that's what's here by default under "any" include any. You can also choose to exclude some if you want messages from a particular device to be ignored or even within one device messages from a particular subsystem to be ignored. Then you can create a filter will hear to ignore them and they'll they'll just be dropped then.
Then you can create filters here to define which messages are a warning for you and which messages are an error. The choices you have here for the filters are the source IP, the agent, the enterprise, OID this is an SNMP trap so you can just define which OID it is, the bindings, the generic trap tight, the specific trap tight, which SNMP version number it is, and community strings.
And you can use "and" in order to build more complicated filter messages if you'd like. So now I'd like to set up an error filter that we can use to receive notifications based on the content of some other traps. Now in my test tool I have one that will send the stream too hot. So I'm gonna set up the filter that says the bindings. We see the text too hot and that's an error message.
So let me say that. And now using my test tool let me send a few messages with the word too hot in them. There we go. Let's see if we could see those arriving. There we have some that say too hot. And now our sensor should notice that is getting trap saying too hot and should go to red. There we go. We've seen it go red. Now if I do nothing if I send no more traps with the error message then the next polling period I should go green again, so I'm gonna stop sending messages and while we're waiting for that i'm gonna look at the notifications. If you'd like to receive an e-mail or an SMS that something has gone wrong then you need to set up a notification.
By default it will inherit from its parent in the tree but for the demo today I'd like to do one that I can really see in action. So I'm gonna say when my sensor goes down for zero seconds so immediately. I'm going to send an email. I'm not going to escalate when the condition clears then I'd like to see an email again. And I'll say that. So now when we see state changes between down and up we should get emails to that email address.
Let me go back to my sensor. It has gone green again, very good. I'm going to trigger it to go red again by sending it a whole bunch more "I'm too hot" messages and we wait for the polling period. It has gone read very good we wait again for that polling period to be finished I'm not sending it anymore errors and it's going green again.
So we've just seen the sensor go red and go green. We had a notification set up to send an email let's see what we see hey look at that, we've got some messages arriving that our trap receiver has seen an error. And has gone okay again so our notifications are working we're getting the emails. Okay there's one other thing I'd like to show you about the trap receiver and that's how to work with private mips with the trap receiver.
Because when you're working with traps you will often be working with private mibs rather than with standard mibs. The traps you'll be receiving is something very specific to that one manufacturer and you need some way to translate them.
As an example I sent a few more traps these happen to be from the network appliance private mib. But when they show up all you see is enterprises ....which is maybe not the most useful error message for us.
So what I like to show you now is how to include the private mibs in PRG so that you care reasonable track messages. And what you need to do is go to your standard PRTG installation directory. It's PRTG network monitor and then a subdirectory called mibs. And and I have a couple tucked away here that I'm gonna use as an example. And all I'm gonna do is copy the mib files that I got from my manufacture in this case network appliance into this mib directory.
Once they're there then I need to restart the server. So let me go into setup and system administration "Administrative Tools" and restart the core server. And now we need to wait a second so bear with me until the servers back, it takes a couple of minutes. Okay once the server comes back up we need to login again and go back to our sensor. Here it is our video trap receiver and I'm going to send the same trap again. This was that net up one. Wait for it to arrive. And now we see instead of that funny number the ....I think it was now we see that it's the net admib and is the product serial number that sending the trap.
So that's what I wanted to show you today with the SNMP trap receiver.I encourage you to look at the other videos we have on our website and if you have any questions either about the trap receiver or about any other feature in PRTG you can write to us at any time at
Thanks and bye!