PRTG receives and
analyzes your SNMP traps
PRTG lets you send, receive and analyze SNMP traps
- PRTG receives thousands of SNMP traps per second
- PRTG filters SNMP traps automatically
- PRTG immediately notifies you in the event of critical situations
What is an SNMP trap?
SNMP traps are one of the oldest standards for network equipment fault notification. Being one of the oldest standard protocols, most network devices with basic management capabilities usually support SNMP traps. When a device detects an error or a change, the device will send a notification to one or more trap receivers.
SNMP traps contain information like:
- Time, source, and version of event
- Severity, agent, and event OID (ID of specific event)
- Event message/description or “Bindings”
Some trap examples are:
- Someone activates a network port by plugging in a computer
- An internet connection goes down on a router
- Loss of power on an UPS
- An open case in a server
- A dead drive in a NAS/SAN or other storage device
Use the following PRTG sensor to start receiving and analyzing SNMP traps
What is a sensor?
In PRTG, “sensors” are the basic monitoring elements. One sensor usually monitors one measured value in your network, e.g. the traffic of a switch port, the CPU load of a server, the free space of a disk drive. On average you need about 5-10 sensors per device or one sensor per switch port.
How the sensor works: The PRTG SNMP Trap Receiver Sensor is a passive receiving sensor. It does not actively query data at fixed intervals, but instead collects incoming trap messages. The PRTG server uses this sensor to receive data and – depending on the filter rule – sound the alarm.
What the sensor displays: The SNMP Trap Receiver Sensor displays the total number of traps received per second, as well as the number of messages that are classified as warnings or errors. It also indicates how many trap packets are lost per second. When using this sensor, you can set your own filter rules.
PRTG saves incoming trap messages as regular system files, and neatly displays them in the sensor. The Trap Receiver Sensor lets you analyze traps and filter them according to date, source, agents, bindings, and more. Be sure to copy the MIB file from the source device and save it in your PRTG program path. PRTG will use this MIB to make your trap messages legible.
How PRTG helps you analyze SNMP traps
SNMP stands for Simple Network Monitoring Protocol. Its usefulness in network administration comes from the fact that it allows information to be collected about network-connected devices in a standardized way across a large variety of hardware and software types. SNMP is a protocol for management information transfer in networks, for use in LANs especially, depending on the chosen version.
Critical system monitoring
Above all else, SNMP trap monitoring is designed for the critical systems that are fundamental to your company. If one of these systems malfunctions, then time is of the essence.
If a critical situation arises, you’ll be notified by PRTG at once – not just when the next scanning interval is scheduled to query your data. PRTG receives the traps, classifies them as errors or warnings, and sounds the alarm.
If a device crashes, often it continues to send log messages with information about the crash, including that which may have caused it. By using PRTG as your trap receiver, you’ll see what happened just before the malfunction, and can therefore quickly get to the root of the problem.
Not a single administrator enjoys spending all their time monitoring network components for unwanted intrusions. SNMP trap monitoring uses trap messages to keep you in the know – such as when someone logs into your system during the night even though no one is in the office.
Thanks to the pre-configured sensor of PRTG, your SNMP trap monitoring will be up and running in no time. Step-by-step instructions facilitate the setup process.
Keep a constant eye on your network –
even while on the go
PRTG can be started within minutes and it's compatible with many mobile devices.
Tutorial: 5 easy steps for setting up SNMP trap monitoring
Configure the target device
Configure your target device so it can send SNMP traps. This configuration varies according to the device and its manufacturer (Cisco, HP, Dell, etc.). In general, the IP address and the trap receiver port will be requested.
Add the SNMP Trap Receiver Sensor
In this step, you’ll incorporate the SNMP Trap Receiver Sensor into your PRTG monitoring. Use the “Sensor/Add Sensor” menu option to search for and add the sensor. Be sure to add the sensor to your probe device. By doing so, you’ll receive traps from all the devices that are connected to the probe. If you add the sensor to a specific device, then only the traps of that device will be received.
Configure the sensor
Configure the filter rules in the sensor settings. By default, every trap will be received. The “Exclude” filter lets you exclude certain types of trap messages, e.g. traps from a specific IP address that do not need to be considered. Use the warning and error filters to define those traps which will prompt PRTG to sound the alarm.
Set up the notification system
In “Notifications,” choose whether you’d like to be alerted by email, SMS, push notification, or some other action. You can also opt to be notified when trap messages are received, and have these messages saved so you can analyze the incidents later.
Sit back and relax
Your SNMP trap monitoring is configured and ready to go. You can now get back to your other tasks.
Video: How the SNMP trap monitor PRTG works
Trusted by 300,000 users
and recognized by industry analysts as a leader
- Unlimited version of PRTG for 30 days
- After 30 days, PRTG reverts to a free version
- Or, you can upgrade to a paid license anytime
The short and sweet of it:
All you need to know about SNMP traps
What is an SNMP trap?
The network protocol SNMP (Simple Network Management Protocol) supplies information on the statuses of individual systems and devices. An SNMP trap is a log-like message that is sent from a device to a “receiver.”
What does an SNMP trap contain?
SNMP packets consist of a packet header, a PDU header, and a PDU body. For trap messages, the information sent in the PDU header can vary. The PDU header of an SNMP trap packet contains the packet types, the OID of the device, the IP address of the sender, general and company-specific IDs, and the time the trap event occurred. The actual values are sent in the PDU body.
How can I receive SNMP traps?
An SNMP trap receiver collects SNMP messages that are sent from network devices to the network management station. Monitored devices send SNMP traps at will to report incidents to the management system. PRTG can handle thousands of SNMP traps per second.
Will I need a trap server?
The term “trap server” is sometimes used synonymously with “trap receiver.” This server receives and processes messages. The SNMP Trap Receiver Sensor lets you configure any PRTG probe device as an SNMP trap server. PRTG supports SNMP v1 traps as defined in RFC 1157, and SNMP v2c traps as outlined in RFC 3416.
Can PRTG analyze and display SNMP traps?
PRTG receives the traps, which include the number of messages received per second, warnings, errors, and lost data packets. PRTG presents trap content and messages in an easy-to-read table. Data can be filtered however you like.
How thoroughly are the SNMP traps analyzed?
With PRTG, you get a quick overview of the traps and their contents, and will be notified immediately in the event of a problem. If you need a more thorough analysis, various specialized tools will allow you to examine traps in detail.
Which port is used for the transmission of SNMP messages?
By default, SNMP traps are sent via UDP port 162. This port must be set as the destination port in your source devices.
What is the difference between Get, GetNext, Set, and Trap?
SNMP works on the assumption that a network management system submits a query, and a managed device returns an answer. There are four possibilities for this exchange: Get, GetNext, Set, and Trap. With Trap, SNMP traps are automatically sent from a device to a compatible receiver – without the receiver requesting them. This is not the case with Get and GetNext. With these commands, queries are performed manually. Set is not a traditional monitoring function.
Does the SNMP trap monitor work with Windows?
PRTG has always been developed for Windows systems, which means you can also set up your trap monitoring in Windows.
Over 95% of our customers recommend PRTG
Paessler AG worldwide trialled PRTG in over 600 IT departments.
The aim was to tune the network monitoring software closer to the needs of the administrators.
The result of the survey: over 95% of the participants would recommend PRTG - or already had.
“We can all work with greater peace of mind knowing
that our systems are constantly being monitored.”
Markus Puke, Network Administrator, Schüchtermann Klinik, Germany
PRTG simplifies your day
Our monitoring software works for you and promptly notifies you of potential issues.
It frees you to concentrate on your day-to-day tasks with peace of mind.
PRTG saves time
With PRTG, you get one central monitoring tool for your servers and entire network. Enjoy a quick overview of your whole infrastructure via our dashboard and app.
PRTG saves worry
Customizing PRTG is a breeze. Getting started or switching from another network monitoring tool is easy thanks to the auto-discovery and pre-configured device templates.
Three reader tips from our knowledge base
See our knowledge base for thousands of helpful articles on PRTG. When it comes to SNMP and SNMP traps, we recommend the following:
- How can I configure sensors using speed limits to keep the status for more than one interval?
- How do I test the SNMP Trap Receiver Sensor?
- My SNMP sensors don't work. What can I do?
PRTG: The Swiss Army knife for sysadminsAdapt PRTG individually and dynamically to your needs relying on a strong API:
- HTTP API: Access monitoring data and manipulate monitoring objects using HTTP requests
- Custom Sensors: Create your own sensors for customized monitoring
- Custom Notifications: Create your own notifications to send alarms to external systems
- REST Custom Sensor: Monitor almost everything that provides XML or JSON
Want to learn more about PRTG?
PRTG comes with several pre-configured SNMP sensors, some of which have been designed especially for device manufacturers such as Cisco, Dell, and HP. Learn which applications and servers are putting the greatest strain on your network’s bandwidth.
PRTG provides for efficient and centralized Syslog message management. It collects Syslog messages according to origin and severity, as well as time and IP address. With PRTG, you can seek out weak spots and take action at once.
Syslog stands for System Logging Protocol and is a standard protocol used to send system log or event messages to a specific server, called a syslog server. It is primarily used to collect various device logs from several different machines in a central location for monitoring and review. The protocol is enabled on most network equipment such as routers, switches, firewalls, and even some printers and scanners. In addition, syslog is available on Unix and Linux based systems and many web servers including Apache.
PRTG is comprehensive network monitoring software. It lets you monitor systems, devices, and applications by working with a variety of different technologies, including SNMP, NetFlow, packet sniffing, and WMI.
PAESSLER AG –
German quality engineering
Still not convinced?
More than 300,000 sysadmins love PRTG
PRTG is used by companies of all sizes. Sysadmins love PRTG because it makes their job a whole lot easier.
Still not convinced?
Monitor your entire IT infrastructure
Bandwidth, servers, virtual environments, websites, VoIP services – PRTG keeps an eye on your entire network.
|Network Monitoring Software - Version 184.108.40.2063 (July 6th, 2021)|
|Download for Windows and cloud-based version PRTG Hosted Monitor available|
|English, German, Spanish, French, Portuguese, Dutch, Russian, Japanese, and Simplified Chinese|
|Up to 100 sensors for free (Price List)|
|Network devices, bandwidth, servers, applications, virtual environments, remote systems, IoT, and more|
Supported Vendors & Applications