<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How can I index SNMP traps with Splunk? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10079#M266</link>
    <description>&lt;P&gt;Previously, snmptrapd would accept all incoming notifications, and log them automatically (even if no explicit configuration was provided). Starting with snmptrapd release 5.3, access control checks will be applied to all incoming notifications. If snmptrapd is run without a suitable configuration file (or equivalent access control settings), then such traps WILL NOT be processed. The simplest solution is to add disableAuthorization yes to snmptrapd.conf.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Jun 2010 04:23:31 GMT</pubDate>
    <dc:creator>Dan</dc:creator>
    <dc:date>2010-06-25T04:23:31Z</dc:date>
    <item>
      <title>How can I index SNMP traps with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10077#M264</link>
      <description>&lt;P&gt;I found these basic instructions in the Splunk docs - &lt;A href="http://www.splunk.com/base/Documentation/4.0.9/Admin/SendSNMPeventstoSplunk" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/4.0.9/Admin/SendSNMPeventstoSplunk&lt;/A&gt; - but I'm not familiar with snmptrapd.  Are there instructions anywhere on how to configure it to write to a file?&lt;/P&gt;</description>
      <pubDate>Tue, 09 Mar 2010 19:19:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10077#M264</guid>
      <dc:creator>Mick</dc:creator>
      <dc:date>2010-03-09T19:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: How can I index SNMP traps with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10078#M265</link>
      <description>&lt;P&gt;The example writes the traps to the specified file.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;# snmptrapd -Lf /var/run/snmp-traps&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;The output will be in /var/run/snmp-traps.&lt;/P&gt;

&lt;P&gt;This document is mostly an example of how you can wire in arbitrary data sources to splunk.  The point is anything that can be caused to produce events in log file format can be fed into splunk. &lt;/P&gt;

&lt;P&gt;snmptrapd itself is part of the net-snmp project: &lt;A href="http://net-snmp.sourceforge.net/" rel="nofollow"&gt;http://net-snmp.sourceforge.net/&lt;/A&gt;
If you're installing this on your system, refer first to any local documentation for your distribution's packaging of the tool, and after that, the documentation here: &lt;A href="http://net-snmp.sourceforge.net/docs/man/snmptrapd.html" rel="nofollow"&gt;http://net-snmp.sourceforge.net/docs/man/snmptrapd.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The default behavior, on UNIX, seems to be to log to syslog, while on Windows to log to the Event Log.  This means that if Splunk is configured to monitor your syslog logs, or your winevent log, you will be acquiring the data.  You could alternatively configure snmptrapd to write to a specific file.  The manpage documents this is accomplished with -o filename  &lt;/P&gt;</description>
      <pubDate>Wed, 10 Mar 2010 05:59:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10078#M265</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-03-10T05:59:49Z</dc:date>
    </item>
    <item>
      <title>Re: How can I index SNMP traps with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10079#M266</link>
      <description>&lt;P&gt;Previously, snmptrapd would accept all incoming notifications, and log them automatically (even if no explicit configuration was provided). Starting with snmptrapd release 5.3, access control checks will be applied to all incoming notifications. If snmptrapd is run without a suitable configuration file (or equivalent access control settings), then such traps WILL NOT be processed. The simplest solution is to add disableAuthorization yes to snmptrapd.conf.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2010 04:23:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10079#M266</guid>
      <dc:creator>Dan</dc:creator>
      <dc:date>2010-06-25T04:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: How can I index SNMP traps with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10080#M267</link>
      <description>&lt;P&gt;Can you stuff an exaample in &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/SendSNMPeventstoSplunk"&gt;http://www.splunk.com/base/Documentation/latest/Admin/SendSNMPeventstoSplunk&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 04:08:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10080#M267</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-06-26T04:08:00Z</dc:date>
    </item>
    <item>
      <title>Re: How can I index SNMP traps with Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10081#M268</link>
      <description>&lt;P&gt;Dan&lt;/P&gt;

&lt;P&gt;Could you explain where and how to add disableAuthorization Yes to Snmptrapd.conf ?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2016 16:39:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-can-I-index-SNMP-traps-with-Splunk/m-p/10081#M268</guid>
      <dc:creator>vr2312</dc:creator>
      <dc:date>2016-07-07T16:39:54Z</dc:date>
    </item>
  </channel>
</rss>

