<?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 Configuration for Search Head, Indexer and Fowarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277534#M53222</link>
    <description>&lt;P&gt;I would suggest some homework first.   Have a look at the Distributed Deployment guide, perhaps starting here:  &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Deploy/Implementationoverview"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Deploy/Implementationoverview&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This configuration is a highly common, typical small Splunk configuration.  You:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Disable the web interface on the indexer&lt;/LI&gt;
&lt;LI&gt;Configure the search head to act as a search peer of the indexer&lt;/LI&gt;
&lt;LI&gt;Configure the search head to forward its _internal and other local logs to your indexer&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;This design is well-covered in the Distributed Deployment guide linked above as well as in the Splunk System Administration class.  If you have specific questions about deploying this design, I would suggest a more specific follow-up question (or questions).&lt;/P&gt;</description>
    <pubDate>Sun, 05 Feb 2017 16:09:05 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2017-02-05T16:09:05Z</dc:date>
    <item>
      <title>Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277533#M53221</link>
      <description>&lt;P&gt;I have 3 systems, I want one system to work as Forwarder, one as Indexer and one as Search Head.&lt;BR /&gt;
Setting up forwarder is fine, but to separate indexing and searching.&lt;BR /&gt;
Means on the indexing system searching should not be available and on search system indexing should not be available.&lt;BR /&gt;
How can I achieve this type of configuration?&lt;/P&gt;

&lt;P&gt;Please let me know if you want more details.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2017 13:37:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277533#M53221</guid>
      <dc:creator>gaurav_maniar</dc:creator>
      <dc:date>2017-02-05T13:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277534#M53222</link>
      <description>&lt;P&gt;I would suggest some homework first.   Have a look at the Distributed Deployment guide, perhaps starting here:  &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Deploy/Implementationoverview"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Deploy/Implementationoverview&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This configuration is a highly common, typical small Splunk configuration.  You:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Disable the web interface on the indexer&lt;/LI&gt;
&lt;LI&gt;Configure the search head to act as a search peer of the indexer&lt;/LI&gt;
&lt;LI&gt;Configure the search head to forward its _internal and other local logs to your indexer&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;This design is well-covered in the Distributed Deployment guide linked above as well as in the Splunk System Administration class.  If you have specific questions about deploying this design, I would suggest a more specific follow-up question (or questions).&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2017 16:09:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277534#M53222</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2017-02-05T16:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277535#M53223</link>
      <description>&lt;P&gt;hey @dwaddle thanks for the help. Actually I just completed power user certification and about to start with administration. Just one more query, after setting up the environment as you have mentioned if I link more forwarders to indexer I have to not worry about search head ???&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2017 17:32:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277535#M53223</guid>
      <dc:creator>gaurav_maniar</dc:creator>
      <dc:date>2017-02-05T17:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277536#M53224</link>
      <description>&lt;P&gt;correct.  Search heads don't particularly care about how many forwarders are connected to the indexer.  But, if you are going to add a bunch of forwarders, then you should be looking at adding a deployment server to your design.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2017 21:39:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277536#M53224</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2017-02-05T21:39:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277537#M53225</link>
      <description>&lt;P&gt;Thanks Bro &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2017 04:44:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277537#M53225</guid>
      <dc:creator>gaurav_maniar</dc:creator>
      <dc:date>2017-02-06T04:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277538#M53226</link>
      <description>&lt;P&gt;we should install forwarder on search head?&lt;/P&gt;</description>
      <pubDate>Sat, 09 May 2020 14:26:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/277538#M53226</guid>
      <dc:creator>nasimm</dc:creator>
      <dc:date>2020-05-09T14:26:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Configuration for Search Head, Indexer and Fowarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/526834#M88864</link>
      <description>&lt;P&gt;Does the search head and indexer must be deployed on different separate servers with different ip adresses? And doest it mean that i have to install splunk on those different servers?&lt;/P&gt;&lt;P&gt;What's the problem with having the indexer and searchhead deployed on 1 server?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2020 11:13:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Configuration-for-Search-Head-Indexer-and-Fowarder/m-p/526834#M88864</guid>
      <dc:creator>Simons20</dc:creator>
      <dc:date>2020-10-28T11:13:56Z</dc:date>
    </item>
  </channel>
</rss>

