This is the error message I get on my replica when there is a connection timeout for few seconds with the Primary. Can anyone tell me whats going on and why are the available storage being moved as this is an AAG where storage is not supposed to be shared and also here there is no failover its just the secondary replica missed heartbeats. Thanks
The failover error logs are mentioned below starting from the bottom
Cluster network 'Cluster Network 2' is operational (up). All available failover cluster nodes attached to the network can communicate using it.
Joiner tried to Create Security Context using Package='Kerberos/NTLM' with Context Requirement ='0' and Timeout ='40000' for the target = 'xxxxxx01'
The Cluster service successfully brought the clustered role 'Available Storage' offline.
Clustered role 'Available Storage' is moving to cluster node 'xxxx'.
Cluster has lost the UDP connection from local endpoint xxx.xx.xx.21:~xx43~ connected to remote endpoint xxx.xx.xx.20:~xx43~.
Cluster has missed two consecutive heartbeats for the local endpoint xxx.xx.xx.21:~xx43~ connected to remote endpoint xxx.xx.xx.20:~xx43~.
Best Answer
The only group that failed over was the Available Storage group, which you aren't using, so it is something you can just ignore. If you want to increase the number of missed heartbeats that will cause it to fail over, change the SameSubnetThreshold accordingly.
See Clustering and High-Availability for details.