As you might know, I'm a part of the Microsoft group that supports failover clusters.As a result, I've had to troubleshoot quite a few problems.So I wanted to pass along some of the most common things to look for and where to look to look for them.With that in mind, let’s first talk about the files that you’ll generally be looking at and their descriptions.It’s also a good idea to to validate your cluster when troubleshooting cluster issues. If you do then your cluster is not supported by Microsoft and you'll need to go through each error and resolve it.In the case of an IP-Less DAG, you will see some warnings as below and we’ll go through the Storage and System Configuration warnings.You cannot use the Failover Cluster Manager to connect and manage the cluster because there’s no IP to connect to.Before you go ahead and try it, you also cannot connect to a single node in the cluster either! In both cases, you get this connection error: Cannot connect without an administrative access point You cannot use Failover Cluster Manager to manage a cluster that was created without an administrative access point.
Log Name: System Source: Tcpip Date: 15/06/2011 PM Event ID: 4199 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Print Server02-VM.Description: The system detected an address conflict for IP address 192.168.127.142 with the system having network hardware address 00-50-56-AE-29-23.
Log Name: System Source: Microsoft-Windows-Failover Clustering Date: 15/06/2011 PM Event ID: 1177 Task Category: None Level: Critical Keywords: User: SYSTEM Computer: Print Server01.Description: The Cluster service is shutting down because quorum was lost.
This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. : Microsoft Failover Cluster Virtual Adapter Physical Address.
You must use Windows Power Shell to manage the cluster.
You should validate your DAG cluster nodes before you create the cluster and after any changes that are made to the configuration of the cluster or hardware.