<?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: search header cluster in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/687797#M28192</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Did you check&amp;nbsp;&lt;SPAN&gt;sslVersions in authentication.conf and server.conf?&lt;BR /&gt;Check that the SSL version is consistent among cluster members.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 16 May 2024 22:26:33 GMT</pubDate>
    <dc:creator>sigma</dc:creator>
    <dc:date>2024-05-16T22:26:33Z</dc:date>
    <item>
      <title>search header cluster</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/686494#M28157</link>
      <description>&lt;P&gt;I deployed the search header cluster and also deployed the indexer cluster, and merged the search header cluster and the indexer cluster. After downloading the sample data and uploading it to the indexer, all members of the indexer cluster can search for the uploaded data. When searching for members in the header cluster, there are two that cannot be searched for the uploaded data, and one that can be searched. "Unable to distribute to peer named 192.168.44.159 at uri=192.168.44.159:8089 using the uri scheme=https because peer has status=Down. Verify uri scheme, connectivity to the search peer, that the search peer is up, and that an equivalent level of system resources are available. See the Troubleshooting Manual for more information."&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 05:12:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/686494#M28157</guid>
      <dc:creator>wangyu</dc:creator>
      <dc:date>2024-05-06T05:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: search header cluster</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/686496#M28158</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/267610"&gt;@wangyu&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;did you followed the instructions at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/Indexer/Clusterdeploymentoverview" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.2.1/Indexer/Clusterdeploymentoverview&lt;/A&gt;&amp;nbsp;and&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.2.1/DistSearch/SHCdeploymentoverview" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.2.1/DistSearch/SHCdeploymentoverview&lt;/A&gt;&amp;nbsp;?&lt;/P&gt;&lt;P&gt;I suppose that you checked the connections between the members al the required ports:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;IDX replication: by default 9100,&lt;/LI&gt;&lt;LI&gt;SHC replication 9200,&lt;/LI&gt;&lt;LI&gt;connection between IDXs and Cluster Manager 8089,&lt;/LI&gt;&lt;LI&gt;connection between SHs and Deployer 8089,&lt;/LI&gt;&lt;LI&gt;connection between SHs and IDXs 8089.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Then, how many SHs do you have in your SHC? they must be at least 3.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 05:27:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/686496#M28158</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-05-06T05:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: search header cluster</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/686520#M28159</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Have you done this on all SHC members?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Configure each search head cluster member as a search head on the indexer cluster. Use the CLI splunk edit cluster-config command. For example:&lt;/LI-CODE&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/SHCandindexercluster" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/SHCandindexercluster&lt;/A&gt;&lt;/P&gt;&lt;P&gt;One correction for those default ports. There is no default ports (or alt least earlier haven't been) for IDX replication or SHC replication. There are some commonly used ports, those are not default, you must always define those manually in CLI, conf files or in GUI!&lt;/P&gt;&lt;P&gt;r. Ismo&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2024 07:39:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/686520#M28159</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-05-06T07:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: search header cluster</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/687797#M28192</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Did you check&amp;nbsp;&lt;SPAN&gt;sslVersions in authentication.conf and server.conf?&lt;BR /&gt;Check that the SSL version is consistent among cluster members.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2024 22:26:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/search-header-cluster/m-p/687797#M28192</guid>
      <dc:creator>sigma</dc:creator>
      <dc:date>2024-05-16T22:26:33Z</dc:date>
    </item>
  </channel>
</rss>

