SNMP Trap Introduction

An SNMP trap is a notification event sent by a managed device over a network when a change-of-state (COS) event occurs. Some events that will cause a device to send SNMP traps include power outages, security breaches, and other major events. However, devices will also send traps for simple status events, such as doors opening and closing. These traps are sent across the network in the same manner, and are given no priority when using a standard SNMP manager.

MIB Flow Char

Trap Messages From SNMP Devices Managed by One SNMP Application.

Simple Network Management Protocol (SNMP) is used when sending trap communications across a network to the device manager. In some cases, SNMP alleviates managers of some responsibility. They don't have to request information from every device in the network individually. Instead, managed devices send unsolicited notification in the form of autonomous traps. Traps are sent to one common SNMP network monitoring application.

Managers then receive the SNMP trap, and can take action based upon the event described by the trap. Managers cannot send a trap message back to a device. Trap communication only occurs from device to network manager. The management application must alert the proper person of the event.

SNMP Capture Results

Autonomous Traps Notify You of All Critical Alarm Events.

SNMP trap requests can fall under two groups, polled or autonomous. When an SNMP manager operates using polled SNMP traps, it will periodically request updates from all managed devices. This is done according a specific time frame, such as every half hour, or every five minutes. When traps are autonomous, they are automatically sent to the manager any time a COS event occurs.Autonomous SNMP traps are sent every time a door opens or closes. There is no repeated update process every few minutes.

An SNMP Alarm can be Identified Through Trap ID Granularity or Through Variable Bindings.

SNMP traps sent from devices most likely conform to 1 of 2 major trap systems. They are either granular traps or use variable bindings. What happens when a trap message is assembled in the granular format? Each single trap is given a trap identifier rather than a Variable Binding Style (VBS). This identifier is a number that is recognized by the SNMP manager. It denotes a particular state change. It could be something like a door opening. T/Mon makes use of this message format.

Other SNMP managers assemble their traps in the VBS format. This assigns each trap the same trap ID number and store alarm data in the variable bindings of the trap. The messages differentiate by giving a different detail message for each trap. This could be indicating a door is open or a battery charge is low.

Get a Custom Application Diagram of Your Perfect-Fit Monitoring System

There is no other network on the planet that is exactly like yours. For that reason, you need to build a monitoring system that's the right fit for you.

"Buying more than you need" and "buying less than you need" are real risks. You also have to think about training, tech support, and upgrade availability.

Send me a quick online message about what you're trying to accomplish. I'll work with you to build a custom PDF application diagram that's a perfect fit for your network.

Make an Informed Decision

Your network isn't off-the-shelf.

Your monitoring system shouldn't be, either.

Customized monitoring application drawing

We'll walk you through this with a customized monitoring diagram.

Just tell us what you're trying to accomplish with remote monitoring.

Get a Custom Diagram