MSSQL Windows Server Failover Cluster - Cluster IP address already in use

Quadra 0 Reputation points
2025-04-23T20:26:47.6466667+00:00

Hello,

I have a cluster named "ClusterMain" that contains three nodes: N1, N2, and N3.

Everything was working fine until N3 suddenly started misbehaving and became isolated from the cluster.

Currently, N1 and N2 are functioning normally within the cluster. However, when I check the Failover Cluster Manager, N3 appears as offline.

When I log into N3 and open the Cluster Manager from there, it shows itself as online, and reports N1 and N2 as offline. At the same time, it displays an error stating that the cluster IP address is already in use.

This IP address is the same one currently being used by the active cluster (ClusterMain), so it seems like N3 is isolated and out of sync with the rest of the cluster.

I performed a network cross-check to confirm that all nodes can ping and reach each other, including on the necessary ports.

I also tried restarting the Cluster Service on N3 using the following commands :

  • Stop-Service clussvc
  • Start-Service clussvc

Then I even restarted the server itself, but the issue persists.

Could I get some advice on how to troubleshoot or resolve this issue?

Thanks in advance for your help.
User's image

Error code :

SQL Server Database Engine
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 46,551 Reputation points
    2025-04-24T06:24:40.0766667+00:00

    Cluster IP address already in use

    The cluster resource must have it's own (unused) IP address and if it's not he case, then you get that error.

    Run a ping with naming reslution to see, which machine uses the IP, like

    ping -a 192.168.0.1
    
    

  2. Quadra 0 Reputation points
    2025-04-25T12:49:34.7333333+00:00

    Hello Olaf,

    This IP is the one used by the cluster where all Nodes were presents. Now N3 is out of the cluster and try to use the same IP like if it's trying to configure its own cluster locally.

    Currenlt N1 and N2 are in the cluster with this IP without issue.

    0 comments No comments

Your answer