April 17, 2013 at 4:21 am
Hi
I have a 2 Node SQL Cluster;
Windows 2008 Enterprise R2 Sp1 , 128gb, with SAN storage
Admittedly it is 2012, but this is a clustering issue.
IP6 enabled on both nodes.
The Cluster Group has a static IP4 and IP6 address and fails over easily, Each NIC has a static IP4 and IP6 address
But the SQL Group has the same, yet it doesn't start on one node due to an IP6 duplicate address conflict. The node it always fails to fail to, is the second node... the node that was added to the SQL Cluster.
[font="Courier New"]Cluster IP address resource 'SQL IP Address 2 ([SERVERNAME]) cannot be brought online because a duplicate IP address 'xxxx:xxxx:xxxx:xxxx::XXX' was detected on the network. Please ensure all IP addresses are unique.[/font]
I had a Google search and found an MSDN blog on it on Validating the Cluster, http://blogs.msdn.com/b/clustering/archive/2008/07/26/8773796.aspx
In my case the cluster validated when it was initially built; now it doesn't.
So I followed the post, (There is also a Microsoft KB http://support.microsoft.com/kb/969256), disabling teredo via 'netsh' and via the registry as the netsh didnt seeme to work even though it tells me teredo is disbabled.
Yet the problem still persists on the second node...
I'm gearing up to removing IP6 off the cluster and telling the network team .. 'no IP6 on clusters'..
Has anyone else come across this?
Any advice or help would be appericated
April 17, 2013 at 2:47 pm
BrunoSealey (4/17/2013)
HiI have a 2 Node SQL Cluster;
Windows 2008 Enterprise R2 Sp1 , 128gb, with SAN storage
Admittedly it is 2012, but this is a clustering issue.
IP6 enabled on both nodes.
The Cluster Group has a static IP4 and IP6 address and fails over easily, Each NIC has a static IP4 and IP6 address
But the SQL Group has the same, yet it doesn't start on one node due to an IP6 duplicate address conflict. The node it always fails to fail to, is the second node... the node that was added to the SQL Cluster.
[font="Courier New"]Cluster IP address resource 'SQL IP Address 2 ([SERVERNAME]) cannot be brought online because a duplicate IP address 'xxxx:xxxx:xxxx:xxxx::XXX' was detected on the network. Please ensure all IP addresses are unique.[/font]
I had a Google search and found an MSDN blog on it on Validating the Cluster, http://blogs.msdn.com/b/clustering/archive/2008/07/26/8773796.aspx
In my case the cluster validated when it was initially built; now it doesn't.
So I followed the post, (There is also a Microsoft KB http://support.microsoft.com/kb/969256), disabling teredo via 'netsh' and via the registry as the netsh didnt seeme to work even though it tells me teredo is disbabled.
Yet the problem still persists on the second node...
I'm gearing up to removing IP6 off the cluster and telling the network team .. 'no IP6 on clusters'..
Has anyone else come across this?
Any advice or help would be appericated
Why you are using IPV6? Mine is also SQL2012 and I unchecked that from my NIC. I would suggest to remove IPV6, unless your business or design needs it somehow.
Be sure to check network binding on both nodes, and disable NetBios on Heartbeat.
You also need to talk to your IT or network guy and ensure that your IPs are actually reserved, to validate no one else is using them.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply