Hi All,
This weekend we had a healthy 2 node cluster get restarted. When the machines got brought up, The cluster itself would not start up, nor would the 1 role. Both the Cluster and the role had the error "The Cluster IP Address is already in use". Yes, it was in use when the cluster itself was up and running, but now its not running. To get the actual cluster working, I changed the IP of Cluster Core Resources, restarted the cluster, and boom, the cluster itself came online. The Role is a different story as it is a SQL AG cluster.
I figure it would not be that hard to change the IP's but since this is a pre-production box, I dont want to use that workaround for when this goes into production.
Server A NIC IP : 10.172.193.89
Server A Cluster IP: 10.172.193.90
Server A Role/SQL AG IP: 10.172.193.91
Server B NIC IP : 10.172.193.89
Server B Cluster IP: 10.172.193.90
Server B Role/SQL AG IP: 10.172.193.91
Within the actual Cluster events I get the Errors:
Cluster IP address resource 'IP Address 10.172.193.91' cannot be brought online because a duplicate IP address '10.172.193.91' was detected on the network. Please ensure all IP addresses are unique.
Cluster resource 'IP Address 10.172.193.91' of type 'IP Address' in clustered role 'CCTX-AG-01' failed. The error code was '0x13c1' ('The cluster IP address is already in use.').
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.
Lastly,
I disabled the NIC on the VM and tried to ping the same IP's just in case someone built other machines without me knowing, but I could not ping or communicate with those IP's. As soon as I Enabled the nic again, I could ping the IP's accordingly.
Thanks,
Jordan
