Deployment Architecture

Why does our distributed management console see one search head cluster member with a GUID label instead of the shcluster_label?

deejay1
Explorer

I have set the shcluster_label on the search head cluster members after deployment. The label is also set on the deployer. Unfortunately, the distributed management console sees two cluster members with the proper label and one member with a GUID label.

I tried to reinstall the member (after removing it according to http://docs.splunk.com/Documentation/Splunk/6.2.0/DistSearch/Removeaclustermember) but to no avail 😞

This seems to mess with the "Search Head Clustering: Status and Configuration" page, even though all 3 hosts are listed under "Snapshots" only two of them are visible on "Historical Charts" and when I switch to the GUID named cluster only the missing one is visible...

Any hints on how to fix this?

0 Karma
1 Solution

deejay1
Explorer

OK, I edited $SPLUNK_HOME/etc/system/local/distsearch.conf, moving the problematic search head from the GUID group to the labelled group and also removed it's mention from $SPLUNK_HOME/etc/apps/splunk_management_console/local/splunk_management_console_assets.conf
This seems to have fixed the problem

View solution in original post

0 Karma

deejay1
Explorer

OK, I edited $SPLUNK_HOME/etc/system/local/distsearch.conf, moving the problematic search head from the GUID group to the labelled group and also removed it's mention from $SPLUNK_HOME/etc/apps/splunk_management_console/local/splunk_management_console_assets.conf
This seems to have fixed the problem

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...