<?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: Ingesting Logs from Cisco Routing and Switching Gear in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568828#M100929</link>
    <description>&lt;P&gt;&amp;gt; So in short - your company is trying to make you move a 5 ton steel beam giving you only a Mazda MX-5. Sorry, it won't fly however strongly you wish for it.&lt;/P&gt;&lt;P&gt;Thank you for saying that. It doesn't help but it DOES make me feel better. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Sep 2021 19:24:09 GMT</pubDate>
    <dc:creator>603_Dan</dc:creator>
    <dc:date>2021-09-28T19:24:09Z</dc:date>
    <item>
      <title>Ingesting Logs from Cisco Routing and Switching Gear</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568801#M100926</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've been asked to add inputs to my organization's Splunk Enterprise from Cisco Routing and Switching Gear. I remember reading in the documentation that Splunk's recommended best practice in is to use a syslog-collector running a UF or HF between the Routers/Switches and Indexers to keep the Indexers from becoming flooded with incoming traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had thought to do this with a Linux machine running a UF or HF and ingesting Router/Switch log traffic before forwarding the traffic along to Splunk Enterprise but I've been told an additional machine, even a virtual one, is a no go. I don't believe a Windows syslog-collector would work either as Windows can't do this with native tools, and I've been told 3rd party software is also a no-go.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could anyone recommend a solution that doesn't use a Linux syslog-collector, a Windows syslog-collector running 3rd party software,&amp;nbsp; that meets Splunk's best practice suggestions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;603_Dan&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Sep 2021 16:47:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568801#M100926</guid>
      <dc:creator>603_Dan</dc:creator>
      <dc:date>2021-09-28T16:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting Logs from Cisco Routing and Switching Gear</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568808#M100927</link>
      <description>&lt;P&gt;Sorry, but if someone wants to receive syslog events (most probably UDP ones) and isn't prepare to create additional component needed to process this trafic... well, then we can't do much.&lt;/P&gt;&lt;P&gt;Yes, splunk can listen on TCP or UDP port for incoming syslog events but it's not a solution advised for production use. Furthermore, I assume that your company is running an all-in-one installation. Processing all input data along with all the other splunk server activity is not a very good idea (again - especially if you're going to be dealing with UDP events which are prone to getting lost).&lt;/P&gt;&lt;P&gt;So in short - your company is trying to make you move a 5 ton steel beam giving you only a Mazda MX-5. Sorry, it won't fly however strongly you wish for it.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Sep 2021 17:06:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568808#M100927</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2021-09-28T17:06:18Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting Logs from Cisco Routing and Switching Gear</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568828#M100929</link>
      <description>&lt;P&gt;&amp;gt; So in short - your company is trying to make you move a 5 ton steel beam giving you only a Mazda MX-5. Sorry, it won't fly however strongly you wish for it.&lt;/P&gt;&lt;P&gt;Thank you for saying that. It doesn't help but it DOES make me feel better. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Sep 2021 19:24:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-Logs-from-Cisco-Routing-and-Switching-Gear/m-p/568828#M100929</guid>
      <dc:creator>603_Dan</dc:creator>
      <dc:date>2021-09-28T19:24:09Z</dc:date>
    </item>
  </channel>
</rss>

