<?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 do I get data from my Cisco switch into Splunk? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-get-data-from-my-Cisco-switch-into-Splunk/m-p/206399#M40720</link>
    <description>&lt;P&gt;The best practice is to use a syslog aggregation tier and then use the Universal Forwarder on top of your syslog server(s). This gives you the most reliability, auto-load balances the data if you have a distributed setup and will not cause data loss if you need to re-start your Splunk infrastructure. I highly recommend you go this route.&lt;/P&gt;

&lt;P&gt;If you don't have syslog servers then you can syslog directly to Splunk.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/Monitornetworkports"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/Monitornetworkports&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/HowSplunkEnterprisehandlessyslogdata"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/HowSplunkEnterprisehandlessyslogdata&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jun 2016 16:28:49 GMT</pubDate>
    <dc:creator>shaskell_splunk</dc:creator>
    <dc:date>2016-06-10T16:28:49Z</dc:date>
    <item>
      <title>How do I get data from my Cisco switch into Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-get-data-from-my-Cisco-switch-into-Splunk/m-p/206398#M40719</link>
      <description>&lt;P&gt;I am new to Splunk. I have set it up on my server, set up an indexer, and set up the logging in my switch, but I have no data.  I do not see the option for Cisco:ios.  How do you install the technology plugin?  &lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2016 13:58:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-get-data-from-my-Cisco-switch-into-Splunk/m-p/206398#M40719</guid>
      <dc:creator>jasonpoth</dc:creator>
      <dc:date>2016-06-10T13:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: How do I get data from my Cisco switch into Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-get-data-from-my-Cisco-switch-into-Splunk/m-p/206399#M40720</link>
      <description>&lt;P&gt;The best practice is to use a syslog aggregation tier and then use the Universal Forwarder on top of your syslog server(s). This gives you the most reliability, auto-load balances the data if you have a distributed setup and will not cause data loss if you need to re-start your Splunk infrastructure. I highly recommend you go this route.&lt;/P&gt;

&lt;P&gt;If you don't have syslog servers then you can syslog directly to Splunk.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/Monitornetworkports"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/Monitornetworkports&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/HowSplunkEnterprisehandlessyslogdata"&gt;http://docs.splunk.com/Documentation/Splunk/6.4.1/Data/HowSplunkEnterprisehandlessyslogdata&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2016 16:28:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-get-data-from-my-Cisco-switch-into-Splunk/m-p/206399#M40720</guid>
      <dc:creator>shaskell_splunk</dc:creator>
      <dc:date>2016-06-10T16:28:49Z</dc:date>
    </item>
  </channel>
</rss>

