Event collection for SNMP traps

Event Management can process SNMP traps as events. In this configuration, a MID Server acts as a collection endpoint for SNMP traps. Upon receiving a trap, the MID Server sends the trap to the ServiceNow instance for further processing as events by Event Management.

Before you begin

Before starting this procedure, confirm with your ServiceNow representative that the server and software specifications for hosting the MID Server are met. Also confirm that the MID Server version matches the ServiceNow instance version. For example, navigate to MID Server, click a Name, and confirm that the Version is the same as the ServiceNow instance version.

Role required: evt_mgmt_operator

About this task

Use the Discovery Trap Collector Extension to process SNMP traps as events. In this configuration, a MID Server acts as a collection endpoint for SNMP traps.

Procedure

  1. Navigate to Event Management > Event Listener (Push) > MID SNMP Traps Listener.
  2. Click New.
  3. Complete the form:
    OptionDescription
    Name Unique name for the SNMP Trap Collector.
    Short description Short description of the MID Server extension execution context.
    Extension The MID Server extension of this context. This field is automatically populated.
    UDP Port UDP port for SNMP Trap Collector to receive SNMP Traps. The default value is 1,162. However, if the port is already in use, you can use port 162 instead.
    Status The current status of this extension execution context. This field is automatically populated.
    Execute on Select either Specific MID Server or Specific MID Server Cluster.
    MID Server MID Server or MID Server Cluster to host the SNMP Trap Collector from the MID Server reference field.
    Executing on

    The name of the MID Server on which the extension is running. This field shows the name of the MID Server even if the MID Server is down. If the extension is stopped by the user, this field is empty.

    This field is automatically populated.
  4. In the Related Links section, click Test.
  5. Click Submit.
  6. (Optional) If the MID Server fails to start, review the MID Server log errors.
  7. (Optional) For high availability, add a second MID Server and configure the trap sender so that both MID Servers receive the same SNMP traps. To prevent duplication, only the active MID Server actually processes SNMP traps.

What to do next

In Related Links, these actions may be run against the SNMP traps listener:
Table 1. Commands available in the SNMP trap listener form
Related Link Description
Start Starts the listener if it is currently not running. The listener is started on the configured MID Server and port number.
Stop Stops the running listener on the configured MID Server. No action is taken if the listener is not running.
Restart Stops, then starts the listener on the configured MID Server and port number.
Test Verifies that the configured MID Server can run the SNMP trap listener on the specified port. Running a test does not affect any listener that are currently running.
Update parameters If you make changes to the listener configuration, use this option to update the parameters of the currently running listener. First, the parameters are tested for validity. If the parameters are valid, the listener disconnects and reconnects with the new parameters.