<?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: ANYCAST redundancy with syslog in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59576#M11752</link>
    <description>&lt;P&gt;Yes, using Quagga + ospfd. Logs get sent to an anycast syslog server IP, which routes to an actual syslog server, which has the Splunk forwarder running on it.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Apr 2012 15:31:05 GMT</pubDate>
    <dc:creator>kogane</dc:creator>
    <dc:date>2012-04-12T15:31:05Z</dc:date>
    <item>
      <title>ANYCAST redundancy with syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59575#M11751</link>
      <description>&lt;P&gt;Is anyone using Anycast technology to provide syslog redundancy for the forwarders?  Anycast idea much like that used for DNS...&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2012 16:01:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59575#M11751</guid>
      <dc:creator>sladei</dc:creator>
      <dc:date>2012-01-27T16:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: ANYCAST redundancy with syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59576#M11752</link>
      <description>&lt;P&gt;Yes, using Quagga + ospfd. Logs get sent to an anycast syslog server IP, which routes to an actual syslog server, which has the Splunk forwarder running on it.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Apr 2012 15:31:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59576#M11752</guid>
      <dc:creator>kogane</dc:creator>
      <dc:date>2012-04-12T15:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: ANYCAST redundancy with syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59577#M11753</link>
      <description>&lt;P&gt;Kogane, could you please elaborate a little on your post? I'm aware Quagga is a fork of Zebra, how did you config syslog to forward to anycast?&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2012 16:56:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59577#M11753</guid>
      <dc:creator>eegilbert</dc:creator>
      <dc:date>2012-05-18T16:56:57Z</dc:date>
    </item>
    <item>
      <title>Re: ANYCAST redundancy with syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59578#M11754</link>
      <description>&lt;P&gt;We just have syslog on our hosts configured to send data to "sysloghost", which resolves to an anycast IP. The actual syslog servers are the ones running quagga/ospfd.&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2012 16:59:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59578#M11754</guid>
      <dc:creator>kogane</dc:creator>
      <dc:date>2012-05-18T16:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: ANYCAST redundancy with syslog</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59579#M11755</link>
      <description>&lt;P&gt;Gotcha, I think I know where to go with this now, thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2012 17:08:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ANYCAST-redundancy-with-syslog/m-p/59579#M11755</guid>
      <dc:creator>eegilbert</dc:creator>
      <dc:date>2012-05-18T17:08:33Z</dc:date>
    </item>
  </channel>
</rss>

