https://community.splunk.com/t5/Installation/Splunk-Daemon-Not-Responding-After-Restart-NIC-Teaming/m-p/677552#M13645 <P>Hi Community,</P><P>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?<BR /><BR />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.</P> Wed, 14 Feb 2024 12:42:16 GMT JohnEGones 2024-02-14T12:42:16Z https://community.splunk.com/t5/Installation/Splunk-Daemon-Not-Responding-After-Restart-NIC-Teaming/m-p/677552#M13645 <P>Hi Community,</P><P>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?<BR /><BR />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.</P> Wed, 14 Feb 2024 12:42:16 GMT https://community.splunk.com/t5/Installation/Splunk-Daemon-Not-Responding-After-Restart-NIC-Teaming/m-p/677552#M13645 JohnEGones 2024-02-14T12:42:16Z