Installation

Splunk Daemon Not Responding After Restart, NIC Teaming

JohnEGones
Communicator

Hi Community,

Just a quick question to see if this is an issue that anyone else has experienced, do you have problems with the Splunk daemon not communicating properly with the other members of a cluster and deployment because of a NIC teaming issue?

Our Splunk (Windows) hosts have servers with dual NIC cards, for whatever reason, in an active-active configuration Splunk does not know how to communicate. The underlying host is up and functional, and the local instance of splunkd appears to be running, but communicating between nodes is nil until the teaming is moved to active-standby or one of the NICs is disabled.

Labels (2)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...