<?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 enable master node on all indexers ? in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473387#M7311</link>
    <description>&lt;P&gt;This is well documented, but here is the short answer.&lt;/P&gt;

&lt;P&gt;Assuming you have already set a pass4SymmKey in the [clustering] stanza on the master, these are the commands you want to run on each of the indexers/peers:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; /opt/splunk/bin/splunk edit cluster-config -mode slave -master_uri &lt;A href="https://xx.xxx.xx.xxx:8089" target="test_blank"&gt;https://xx.xxx.xx.xxx:8089&lt;/A&gt; -replication_port 9887 -secret your_key_here

/opt/splunk/bin/splunk restart
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Obviously substituting in your master's IP and pass4SymmKey value (in plain text, not the hashed version).&lt;/P&gt;

&lt;P&gt;However, I don't personally like this method as it leaved behind the secret in the command history. It's more secure to update server.conf and cycle Splunk, but you asked specifically about the CLI method.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/ConfigurepeerswithCLI"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/ConfigurepeerswithCLI&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Apr 2020 15:37:59 GMT</pubDate>
    <dc:creator>codebuilder</dc:creator>
    <dc:date>2020-04-17T15:37:59Z</dc:date>
    <item>
      <title>How to enable master node on all indexers ?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473386#M7310</link>
      <description>&lt;P&gt;Hi All ,&lt;/P&gt;

&lt;P&gt;I am working in cluster environment with 16 prod indexers, and one separate  cluster master node.&lt;/P&gt;

&lt;P&gt;if I run /opt/splunk/bin/splunk list cluster-peers&lt;/P&gt;

&lt;P&gt;if i run  the above command in master node command prompt which showing all indexers in the cluster but if run same command on any of the indexers showing master node not enabled. &lt;BR /&gt;
how to enable master node on each indexer .  this case came while synch or pairing  indexer with master node.&lt;/P&gt;

&lt;P&gt;How to enable master node on all indexers with command line prompt.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 12:44:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473386#M7310</guid>
      <dc:creator>90509</dc:creator>
      <dc:date>2020-04-16T12:44:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable master node on all indexers ?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473387#M7311</link>
      <description>&lt;P&gt;This is well documented, but here is the short answer.&lt;/P&gt;

&lt;P&gt;Assuming you have already set a pass4SymmKey in the [clustering] stanza on the master, these are the commands you want to run on each of the indexers/peers:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; /opt/splunk/bin/splunk edit cluster-config -mode slave -master_uri &lt;A href="https://xx.xxx.xx.xxx:8089" target="test_blank"&gt;https://xx.xxx.xx.xxx:8089&lt;/A&gt; -replication_port 9887 -secret your_key_here

/opt/splunk/bin/splunk restart
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Obviously substituting in your master's IP and pass4SymmKey value (in plain text, not the hashed version).&lt;/P&gt;

&lt;P&gt;However, I don't personally like this method as it leaved behind the secret in the command history. It's more secure to update server.conf and cycle Splunk, but you asked specifically about the CLI method.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/ConfigurepeerswithCLI"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/ConfigurepeerswithCLI&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2020 15:37:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473387#M7311</guid>
      <dc:creator>codebuilder</dc:creator>
      <dc:date>2020-04-17T15:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable master node on all indexers ?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473388#M7312</link>
      <description>&lt;P&gt;could you please let me know the reason why it happened . all are in cluster environment with master node if we check from master node to all indexers are in state &lt;STRONG&gt;UP&lt;/STRONG&gt; condition but if we check from indexer master node not enabled why this was coming .&lt;/P&gt;

&lt;P&gt;one more question i would like to ask , if we ping from master node to indexer the data packets are sending but we check from indexer to master node showing "unknown host"  ,  is it bidirectional or single direction....&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 11:02:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473388#M7312</guid>
      <dc:creator>90509</dc:creator>
      <dc:date>2020-04-18T11:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable master node on all indexers ?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473389#M7313</link>
      <description>&lt;P&gt;If the master shows all peers are "up" then your cluster is healthy.&lt;/P&gt;

&lt;P&gt;Running "/opt/splunk/bin/splunk list cluster-peers" is &lt;STRONG&gt;only&lt;/STRONG&gt; valid from the master, it is not run on the peers.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 16:21:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-enable-master-node-on-all-indexers/m-p/473389#M7313</guid>
      <dc:creator>codebuilder</dc:creator>
      <dc:date>2020-04-18T16:21:04Z</dc:date>
    </item>
  </channel>
</rss>

