Cluster Network Status: Unavailable

Question

_{Monday, June 20, 2011 2:43 PM}

Hello

I'm having this issue:

On a 2 node Exchange DAG Cluster, one of networks is on state Unavailable.

node info.

SO: Win 2K8 Ent R2 SP1

there weren't made any changes on any firewall.

from the node, I can reach (ping) the other cluster node and the witness share, but unable to reach the cluster ip address.

how can I change the state of the network

thank you in advance

All replies (1)

_{Monday, June 20, 2011 5:42 PM ✅Answered}

Found the solution in http://blogs.technet.com/b/askcore/archive/2010/06/08/windows-server-2008-and-2008r2-failover-cluster-startup-switches.aspx

"As discussed, we need at least 2 votes to achieve “quorum”. We currently have one node up, so we have one vote. The other node is down and the Witness Disk is unavailable which would account for the other two votes. But you can see that the Cluster Service itself is started. The reason it stays started is that is sitting there just listening for another node to join and give it a majority. Once it does, the Cluster resources will be made available for everyone to use. If you were to run the command to get the state of the nodes, you would see this:

This is where the FORCEQUORUM switch comes into play. When using this, it will force the Cluster to become available even though there is no “quorum”. There are multiple ways of forcing the Cluster Service to start. However, please keep in mind that there are some implications when running this. The implications are explained in this article.

1. Go into Service Control Manager and start the Cluster Service with /FORCEQUORUM (or /FQ)
2. Go to an Administrative Command Prompt and use:
a. net start clussvc /forcequorum
b. net start clussvc /fq
3. In Failover Cluster Management, highlight the name of the Cluster in the left pane, and
on the far right pane in the Actions column, there is a FORCE CLUSTER START option that
you can select shown below.