Failover Clustering and Network Load Balancing Team Blog
Hi Cluster Fans,
We’ve been seeing an increasing number of questions about a specific error in Windows Server 2008 Failover Clustering using the ‘Validate a Configuration’ Wizard (‘Validate’). This error is fairly common and very easy to fix and I’m going to show you how. But first, a little background…
Validate is our new built-in functional test tool for Failover Clustering. It can be run before you create your cluster, during creation or even during production where it functions as a diagnostics and troubleshooting tool. Passing all Validate tests is required for support, as described in our support policy: http://support.microsoft.com/kb/943984.
However some of you are failing Validate with the following error:
Verifying that there are no duplicate IP addresses between any pair of nodes.
Found duplicate IP address fe80::100:7f:fffe%13 on node node1.contoso.com adapter Local Area Connection* X and node node2.contoso.com adapter Local Area Connection* X.
It turns out that this is the result of the Teredo, an IPv6 Tunneling Protocol. Teredo allows IPv6 communications to pass through IPv4 NATs and IPv4 servers. However Teredo gives an identical IPv6 address to its network interfaces, which Failover Clustering flags as an error since it require unique IP addresses.
So how do you fix this? There are 2 ways, some details are provided here: http://technet2.microsoft.com/WindowsVista/en/library/91d35c9f-3049-44f4-b711-743dc152c7c31033.mspx?mfr=true
1) Disable Teredo through command line
a. Open ‘Command Prompt’ and ‘Run as Administrator’
i. > netsh
ii. > interface
iii. > teredo
iv. > set state disabled
c. Teredo will now be disabled
2) Disable Teredo through the registry
a. Open the Registry Editor
i. This can be done through an elevated Command Prompt and typing ‘regedit’
b. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6
c. Right-click on the ‘Parameters’ tab, select ‘New’, choose ‘DWORD’
i. Enter the following name (including capitalization): “DisabledComponents”
d. Double-click on “DisabledComponents”, select ‘Hexadecimal’, under ‘Value data’
i. Enter “8”
e. Click ‘OK’
f. Restart your machine
g. Teredo will now be disabled
But what about disabling Teredo through Device Manager? This will only disable the Teredo adapter so the system does not see it anymore, however this does not disable the underlying logic. This could cause issues later, so it is recommended to disable it through the command line or the registry.
Run Validate and this test will now pass. Enjoy your fully supported cluster!
Clustering & HA
PingBack from http://wordnew.acne-reveiw.info/?p=13184
PingBack from http://www.travel-hilarity.com/travel-airline-tickets/?p=1849
I’m a big fan of the changes to clustering in Windows 2008, especially the new cluster support policy
When you setup a cluster for Exchange 2007 CCR on Server 2008, you may find that it doesn’t validate...
PingBack from http://www.keyongtech.com/2869597-clustering-windows-2008-a
PingBack from http://www.pythian.com/blogs/1471/building-a-windows-server-2008-cluster-part-2
PingBack from http://mobilepcnz.wordpress.com/2009/03/29/cluster-validate-error-for-duplicate-ip-addresses-teredo-may-be-the-culprit/
Hi Cluster Fans, Resources can be hard to find, so every few months we will be publishing an updated
PingBack from http://besteyecreamsite.info/story.php?id=452
Thanks for the post, but i'm still getting the error. I disable it both on prompt and registry. I even did the command "Offline" on the NETSH prompt. But im still with the same error.
I have 2 Vmware images of WinSrv2008 that have been cloned.
There's anything i can do to fix it??
Thanks a lot!
I expect the problem is that you are using cloned images for cluster nodes which isn’t supported.
If you want to clone an image, you must do this before the Failover Clustering feature is installed.
During feature installation our networking driver, NetFT, will use the MAC address based on one of the physical MAC addresses of an adapter on that server. If you then cloned that image, then all the nodes would be using that same MAC address, which only exists on the first node.
To use cloned images you must:
• Configure the first server
• Clone it
• Deploy the clone
• THEN install the clustering feature and create a cluster on those clones