Cluster Validate Error for Duplicate IP Addresses? Teredo may be the Culprit!

Cluster Validate Error for Duplicate IP Addresses? Teredo may be the Culprit!

Rate This
  • Comments 11

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’

b.      Type:

                                                              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!

 

Thanks,

Symon Perriman

Program Manager

Clustering & HA

 

Leave a Comment
  • Please add 7 and 3 and type the answer here:
  • Post
Page 1 of 1 (11 items)