Splunk® Enterprise

Getting Data In

Acrobat logo Download manual as PDF

Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Acrobat logo Download topic as PDF

Send SNMP events to Splunk Enterprise

Simple Network Management Protocol (SNMP) traps are alerts that remote devices send out. This topic describes how to receive and index SNMP traps at the Splunk Enterprise indexer.

The procedures in this topic (for both *nix and Windows) are examples only. You can accomplish the task of sending SNMP traps to Splunk Enterprise in a number of ways. For example, instead of using Net-SNMP, you can use other tools, such as Snare or SNMPGate, to write SNMP traps to file storage for monitoring by Splunk Enterprise.

For information on how to use Splunk Enterprise as a monitoring tool to send SNMP alerts to other systems, such as a Network Management System console, see Send SNMP traps to other systems in the Alerting manual.

How to index SNMP traps

The most effective way to index SNMP traps is to first write them to a file on the Splunk Enterprise server. Then, configure Splunk Enterprise to monitor the file.

To consume SNMP trap data:

1. Configure the remote devices to send their traps directly to the Splunk Enterprise instance IP address. The default port for SNMP traps is udp:162.

2. Write the SNMP traps to a file on the Splunk Enterprise instance, as described in Write SNMP traps to a file on the Splunk Enterprise server.

3. Configure Splunk Enterprise to monitor the file, as described in Monitor files and directories.

Note: This topic does not cover SNMP polling, which is a way to query remote devices.

Write SNMP traps to a file on the Splunk Enterprise instance

Use your favorite SNMP software to write the SNMP traps to a file. For information about available SNMP software, visit the SNMP portal (http://www.snmplink.org) website.

For *nix

On *nix, you can use the Net-SNMP project snmptrapd binary to write SNMP traps to a file.

Before you install snmptrapd on your system, see the local documentation for the version of snmptrapd that comes with your distribution of *nix. See also the manual page for snmptrapd.

The simplest configuration is:

# snmptrapd -Lf /var/log/snmp-traps

Note: Versions 5.3 and later of snmptrapd apply access control checks to all incoming notifications instead of accepting and logging them automatically (even if no explicit configuration was provided). If you run snmptrapd without suitable access control settings, then it does not process those traps. You can avoid this by specifying:

# snmptrapd -Lf /var/log/snmp-traps --disableAuthorization=yes

To see the version of snmptrapd, run snmptrapd --version from the command prompt.

Troubleshoot problems with SNMP

If you experience problems sending SNMP traps to Splunk Enterprise, consider that:

  • UDP port 162 is a privileged network port. If you need to use this port, then you must run snmptrapd as root.
  • You can use the -f flag to keep snmptrapd in the foreground while testing.
  • You can use the -Lo flags instead of -Lf to log to standard output.
  • You can use the snmptrapd command to generate an example trap, for example:

# snmptrap -v2c -c public localhost 1 1

For Windows

To log SNMP traps to a file on Windows.

1. Download and install the latest version of NET-SNMP for Windows from the NET-SNMP website.

Note: The OpenSSL library must not be installed on the system because it conflicts with NET-SNMP.

2. Register snmptrapd as a service using the script included in the NET-SNMP install.

3. Edit C:\usr\etc\snmp\snmptrapd.conf:

snmpTrapdAddr [System IP]:162
authCommunity log [community string]

4. The default log location is C:\usr\log\snmptrapd.log

Use Management Information Bases (MIBs)

Management Information Bases (MIBs) provide a map between numeric object IDs (OIDs) that the SNMP trap reports and a textual human readable form. Though snmptrapd can work without any MIB files at all, it does not display the results in exactly the same way.

The vendor of the device you receive SNMP traps from can provide a specific MIB. For example, all Cisco device MIBs can be located using the online Cisco SNMP Object Navigator.

To add a new MIB file:

1. Download and copy the MIB file into the MIB search directory. On the *nix version of Net-SNMP, the default location is /usr/local/share/snmp/mibs. You can set a different directory by providing the -m argument to snmptrapd.

2. Instruct snmptrapd to load the MIB(s) by passing a colon-separated list to the -m argument.


  • If you add a leading '+' character for the parameters in the -m argument, snmptrapd loads the MIB in addition to the default list, instead of overwriting the list.
  • The special keyword ALL tells snmptrapd to load all MIB modules in the MIB directory.

For example, to load all MIB modules in the MIB directory:

     snmptrapd -m +ALL
Last modified on 20 February, 2016
How the Splunk platform handles syslog data over the UDP network protocol
About Windows data and Splunk Enterprise

This documentation applies to the following versions of Splunk® Enterprise: 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters