Troubleshooting Three Node WSFC Cluster

Shivkumar Mallesappa 21 Reputation points
2021-10-04T07:06:49.257+00:00

I am trying to build a three node WSFC Cluster, I will be implementing SQL Always On Failover Cluster Instances into this Cluster once it is successfully configured.
I am totally new to this Windows WSFC technology.
I have performed the following steps in my AWS account to Setup the Cluster.

  • Created Managed AD
  • Launched 3 Windows SQL Server Instances with AD Configuration (2 Instances are launched in one AZ and 1 Instance is launched in another)
  • Added the Instances to AD using SSM
  • Added secondary IP to the instances
  • Installed FCI Features using Server Manager on all of the three nodes
  • Checked Validation Configuration
  • Created Cluster

My Queries:

  • In my Cluster Summary I am able to see only two nodes under Cluster Core Resources. I was excepting three nodes. Is this my understanding correct?
  • The overall Cluster status is online, but when I try to bring one of the other Node online, it gives me error
    "Error Code: 0x80071397" The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group." What does this mean?
  • On my Three Nodes I can see the error: Cluster resource 'Cluster Name' of type 'Network Name' in clustered role 'Cluster Group' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. What does this mean and how to resolve it? This is something which I am not able to understand.
  • I am also getting the following warning : No matching network interface found for resource 'Cluster IP Address' IP address '10.85.239.XXX' (return code was '5035'). If your cluster nodes span different subnets, this may be normal. Will this impact my Cluster?
  • Will I need Quorum and Witness configurations in this setup? I will be using AWS FSx as a shared storage for this Cluster, so I am bit confused about Witness/Quorum/File Share Witness etc. It will be great if someone could also throw some light on this as well.
  • Overall my setup is correct or there is something which I misconfigured or missed?

Please refer to the attached screenshots for the overall infra setup:

Overview
Node Details
Warning
Error
Node Bring Up Error

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,121 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
957 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,351 Reputation points
    2021-10-07T09:17:17.827+00:00

    Hello @Shivkumar Mallesappa ,

    Thank you for your question.

    After manually bringing down a cluster or after a cluster fails, a group and all of its resources can fail if the cluster experiences a loss of a node. However, the group can also go into an offline state.

    Access the article below to see possible scenarios of this happening and how to resolve it:

    https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/error-messages-bring-cluster-group-online

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

    If the answer is helpful, please vote positively and accept as an answer.

    0 comments