Sql failover cluster node2 down

Question

The node2 on the failover cluster manager status show “down”.
Event Viewer show error Event ID 1653 & 5398 while the node2 critical event on the failover cluster manager show1653 and 1573.

Done ping test from node2 server to node1 with replied as in the connection is reachable.

So i can’t figure out what is wrong.

Please advise me on what i should do.

Answer 1

I can see Event ID 1573 which says

Event 1573: SERVICE_FORM_WITNESS_FAILED
Node '%1' failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available.

Can you tell me your SQL FCI configuration and how is witness configures. How many nodes you have and what is quorum configured. It seems like due to lack of quorum, because witness was not reachable, the WSFC has come down. If you can give me full details I might be able to help you better. Is cluster network up ? You can check that in cluster GUI

Answer 2

We have 2 nodes in the cluster
The witness is quorum disk . It was configure by my predecessor’ how to find this info from the failover cluster management.
At the cluster core resources -> quorum disk show 4.91 go free of 4.97 gb

Answer 3

Hey,

Check if Cluster Service is running. The Cluster service is the essential software component that controls all aspects of failover cluster operation and manages the cluster configuration database. If the Cluster service fails to start on a failover cluster node, the node cannot function as part of the cluster.

Open Event Viewer and view events related to failover clustering. I would recommend you to identify where is the quorum disk is located to make troubleshooting easier in the future.

If you need to configure new Witness follow the preocedures described via following links:
https://learn.microsoft.com/en-us/windows-server/failover-clustering/manage-cluster-quorum

https://learn.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness

FYI, you can deploy Disk Witness using StarWind VSAN free. The following guide will help you:
https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Answer 4

Hi,

Event 1653 Cluster node failed to join the cluster, event 1573 failed to form a cluster.

I would like to check how many nodes in the cluster? Is the cluster running well before? What is the cluster status now, is the cluster running?

If the Cluster is down, we may try to force the cluster to start on one of the nodes, then please check if the network connection between the node and other cluster nodes and the witness.

If it is a sudden issue, it is recommended to check if there's any network issue of the cluster.

Thanks for your time!
Best Regards,
Anne

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 5

Hi Annie,

There are only 2 node in the cluster, bother are physical.
The cluster is failover cluster and both node are seen inside. node1 is running active while node2 is down.
Yes cluster is running otherwise i couldn't open the failover cluster manager and seeing the 2 node inside.

I can ping node1 from node2 IP add on iscsi, heartbeat and production via command prompt but on failover clusterr the node2 network tab shows all 3 is down.

i can ping node2 from node1 IP add on iscsi, heartbeat and production via command prompt.