<?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: Required network openings for a distributed Splunk setup in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524157#M18054</link>
    <description>Hi&lt;BR /&gt;here is diagram how nodes are connected together and which node is active on which connection.&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.6/InheritedDeployment/Ports" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.6/InheritedDeployment/Ports&lt;/A&gt;&lt;BR /&gt;r. Ismo</description>
    <pubDate>Mon, 12 Oct 2020 05:41:02 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2020-10-12T05:41:02Z</dc:date>
    <item>
      <title>Required network openings for a distributed Splunk setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524143#M18051</link>
      <description>&lt;P&gt;I apologize if the title isn't very descriptive of the question I have, was not sure how to best frame it.&lt;/P&gt;&lt;P&gt;For a setup with numerous splunkforwarders forwarding to two indexing servers, and getting inputs/outputs from a deployment server, how is the network flow?&lt;/P&gt;&lt;P&gt;splunkforwarder -&amp;gt; splunk-index1/2 - is this forwarder-initiated?&lt;BR /&gt;splunk-master (deployment+cluster master) -&amp;gt; splunkforwarder - master or forwarder initiated for deployment of config/splunkd restarts?&lt;/P&gt;&lt;P&gt;I believe I found some information on this at some point, but that was for an older version and possibly outdated.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 04:37:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524143#M18051</guid>
      <dc:creator>mart10</dc:creator>
      <dc:date>2020-10-12T04:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Required network openings for a distributed Splunk setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524150#M18053</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/224287"&gt;@mart10&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;splunk-master (deployment+cluster master) -&amp;gt; splunkforwarder - master or forwarder initiated for deployment of config/splunkd restarts? ///&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;on Deployment server, when you make changes (to inputs.conf, etc), the changes will be sent to universal forwarders -&amp;nbsp;In some cases, it deploys apps automatically. In other cases, you need to manually initiate the deployment.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.6/Updating/Updateconfigurations" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.6/Updating/Updateconfigurations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The phone home interval (that is, how frequently each client checks in with the deployment server for updates)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.6/Updating/Calculatedeploymentserverperformance" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.6/Updating/Calculatedeploymentserverperformance&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;phoneHomeIntervalInSecs = &amp;lt;number in seconds&amp;gt;
* Determines how frequently, in seconds, this deployment client should
  check for new content.
* Fractional seconds are allowed.
* Default: 60.&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Deploymentclientconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Deploymentclientconf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 05:07:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524150#M18053</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2020-10-12T05:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: Required network openings for a distributed Splunk setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524157#M18054</link>
      <description>Hi&lt;BR /&gt;here is diagram how nodes are connected together and which node is active on which connection.&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.6/InheritedDeployment/Ports" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.6/InheritedDeployment/Ports&lt;/A&gt;&lt;BR /&gt;r. Ismo</description>
      <pubDate>Mon, 12 Oct 2020 05:41:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524157#M18054</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-10-12T05:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: Required network openings for a distributed Splunk setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524165#M18055</link>
      <description>&lt;P&gt;Thanks, just so I am sure I properly understand this:&lt;/P&gt;&lt;P&gt;splunkforwarder -&amp;gt; indexers # this is forwarder-polling/initiated on port 9997.&lt;BR /&gt;splunkforwarder -&amp;gt; deployment # this is also forwarder-polling/initiated, port 8089.&lt;BR /&gt;&lt;SPAN&gt;indexer/deployment/head -&amp;gt; license server # this is&amp;nbsp;indexer/deployment/head-polling on port 8089.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So overall, splunkforwarders initiates every connection to their mothership. And splunk servers initiates connections to the license server.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2020 06:15:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524165#M18055</guid>
      <dc:creator>mart10</dc:creator>
      <dc:date>2020-10-12T06:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: Required network openings for a distributed Splunk setup</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524187#M18056</link>
      <description>Yes, those are correct.</description>
      <pubDate>Mon, 12 Oct 2020 08:11:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Required-network-openings-for-a-distributed-Splunk-setup/m-p/524187#M18056</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-10-12T08:11:49Z</dc:date>
    </item>
  </channel>
</rss>

