Monitoring Splunk

Search Peer unreachable

gitau_gm
Explorer

How do I resolve authentication or pass4SymmKey mismatch between search head and peer?
Also getting a situation where 0 clients phone home.

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

That's two different things.

To resolve a pass4SymmKey mismatch, update the plain-text pass4SymmKey value in server.conf and restart the Splunk instance.  Splunk will encrypt the value when it restarts.  Repeat for each SH and peer.  Do NOT copy an encrypted pass4SymmKey from another Splunk instance.

Peers do not phone home so you must be referring to forwarders contacting the Deployment Server (DS).  Ensure all clients have the correct DS info in deploymentclient.conf and that the network permits connections from each client to the DS.

With more information about the problem(s) we can be more specific about the solution(s).

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

That's two different things.

To resolve a pass4SymmKey mismatch, update the plain-text pass4SymmKey value in server.conf and restart the Splunk instance.  Splunk will encrypt the value when it restarts.  Repeat for each SH and peer.  Do NOT copy an encrypted pass4SymmKey from another Splunk instance.

Peers do not phone home so you must be referring to forwarders contacting the Deployment Server (DS).  Ensure all clients have the correct DS info in deploymentclient.conf and that the network permits connections from each client to the DS.

With more information about the problem(s) we can be more specific about the solution(s).

---
If this reply helps you, Karma would be appreciated.
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...