I have a few devices (switches, routers and a UPS) which are able to send SNMP Traps. My intention would be to include these in PRTGs Monitoring. Is that possible, if so how to do?
The following information is deprecated as of PRTG 14.1.8. It applies to the SNMP Trap Receiver sensor in PRTG 7 through 13.
PRTG version 14.1.8 and later includes an SNMP Trap receiver which is designed for high performance usage in order to review and analyze incoming trap messages from various devices.
PRTG's Trap Receiver
SNMP Traps are packets containing one or more parts of information sent by an agent to a dedicated listening device via the Simple Network Management Protocol (SNMP).
With the SNMP Trap Receiver sensor you can configure any PRTG probe device as a trap receiver. The sensor checks every interval if new traps have been received and reports the number of traps received so far in its primary channel.
These are the differences between a dedicated trap receiver and PRTG's trap receiver:
- Dedicated trap receivers are optimized to receive and process many different traps from a large number of devices.
- Dedicated trap receivers are able to store many messages per time interval in their internal database for later analysis.
- PRTG's trap receivers are not suitable to handle high loads, process many different message types or to store many messages in its log database. It can process some hundred messages per minute, one sensor can process and check one message type and PRTG can store some hundred messages per minute in its log database (across all trap sending agents).
The sensor is not intended to be a full-scale replacement for a dedicated trap receiver. It is a great tool if you need to monitor a handful of devices that send traps from time to time. And, as such, it avoids the need to install, setup and manage a dedicated trap receiver software for just a few devices.
Configuring an SNMP Trap Receiver Sensor
To create a SNMP trap sensor navigate to your "Local Probe" (or one of your remote probes) and choose "Add Sensor". From the sensor type selection menu choose "SNMP Trap Receiver".
In the sensor settings you must enter a listening port (the common port number is 162).
Note: Remember that the listening port must be opened if you run a firewall on the probe system (the built-in Windows Firewall will be configured automatically by PRTG).
Note: You can only create SNMP trap sensors on probe devices, seeing as the PC running the probe software is the actual receiver.
Settings of SNMP Trap Receiver Sensor
- OID value: SNMP traps sent by agents may contain several different textual information entries, each represented by a unique OID. It is therefore necessary to tell PRTG which part of the trap you want to log. Please refer to the trap sending device description to find the appropriate OID.
- When a message comes in: Activate the option "Write message to log and fire change trigger" to fire the "change trigger" for this sensor and to write a log entry whenever a trap is received (this may create lots of log entries, use with caution). This is only suitable when a few messages per minute are received. After creating the sensor you can enter a "change" trigger on the notifications tab of the sensor that will send a notification (e.g. email) whenever a trap comes in.
- Set Sensor to 'Warning' (available in newer versions): Define when the sensor will be put to a Warning status.
- Message must include: This setting allows you to define a string. The sensor will go into warning status (error in older versions) if one or more of the incoming messages do not contain this string.
- Message must not include: Here you can enter a second string. The sensor will go into warning status (error in older versions) if a message contains this string. The first option allows you to create a log of all incoming messages (at least for small scenarios with <100 messages per minute).
For details and other settings, please see PRTG Manual: SNMP Trap Receiver Sensor
The last two options are used to filter out specific messages. Configure a "state trigger" for "down" on the notification tab and PRTG will trigger an email if a message meeting any or both of the two criteria is received.
an explicit OID needs to be entered in the PRTG Trap sensor.
If you are not sure what OID you have to use you might want to use a tool like
Trap Receiver http://www.trapreceiver.com/
to find the exact OID for the information you want PRTG to monitor
If PRTG Snmp Trap receiver is configured on a probe with two Network Cards, is the Sensor listening on both interface?
Hi There, is it posible to recive *all* SNMP Traps? We seam to be able to receive only one trap from one specific OID. But we would like to receive (and see) all the traps. Regardless if have specivied an OID or not (i.eg. everything that starts with 18.104.22.168.4)
Hello, I'm afraid that's not possible.
In der neuesten deutschen Version kann ich nur einstellen, dass der Sensor auf den Status Warnung geht. Ist es auch möglich den Sensor auf Fehler / Error zu setzen?
Das ist nicht möglich.
Hi to all, Where, in PRTG, I have to configure the community for Trap Receiver sensors?
In the Credentials for SNMP Devices you can configure what the community, port and version. This is found under the device's settings.
thanks for fast reply, but maybe I didn't explained my problem.. I activate a Trap Receiver sensor on PRTG local probe. In that sensor's settings I put: 1- the correct OID I expect to receive traps (verified with wireshark); 2- default snmp trap port udp162; ..other default settings.. But I don't see the place where to put the trap community!
Maybe you mean that the community is the same that I find in "Credentials for SNMP Devices" in Local probe's settings? If so, I already tried, but no trap are received from PRTG.
Obviously trap version is 1 and with wireshark I see that trap is received by server..
..What's the trick?
Thanks in advance!
Do you know whether the OID that you are using is explicit? Unfortunately the trap receiver is limited (although a new version is coming out soon to resolve this) and you have to define a specific OID for PRTG to watch. If this is an enterprise OID, with others beneath it in the tree, PRTG cannot handle this.