<?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: Heavy Forwarders in Active-Active as failover in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Heavy-Forwarders-in-Active-Active-as-failover/m-p/359145#M13267</link>
    <description>&lt;P&gt;Hi pranitprakash,&lt;BR /&gt;
if you configure your Universal Forwarders in AutoLoadBalancing (&lt;A href="https://docs.splunk.com/Documentation/Forwarder/6.6.1/Forwarder/Configureloadbalancing"&gt;https://docs.splunk.com/Documentation/Forwarder/6.6.1/Forwarder/Configureloadbalancing&lt;/A&gt;), they send logs to all the available Heavy Forwarders using a round robin algorithm.&lt;BR /&gt;
When only one Heavy Forwarder is available, UFs send logs the the only available HF.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2017 14:37:25 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2017-06-20T14:37:25Z</dc:date>
    <item>
      <title>Heavy Forwarders in Active-Active as failover</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Heavy-Forwarders-in-Active-Active-as-failover/m-p/359144#M13266</link>
      <description>&lt;P&gt;In one DC scenario, I am going to put two HFs in active-active mode and update Output.conf on Universal Forwarders (~ 200 in count) to send logs to these. &lt;BR /&gt;
I understand that from Splunk URLs that these can be configured to get logs every 30 seconds one by one using autoLBFrequency. What will happen in case one of these HF is down? Will the second HF continue to receive all the TCP connections from UFs and keep forwarding to next level of receivers? &lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2017 12:35:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Heavy-Forwarders-in-Active-Active-as-failover/m-p/359144#M13266</guid>
      <dc:creator>pranitprakash</dc:creator>
      <dc:date>2017-06-20T12:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: Heavy Forwarders in Active-Active as failover</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Heavy-Forwarders-in-Active-Active-as-failover/m-p/359145#M13267</link>
      <description>&lt;P&gt;Hi pranitprakash,&lt;BR /&gt;
if you configure your Universal Forwarders in AutoLoadBalancing (&lt;A href="https://docs.splunk.com/Documentation/Forwarder/6.6.1/Forwarder/Configureloadbalancing"&gt;https://docs.splunk.com/Documentation/Forwarder/6.6.1/Forwarder/Configureloadbalancing&lt;/A&gt;), they send logs to all the available Heavy Forwarders using a round robin algorithm.&lt;BR /&gt;
When only one Heavy Forwarder is available, UFs send logs the the only available HF.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2017 14:37:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Heavy-Forwarders-in-Active-Active-as-failover/m-p/359145#M13267</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-06-20T14:37:25Z</dc:date>
    </item>
  </channel>
</rss>

