troubleshooting Question

Keeps getting Critical errors for Microsoft-Windows-FailoverClustering and Failover cluster cannot failover automatically.

Avatar of Maricel Lepana
Maricel Lepana asked on
Microsoft SQL Server 2008Windows Server 2008
10 Comments1 Solution703 ViewsLast Modified:
I'm having a mysterious problem with my Failover cluster,

Cluster name: SQLCluster01.domain.com
 Members: SQLServer01.domain.com andSQLServer02.domain.com

in the Failover Cluster Management – Cluster Event I received the Critical error message 1135 and 1177:

Log Name: System
 Source: Microsoft-Windows-FailoverClustering
 Date: 15/06/2014 9:07:49 PM
 Event ID: 1177
 Task Category: None
 Level: Critical
 Keywords:
 User: SYSTEM
 Computer: SQLServer01.domain.com
 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.
 Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.


 Log Name: System
 Source: Microsoft-Windows-FailoverClustering
 Date: 15/06/2014 9:07:28 PM
 Event ID: 1135
 Task Category: None
 Level: Critical
 Keywords:
 User: SYSTEM
 Computer: SQLServer01.domain.com
 Description:
 Cluster node 'SQLServer02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

After further investigation, I found some interesting error here, from the very first critical error message logged in the Event viewer on SQLServer02:


 Log Name: System
 Source: Tcpip
 Date: 15/06/2014 9:07:29 PM
 Event ID: 4199
 Task Category: None
 Level: Error
 Keywords: Classic
 User: N/A
 Computer: SQLServer02-VM.domain.com
 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. Network operations on this system may be disrupted as a result.

Any help would be greatly appreciated.
ASKER CERTIFIED SOLUTION
James
Senior Cloud Infrastructure Engineer

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 10 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 10 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros