SNMP traps contain information sent from a monitored host to a monitoring server using the SNMP protocol.

Trap definition files are used to define the actions to be performed when a Box receives an SNMP trap.

• If an action is defined for the received trap in a trap definition file, it will be run. The trap will be written to a TRAP file with the IP address of the machine that sent it.
• If no action is defined, the trap will be written to an unknown trap file.
   

You set up monitoring for SNMP traps in the Box using the TRAP-Handle service template.

Notes

• To use services based on SNMP traps, specific prerequisites must first be met.  See the detailed procedure.

• To interpret the events received, the monitoring server must have an MIB file containing the OIDs (message IDs) and their descriptions.
  • Standard MIBs use standardized OIDs.
  • Manufacturers can also define their own MIBs for their host templates. You should retrieve the manufacturer MIB files from the equipment manufacturer.
• You can create trap definition files manually or automatically using an MIB file.
   

List of files for monitoring SNMP traps

• /etc/snmp/snmptt.ini: List of trap definition files to be taken into account.
• /etc/snmp/trapConf/*: List of trap definition files. One action is configured for each trap.
• /var/log/snmptt/*.trap: File containing the traps received by the Box. There is one file for each server that generates traps.
• /var/log/snmptt/snmpttunknown.log: List of files containing unknown traps, i.e. unspecified in trap definition files.
   

Purpose of the TRAP-Handle service template

• It checks the trap log file generated by SNMPTT.

Characteristics of an SNMP trap definition file

• An SNMP trap definition file is a text file that contains two rows for each event.
  • EVENT row: Description of the type of event, with the name of the event ({Event_name}) and its OID ({Event_OID}).
  • EXEC row: Description of the action to be performed when the trap is received, with the description of the event ({Event_description}). 

• The trap complies with a specific syntax.
  • Fields in the message written in the trap file are separated using the  |-|.
  • The description written in the third field appears in the Web app via a dataviz.
  • $1 indicates the first variable in the trap.

Examples

Trap definition file for a Juniper SRX host used to capture UP and DOWN events for a network link and Fan Fail events

File containing received traps

Best Practice

• To find out more about the variables in host traps, see the relevant MIB description.
• To display all of the variables in a trap, use the instruction $*.

Procedure: How to create an SNMP trap definition file

Prerequisites

       See the detailed procedure

Step 1: Create trap definition files to define the actions to be performed when an SNMP trap is received

Manual creation of the trap definition file

1. Create a trap definition file.

• Log in to the Box.

• Run the commands below.

2. Specify the information on the new event.

• Add the rows below to the file.
  Replace:
  • {Event_name} with the name of the event.
  • {Event_OID} with the OID of the event as specified in the MIB file.

Automatic creation of the trap definition file

1. Generate the trap definition file automatically using an MIB file.

2. Copy the file to the folder called /etc/snmp/trapConf.

3. Run the command below to restart the snmptt service.

4. Check that the trap is correctly received.

• Run the command below in the Box to generate a trap for itself.
  Replace:
  • {Event_OID} with the OID of the event as specified in the MIB file.
  • {Community_name} with the SNMP community.

• Check that a file called snmptt/127.0.0.1.trap is successfully created in the /var/log/ folder and that it contains the trap.
   

Step 2: Use a trap definition file

1. Run the commands below to open the snmptt.ini configuration file.

2. Run the command below to add the path of the trap definition file to the [TrapFiles] section at the end of the file.

3. Run the command below to restart the snmptt service.

Step 3: Set up monitoring for SNMP traps in the Box using the TRAP-Handle service template

1. Go to the Web app.

2. Create a new service template.

• Select  Configuration > Services > List in the menu.
• Click + Add in the Mode: Box tab. 

• Specify the information below.

General information tab
         

Availability and checks tab
         

• Click Validate.