Regarding the SH configuring for the multisite indexing cluster

[dhana22]

Hello All,

I am getting the message in SH The searchhead is unable to update the peer information. Error = 'Unable to reach the cluster manager' for manager=https://x.x.x.x:8089, SH is trying to connect to the CM that is Standy. We have 2 CM, one of the CM is active and other one is StandBy, below are the configs in CM and SH. Could you please advice if anything is wrong in the config. Thanks!

CM Config -

[clustering]
mode = manager
manager_switchover_mode = auto
manager_uri = clustermanager:dc1,clustermanager:dc2
pass4SymmKey = key
multisite = true
available_sites = site1,site2
site_replication_factor = origin:1,site1:1,site2:1,total:3
site_search_factor = origin:1,site2:1,site1:1,total:3
cluster_label = publisher_cluster
access_logging_for_heartbeats = 0
cm_heartbeat_period = 3
precompress_cluster_bundle = 1
rebalance_threshold = 0.9

[clustermanager:dc1]
manager_uri = https://x.x.x.x:8089

[clustermanager:dc2]
manager_uri = https://x.x.x.x:8089

--

SH Config -

[general]
serverName = x.com
pass4SymmKey = key
site = site2

[clustering]
mode = searchhead
manager_uri = clustermanager:dc1, clustermanager:dc2

[clustermanager:dc1]
multisite = true
manager_uri = https://x.x.x.x:8089
pass4SymmKey = key

[clustermanager:dc2]
multisite = true
manager_uri = https://x.x.x.x:8089
pass4SymmKey = key

[replication_port://9100]

[shclustering]
conf_deploy_fetch_url = https://x.x.x.x:8089
mgmt_uri = https://x.x.x.x:8089
disabled = 0
pass4SymmKey = key
replication_factor = 2
shcluster_label = publisher_shcluster
id = B57109F1-5D63-4FC9-9BFC-BE6B0375D9A7
manual_detention = off

Dhana

[tej57]

Hello @dhana22 ,

For using cluster manager redundancy, I would suggest you to use the load balancer to switch between the active and the standby cluster managers. As per the following document as well, if the manager switch over mode is set to auto, ideally load balancing using a 3rd party load balancer would be the best possible solution to configure the indexer peers and the search heads.

Document link - https://docs.splunk.com/Documentation/Splunk/9.2.1/Indexer/CMredundancy#Configure_peer_nodes.2C_sear...

Thanks,
Tejas.

---

If the above solution helps, an upvote is appreciated.