SNMP Trap Messages

Follow the instructions in your vendor documentation on how to configure the device or software to send SNMP traps to Revolution.

To configure Revolution,

• you'll need the unique Object Identifier (OID) for the trap you want to send.

  Note: If the device generates a trap message with a NULL value, Revolution will ignore that message.

• If you're using the enterpriseSpecific trap type, you'll also need the list of vendor-specific trap codes. The vendor determines what the trap codes are.

The OID and trap codes are found in the Management Information Bases (MIB) files for the device or software.

Prerequisite: Confirm that the Revolution community string matches that of your device or software. See Make SNMP setting changes.

1. Go to Configuration > Integrations > SNMP Trap Trigger
2. Select New SNMP Trap Trigger.
3. Enter a descriptive Name.

4. For Available in All Sites:

   • Enable to ensure all your site locations have access.
   • Disable and select a Site to limit which site has access.

5. Enter the Enterprise OID for the trap being sent, as defined in the MIB files of your SNMP-compliant device or software.

   Note: This is a required field.

   For our example, 1.3.6.1.4.1.20916.1.8.2.1 is the OID – iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 20916 products(1) roomalert32E(8) traps(2) alarmmessage(1) – 20916 is the private enterprise number assigned to the vendor by the Internet Assigned Numbers Authority.

6. For Version, select the version of SNMP trap message:
   • V1 – define the version as SNMPv1.
   • V2 – define the version as SNMPv2.
   • V3 authentication – define the version as SNMPv3 and specify the following
     • Username and Authentication – Credentials used for V3 security. The Username is always required and the Authentication must have a minimum of eight characters and can not contain whitespace.
     • Authentication Type – Encryption type (MD5 or SHA) used with the authentication password.
   • V3 authentication and privacy – adds privacy information onto details similar to V3 authentication.
     • Privacy Phrase – Additional phrase required in addition to V3 credentials.
     • Privacy Type – Encryption type (DES, AES-128, AES-192, or AES-256) used with the privacy phrase.

6. (Only applies to Version V1) Select the Generic Trap Type from the drop-down list.

   For our example, I'll select enterpriseSpecific for my temperature monitoring device.

   Generic Trap Name and Number	Description
   Note: The number assigned to the trap name is automatically assigned by Revolution.
   coldStart (0)	Indicates that the agent has rebooted. All management variables will be reset; specifically, Counters and Gauges will be reset to zero (0). One nice thing about the coldStart trap is that it can be used to determine when new hardware is added to the network. When a device is powered on, it sends this trap to its trap destination. If the trap destination is set correctly (i.e., to the IP address of your Network Management System) the NMS can receive the trap and determine whether it needs to manage the device.
   warmStart (1)	Indicates that the agent has reinitialized itself. None of the management variables will be reset.
   linkDown (2)	Sent when an interface on a device goes down. The first variable binding identifies which interface went down.
   linkUp (3)	Sent when an interface on a device comes back up. The first variable binding identifies which interface came back up.
   authenticationFailure (4)	Indicates that someone has tried to query your agent with an incorrect community string; useful in determining if someone is trying to gain unauthorized access to one of your devices.
   egpNeighborLoss (5)	Indicates that an Exterior Gateway Protocol (EGP) neighbor has gone down.
   enterpriseSpecific (6)	Indicates that the trap is enterprise-specific. SNMP vendors and users define their own traps under the private-enterprise branch of the SMI object tree. To process this trap properly, the NMS has to decode the specific trap number that is part of the SNMP message.
   ANY	This trigger accepts any of the generic trap types in this table (0-6).

7. (Available only if you select V1 > enterpriseSpecific) Enter the Specific Trap Code defined by the vendor.

   For our example, my temperature monitoring device has a temperature alarm profile to notify me when the temperature falls below 60 or rises above 80. The particular alarm message that I want has a trap code of 1.

8. Select Save.

Create as many triggers as you need, and then assign them to notifications.

Here's some different ways to create trap alerts

Create an alert for each individual trap type you want to receive data on. For example, I want to know when

• new hardware is added to the network – create a trigger for trap type coldStart
• a device interface goes down – create a trigger for trap type linkDown ... and when
• a device interface is up again – create a trigger for trap type linkUp

I can then have each trigger assigned to its own notification or have one generic notification with all three triggers assigned.

Create enterprise specific alerts for each type of code you want to receive data on. For example, I want to know when

• the room temperature alarm is activated – create a trigger for trap type enterpriseSpecific and Specific Code Type 1
• there's a change in power state (main power vs batter back-up power) – create a trap type enterpriseSpecific and Specific Code Type 3

I can have each trigger assigned to its own notification, or have one generic notification with all

Create one generic alert for all SNMP trap messages – create a trigger for trap type ANY.

For this one, I'll create one notification and assign this trigger. Any time an SNMP trap message is received, the notification is sent. For enterprise specific trap messages, this trigger is sent when any vendor-defined trap code is received.

Create the notification(s) you want sent and assign the SNMP trap triggers.

• General – Typically, you'll select a Text and Images or Stored Audio notification type. You might also choose to use Text to Speech since this is an emergency notification. If you want to include an opening tone to get the receivers attention, choose Stored Audio notification type. You would not choose One-Way, Recorded, or Two-Way notification types.

• Select Triggers – Select SNMP from the Activator drop-down list and select the trigger you created.

• Message Details and Actions – Enter the content you want sent.

• Endpoints & Contacts – Assign the endpoints and contacts you want the emergency notification sent to. If you want the notification sent to the Mobile app, for example, add the contacts and make sure to check Mobile in the Contact Methods section.