<?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: How to configure the cluster peers inputs.conf file through the Cluster Master in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/573348#M10576</link>
    <description>&lt;P&gt;I think this may help:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.2/Indexer/Managesinglepeerconfigurations" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.2/Indexer/Managesinglepeerconfigurations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I get what your saying as if you theoretically have 3 Indexer Peers therefore 3 different inputs.conf allowing Splunk SSL receiving.&lt;/P&gt;&lt;P&gt;If it is a small deployment I would manage it on a peer by peer basis and locally configure it in its own app context/repository.&lt;/P&gt;&lt;P&gt;Or use the same cert and password throughout (probably not what you want) and use the deployment server to deploy it as an app&lt;/P&gt;</description>
    <pubDate>Tue, 02 Nov 2021 17:55:29 GMT</pubDate>
    <dc:creator>kjstogn</dc:creator>
    <dc:date>2021-11-02T17:55:29Z</dc:date>
    <item>
      <title>How to configure the cluster peers inputs.conf file through the Cluster Master</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/519445#M3412</link>
      <description>&lt;P&gt;I'm tasked with moving the $SPLUNK_HOME/etc/system/local/ conf files within our peer nodes to their own Splunk apps for easier management using the deployment-server/cluster master method.&lt;BR /&gt;&lt;BR /&gt;Since, we are using third-party SSL certificates to secure log ingestion from the forwarders each peer has their own unique .pem file.&lt;BR /&gt;&lt;BR /&gt;What is the best way to incorporate the inputs.conf file regarding the SSL configs, for all peer nodes within a Splunk app that will be distributed to all peers?&lt;BR /&gt;&lt;BR /&gt;Specifically, I'm referring to the serverCert option, which has a different filename on each peer node. All other config options are the same within the inputs.conf files.&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2020 14:06:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/519445#M3412</guid>
      <dc:creator>mcirrici</dc:creator>
      <dc:date>2020-09-14T14:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure the cluster peers inputs.conf file through the Cluster Master</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/520475#M3488</link>
      <description>&lt;P&gt;search peers ( Indexers participating in Indexer cluster)&amp;nbsp; are always managed by Cluster Master. Configuration will be kept under $SPLUNK_HOME/etc/master-apps&lt;/P&gt;&lt;P&gt;The same configuration needs to be pushed to search peers which are indexers. same configuration will be kept under $SPLUNK_HOME/etc/slave-apps in search peers.&lt;/P&gt;&lt;P&gt;To Move inputs.conf which is in system/local on Indexers:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;create an app "Indexers_inputs" under&amp;nbsp;$SPLUNK_HOME/etc/master-apps on Cluster master&lt;/LI&gt;&lt;LI&gt;create a directory "local" under&amp;nbsp;$SPLUNK_HOME/etc/master-apps/Indexers_inputs on Cluster master&lt;/LI&gt;&lt;LI&gt;move your inputs.conf to&amp;nbsp;$SPLUNK_HOME/etc/master-apps/Indexers_inputs/local&lt;/LI&gt;&lt;LI&gt;Then deploy app to search peers from cluster master using below command&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;$SPLUNK_HOME/bin/splunk apply cluster-bundle&lt;/P&gt;</description>
      <pubDate>Sun, 20 Sep 2020 09:15:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/520475#M3488</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-20T09:15:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure the cluster peers inputs.conf file through the Cluster Master</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/573348#M10576</link>
      <description>&lt;P&gt;I think this may help:&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.2/Indexer/Managesinglepeerconfigurations" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.2/Indexer/Managesinglepeerconfigurations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I get what your saying as if you theoretically have 3 Indexer Peers therefore 3 different inputs.conf allowing Splunk SSL receiving.&lt;/P&gt;&lt;P&gt;If it is a small deployment I would manage it on a peer by peer basis and locally configure it in its own app context/repository.&lt;/P&gt;&lt;P&gt;Or use the same cert and password throughout (probably not what you want) and use the deployment server to deploy it as an app&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 17:55:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-configure-the-cluster-peers-inputs-conf-file-through-the/m-p/573348#M10576</guid>
      <dc:creator>kjstogn</dc:creator>
      <dc:date>2021-11-02T17:55:29Z</dc:date>
    </item>
  </channel>
</rss>

