November 2, 2021 at 3:45 pm
Hello
I have production setup of 2 Windows 2016 Servers with SQL server 2017. Configured Failover Clustering in synchronous mode with Cloud Witness in Azure. It was working fine for more than a year, today we had some network issues and after we fixed the network secondary windows server has not came back to synchronization with primary.
I checked the logs and found in Cluste Events on secondary server "Cluster resource 'AVGListenerName_172.16.0.55' of type 'IP Address' in clustered role ''AVGListenerName" failed. The error code was '0x13c1' ('The cluster IP address is already in use.')."
This was true, because cluster role AVGListenerName was up and running on primary server, and IP address was there since it is virtual ip shared between cluster nodes and primary was working all the time with that address, and locked cloud witness(it was primary before network issues so failover did not happend).
Secondary lost connection with primary and after connection was restored wanted to bring AVG listener up with shared IP even it was up and running on primary node. Because it was not possible it did not started cluster service on secondary.
Can somebody help me with this, I can not realize why secondary did not realize that shared IP address is on primary and it was working, so it should just come back as a secondary server and continue to sync the data?
November 3, 2021 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply