SQL Cluster Node - Showing as down

Question

SQL Cluster Node - Showing as down

Ben 16

I have a 2 node failover cluster with 2 SQL VM's in. one is showing as down, the services are running however in the cluster manager it says that the networks are down however i can ping them, rdp to them etc etc I've tried rebooting both servers in the cluster and that didnt have an effect. unsure whethger to evict the server and re-add it?

the quorum is online, the cluster IP address pings the sql server in question has all the correct services running and there are a number of errors in the cluster event viewer

Cluster failed to start (5398)
Cluster node failed to join cluster as it could not communicate over the network with any other node in the cluster (1653)
Node failed to firm a cluster this was because witness was not accessible (1573)

4 answers

Your answer

Answer 1

Xiaowei He 9,936

Hi,

Do you mean the Cluster node unable to start cluster service, if yes, we may try to evict the cluster node, then check if the NIC on the node is well and if the NIC driver is up to date, if not, please try to update the NIC driver. Then try to re-add the Cluster node into the cluster.

If we meet issue to re-add the Cluster nodes, please run PowerShell command "Get-clusterLog" then check the detailed log when adding the cluster node.

https://learn.microsoft.com/en-us/powershell/module/failoverclusters/get-clusterlog?view=win10-ps

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.

Ben 16 Reputation points

2020-12-02T13:42:23.47+00:00

Hi, There is 2 virtual SQL servers in a SQL cluster but then also a failover cluster for the VM's in the failover cluster manager MMC console it shows both NICs as offline however I am to connect to both the connections as well as pinging from the other node. I was thinking of evicting the node but was not sure of the concequences involved in that, is it simple as just evicting and then add a role and re-add the server, it wont affect the existing node thats running with live databases on it??

The drivers for Hyper-V are up to date as far as i can tell.

I have tried running get-clusterlog, or running any of the cluster powershell commands seems to just not respond anymore in powershell

Answer 2

Ben 16

Hi, There is 2 virtual SQL servers in a SQL cluster but then also a failover cluster for the VM's in the failover cluster manager MMC console it shows both NICs as offline however I am to connect to both the connections as well as pinging from the other node. I was thinking of evicting the node but was not sure of the concequences involved in that, is it simple as just evicting and then add a role and re-add the server?

The drivers for Hyper-V are up to date as far as i can tell.

Answer 3

Ben 21

is there any further advise on this?

Ben Miller (DBAduck) 966 Reputation points

2020-12-11T15:47:03.697+00:00

If you evict the node, you will have to re-add the SQL side of things on the node that you evict as it severs the connection to SQL.

But you can certainly do that. There seems to be something wrong with the VM that cannot join.
Ben 21 Reputation points

2020-12-11T15:50:26.583+00:00

OK, so its not just a case of eviting it then re-add node and it'll sort itself out? I dont suppose theres any microsoft documentation on this either i couldnt find much related to this sort of issue, hence this question!
Ben Miller (DBAduck) 966 Reputation points

2020-12-11T16:07:34.36+00:00
It is not as easy as evicting and re-adding and it sorts itself out.

If you intend to put the node back in, then you need to do more.

On the node that you evicted, you need to run an Admin PowerShell window

Import-Module FailoverClusters Clear-ClusterNode Remove-WindowsFeature Failover-Clustering

You will need to remove SQL Server from that node as well.

Then reboot the node and you will add the feature Failover-Clustering to the node and then add the node back in. Then connect the storage and addNode the SQL part back into that node. If you need more detail, please let me know.

Answer 4

Xiaowei He 9,936

Hi,

In addition, if we have some issues with the network communication between the two nodes, after evicting the node from the cluster, we may also have issues to re-add the node into the cluster.

However, when the node fails to add to the Cluster, we may get more detailed logs about the issue, this is why I suggest getting the cluster log to check more detailed information.

Best Regards,
Anne

Share via

SQL Cluster Node - Showing as down

4 answers

Your answer