W2K3 cluster failed with IP Conflict -- sql server clustering

DTully
1/29/2007 8:07:19 AM

We have a A/P W2K3 cluster running SQL 2005. This morning the following error
was recorded:

The Cluster Network Driver has lost contact with Cluster service for 0
seconds. Cluster service will be Terminated.

Within 30 seconds the event log was recording IP Conflicts:

The system detected an address conflict for IP address 172.20.10.239 with
the system having network hardware address 00:13:21:B4:E1:BE. Network
operations on this system may be disrupted as a result.

The cluster did failover, but the IP error prevented SQL from coming online.
But when I logged on I was able to start the resource with no issues. I'm not
having any luck finding any info on the first error about it losing contact.
So, any help would be greatly appriciated.

Anthony Thomas
1/29/2007 10:36:19 PM

I've seen this error on a few occasions. Usually, during bus resets and
arbitration for cluster resources when one cluster node has still bound to
IP address. Eventually will timeout, thus allowing you to manually come in
later and start the resource.

If you check the cluster log on each node, you will see why one was failing,
and why the other wouldn't let go.

Tip would be to make sure you have a dedicated heartbeat network and that
all network drivers are up to date.

Sincerely,

Anthony Thomas

--

[quoted text, click to view]

sql server clustering : W2K3 cluster failed with IP Conflict