<?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 to monitor switch, router... and other Cisco devices using SNMP. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275563#M52853</link>
    <description>&lt;P&gt;I have installed NET-SNMP on splunk machine (winserver 2008 R2). &lt;BR /&gt;
1. splunk machine &lt;BR /&gt;
- edit file C:/usr/ etc/snmp/snmptrapd.conf&lt;BR /&gt;
snmpTrapdAddr 192.168.1.100:162&lt;BR /&gt;
authCommunity log public&lt;BR /&gt;
- Add data -&amp;gt;monitor-&amp;gt; UDP port 162&lt;BR /&gt;
2. Router&lt;BR /&gt;
I configured&lt;BR /&gt;
Router(config)# snmp-server community public ro&lt;BR /&gt;
Router(config)# snmp-server community public rw&lt;BR /&gt;
Router(config)# snmp-server host 192.168.1.100 version 2 public&lt;/P&gt;

&lt;P&gt;But on splunk machine i didn't receive snmp. what did wrong?&lt;/P&gt;</description>
    <pubDate>Mon, 19 Oct 2015 13:45:28 GMT</pubDate>
    <dc:creator>ledaipro</dc:creator>
    <dc:date>2015-10-19T13:45:28Z</dc:date>
    <item>
      <title>How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275556#M52846</link>
      <description>&lt;P&gt;Hi. &lt;/P&gt;

&lt;P&gt;Using NET-SNMP on Windows to receive and log SNMP traps to a file, and I want Splunk monitor that file. How to do this?&lt;BR /&gt;
I installed NET-SNMP on Windows &lt;BR /&gt;
What is next step?&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2015 15:17:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275556#M52846</guid>
      <dc:creator>ledaipro</dc:creator>
      <dc:date>2015-10-18T15:17:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275557#M52847</link>
      <description>&lt;P&gt;Hey! &lt;/P&gt;

&lt;P&gt;This is fairly simple since you will be monitoring just one file containing all your SNMP traps logs.&lt;BR /&gt;
Assuming your Splunk indexer is located in a dedicated server somewhere else, you will have to install an Universal Forwarder in the Windows instance where  the snmp traps log file is located..&lt;/P&gt;

&lt;P&gt;Download the Universal Forwarder, install it and as a best practice I would recommend you to create an &lt;STRONG&gt;inputs.conf&lt;/STRONG&gt; and &lt;STRONG&gt;outputs.conf&lt;/STRONG&gt; file located inside an app, which is basically a directory where you will palce both files for snmp traps, for example:&lt;BR /&gt;
&lt;CODE&gt;$SPLUNK_HOME\etc\apps\UF-SNMP_collection.&lt;/CODE&gt; This will be a scalable way of managing all your inputs centrally from a deployment-server. &lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;&lt;STRONG&gt;Universal Forwarder&lt;/STRONG&gt; &lt;/P&gt;

&lt;P&gt;UF-SNMP_collection &amp;gt; default &amp;gt; &lt;STRONG&gt;inputs.conf&lt;/STRONG&gt; &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://C:\folder1\folder2\snmptraps.log]
host          = yourhostname
index         = (defaults to *main*, but creating a test index is a best practice)
sourcetype    = snmptraps could be a good one.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;UF-SNMP_collection &amp;gt; default &amp;gt; &lt;STRONG&gt;outputs.conf&lt;/STRONG&gt; &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
defaultGroup = default-autolb-group

[tcpout:default-autolb-group]
server = yourindexer:9997
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;HR /&gt;

&lt;P&gt;&lt;STRONG&gt;Splunk Indexer or Search Head&lt;/STRONG&gt; &lt;/P&gt;

&lt;P&gt;Define an app name, for example "APP-SNMP" and then create two sub-folders default and metadata.&lt;/P&gt;

&lt;P&gt;If your Splunk indexer is located in the same Windows instance as your snmp traps log file, just place the inputs.conf file together with the &lt;STRONG&gt;props.conf&lt;/STRONG&gt; file within this app and discard the &lt;STRONG&gt;outputs.conf&lt;/STRONG&gt; file step.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;APP-SNMP&lt;/STRONG&gt; &amp;gt; default &amp;gt;props.conf&lt;/P&gt;

&lt;P&gt;These parameters are examples of best practices for line breaking, and search optimization , you will have to tweak them according to your snmp trap logs timestamp format and location within log. Read about this in Splunk Docs, you don't have to do it, but its good to know it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[snmptraps]

# Accurarte line breaking steps 

TIME_FORMAT              = %b %d %H:%M:%S %Z%z %Y 
TIME_PREFIX              = \w+\s\w+\s\d+\s\d+\s\d+:\d+:\d+
LINE_BREAKER             = ([\n\r])\w+\s\w+\s\d+\s\d+\s\d+:\d+:\d+
MAX_TIMESTAMP_LOOKAHEAD  = 25
TRUNCATE                 = 50000

# field extraction

EXTRACT-field_foo       = some regex
EXTRACT-field_bar        = some regex
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;APP-SNMP&lt;/STRONG&gt; &amp;gt; metadata &amp;gt; default.meta&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[]
access = read : [ * ], write : [ admin ]
export = system
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;All the filed extractions should be placed within this app context so you have a better control of it.&lt;/P&gt;

&lt;P&gt;Normally when you do the filed extraction in Splunk GUI, the props.conf will be placed in a local folder of the app context you are standing.&lt;/P&gt;

&lt;P&gt;Commonly search or launcher, so check either:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$SPLUNK_HOME\etc\apps\launcher\local\props.conf
$SPLUNK_HOME\etc\apps\search\local\props.conf
$SPLUNK_HOME\etc\user\**youruser**\search\local\props.conf
$SPLUNK_HOME\etc\user\**youruser**\launcher\local\props.conf
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 18 Oct 2015 17:56:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275557#M52847</guid>
      <dc:creator>santiagoaloi</dc:creator>
      <dc:date>2015-10-18T17:56:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275558#M52848</link>
      <description>&lt;P&gt;This Q&amp;amp;A on &lt;CODE&gt;SNMP&lt;/CODE&gt; is incredible:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/229041/how-to-send-snmp-traps-from-my-linux-machine-to-a.html"&gt;https://answers.splunk.com/answers/229041/how-to-send-snmp-traps-from-my-linux-machine-to-a.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2015 21:37:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275558#M52848</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-10-18T21:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275559#M52849</link>
      <description>&lt;P&gt;Have you taken a look at the Cisco Networks app for Splunk? &lt;A href="https://splunkbase.splunk.com/app/1352/"&gt;https://splunkbase.splunk.com/app/1352/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2015 21:50:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275559#M52849</guid>
      <dc:creator>friea</dc:creator>
      <dc:date>2015-10-18T21:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275560#M52850</link>
      <description>&lt;P&gt;thank you for this reply. this is very helpful!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2015 06:07:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275560#M52850</guid>
      <dc:creator>ledaipro</dc:creator>
      <dc:date>2015-10-19T06:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275561#M52851</link>
      <description>&lt;P&gt;but how to send snmp trap from switch to splunk machine, i have installed net-snmp on splunk machine, and configured snmp on switch &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2015 06:16:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275561#M52851</guid>
      <dc:creator>ledaipro</dc:creator>
      <dc:date>2015-10-19T06:16:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275562#M52852</link>
      <description>&lt;P&gt;Ok , as I understood you are dumping all the SNMP traps into a log file, right? &lt;BR /&gt;
You will have to either monitor that log file, assuming you have installed Splunk Enterprise in the same machine where the file is, or use an Universal Forwarder as I described above, to monitor that file and forward it to the indexer.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2015 13:16:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275562#M52852</guid>
      <dc:creator>santiagoaloi</dc:creator>
      <dc:date>2015-10-19T13:16:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor switch, router... and other Cisco devices using SNMP.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275563#M52853</link>
      <description>&lt;P&gt;I have installed NET-SNMP on splunk machine (winserver 2008 R2). &lt;BR /&gt;
1. splunk machine &lt;BR /&gt;
- edit file C:/usr/ etc/snmp/snmptrapd.conf&lt;BR /&gt;
snmpTrapdAddr 192.168.1.100:162&lt;BR /&gt;
authCommunity log public&lt;BR /&gt;
- Add data -&amp;gt;monitor-&amp;gt; UDP port 162&lt;BR /&gt;
2. Router&lt;BR /&gt;
I configured&lt;BR /&gt;
Router(config)# snmp-server community public ro&lt;BR /&gt;
Router(config)# snmp-server community public rw&lt;BR /&gt;
Router(config)# snmp-server host 192.168.1.100 version 2 public&lt;/P&gt;

&lt;P&gt;But on splunk machine i didn't receive snmp. what did wrong?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2015 13:45:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-switch-router-and-other-Cisco-devices-using-SNMP/m-p/275563#M52853</guid>
      <dc:creator>ledaipro</dc:creator>
      <dc:date>2015-10-19T13:45:28Z</dc:date>
    </item>
  </channel>
</rss>

