Installation

Splunk Daemon Not Responding After Restart, NIC Teaming

JohnEGones
Path Finder

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
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...