<?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: Splunk License Master and Heavy Forwarder communicate in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302271#M19279</link>
    <description>&lt;P&gt;Not sure on the license front, but TCP/8089 is used for more than Licensing.&lt;/P&gt;

&lt;P&gt;This includes deployment client, distributed management console etc.  If you have more than just licensing on the host serving that function, you have clear justification to request that port being opened as splunk uses TCP/8089 for all of those features.&lt;/P&gt;</description>
    <pubDate>Fri, 19 May 2017 19:59:05 GMT</pubDate>
    <dc:creator>dsctm3</dc:creator>
    <dc:date>2017-05-19T19:59:05Z</dc:date>
    <item>
      <title>Splunk License Master and Heavy Forwarder communicate</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302270#M19278</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;does anyone know if there is any communication between License Master and Heavy Forwarder initiated by the License Master. I know that Heavy Forwarder initiate some communication with License Master to download license information. I also found that indexers are reporting every minute an amount if indexed data to License Master. However I have not found any official Splunk explanation what communications exist and how the components exactly talk together.&lt;/P&gt;

&lt;P&gt;There is a simple reason for this question ... our firewall guys are complaining to open tcp/8089 initiated from License Master to Heavy Forwarders.&lt;/P&gt;

&lt;P&gt;Thanks to anyone for an answer.&lt;/P&gt;

&lt;P&gt;Best Regards,&lt;BR /&gt;
Ales&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2017 07:30:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302270#M19278</guid>
      <dc:creator>AlesFrohlich</dc:creator>
      <dc:date>2017-05-18T07:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Master and Heavy Forwarder communicate</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302271#M19279</link>
      <description>&lt;P&gt;Not sure on the license front, but TCP/8089 is used for more than Licensing.&lt;/P&gt;

&lt;P&gt;This includes deployment client, distributed management console etc.  If you have more than just licensing on the host serving that function, you have clear justification to request that port being opened as splunk uses TCP/8089 for all of those features.&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2017 19:59:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302271#M19279</guid>
      <dc:creator>dsctm3</dc:creator>
      <dc:date>2017-05-19T19:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Master and Heavy Forwarder communicate</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302272#M19280</link>
      <description>&lt;P&gt;AFAIK, The slaves report their license usage to License Master and there is no communication happens from LM to L slaves.&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2017 21:02:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302272#M19280</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-05-19T21:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Master and Heavy Forwarder communicate</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302273#M19281</link>
      <description>&lt;P&gt;Thank you for your replies. The server is only license master. So the one way communications should be enough.&lt;/P&gt;

&lt;P&gt;Thanks a lot from help.&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Ales&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2017 06:42:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-License-Master-and-Heavy-Forwarder-communicate/m-p/302273#M19281</guid>
      <dc:creator>AlesFrohlich</dc:creator>
      <dc:date>2017-05-22T06:42:24Z</dc:date>
    </item>
  </channel>
</rss>

