none
Teredo and clustering

    Question

  • I attempted to cluster two of my machines using LH 6001.16475.070228 x86 build but the Cluster Validation Tool failed my setup because of duplicate IP addresses. After digging in the log I noticed that Teredo addresses on both nodes were identical. I was able to remove the duplicate IP error after disabling Teredo on both machines.

    Is this a bug? I was under the impression that Teredo supposed to generate unique addresses.

    Tuesday, March 13, 2007 3:43 PM

Answers

  • So, based on our 'offline' conversation, it appeared that the problem was a fibre optic cable, and once that was replaced, everything worked fine and you were able to create a cluster and move forward.

     

    Thanks.

     

     

    Tuesday, April 24, 2007 11:01 AM
    Moderator

All replies

  • Well, since Teredo addressing is partially based on IPv4 addresses, if you have a duplicate IPv4 address you could, potentially, have an duplicate Teredo address.  I personally have never run into this issue in the cluster validation process.
    Wednesday, March 14, 2007 1:47 PM
    Moderator
  • I verified and there are no-duplicate IPv4 addresses. The following address was assigned on both nodes

     

    Item Name
    Adapter Name Local Area Connection* 8
    Adapter Description Teredo Tunneling Pseudo-Interface
    Physical Address 02-00-54-55-4E-01-00-00
    Status Not Operational
    IP Address fe80::100:7f:fffe%12
    Prefix Length 64

     

    and here is an error

     

    Verifying that a node does not have multiple adapters connected to the same subnet.
    Verifying that each node has at least one adapter with a defined default gateway.
    Verifying that there are no node adapters with the same EUI-48 physical address.
    Verifying that there are no duplicate IP addresses between any pair of nodes.
    Found duplicate IP address fe80::100:7f:fffe%12 on node twilk-amd1.twilk-dom2.com adapter Local Area Connection* 8 and node twilk-amd2.twilk-dom2.com adapter Local Area Connection* 8.
    Checking that nodes are consistently configured with IPv4 and/or IPv6 addresses.


     

    Thursday, March 15, 2007 2:10 PM
  • It will not be possible to address this issue in a build that is later than the Feb CTP and not available on the Connect site.  I suggest you run validation using the FEB CTP build which is either of these - 

    0xBC239496      wsl_6001.16461.070209-1510_x86fre_server-KB3SFRE_EN_DVD.iso

     

    0x94CD7B61     wsl_6001.16461.070209-1510_x64fre_server-KB3SxFRE_EN_DVD.iso

     

    Please post the results when completed.

     

    Thanks.

    Thursday, March 15, 2007 2:20 PM
    Moderator
  • The build I am using is from the Connect site.

     

    Windows Server Longhorn 6001-16475-070228-1640 for X86 and X64 (Weekly)

    0x5DEAF265 wsl_6001.16475.070228-1640_x86fre_server-KB3SFRE_EN_DVD.iso

    0xCE9AF82D wsl_6001.16475.070228-1640_x64fre_server-KB3SxFRE_EN_DVD.iso

    http://connect.microsoft.com/windows/Downloads/DownloadDetails.aspx?DownloadID=5607

     

    Feb CTP build did not have this problem and that was the build I was using before. I moved to a newer build due to other LH bugs.

    thx

    Thursday, March 15, 2007 3:57 PM
  • Hi,

    Looks like it is detecting a duplicate link local IPv6 address, we are currently investigating.  We'll have more to follow shortly.

    Thanks!!
    Elden Christensen
    Program Manager
    Windows Failover Cluster Group
    Microsoft Enterprise Server Products

    Of course, this posting wouldn’t be complete without a nice, juicy disclaimer from our lawyers: This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use. © 2007 Microsoft Corporation. All rights reserved.
    http://www.microsoft.com/info/cpyright.htm

    Friday, March 16, 2007 1:47 AM
    Owner
  • Can you confirm that this was a 'Warning' message and not a 'Failure' message.
    Friday, March 16, 2007 11:23 AM
    Moderator
  • It was an error message.

     

    Validate Cluster Network Configuration Success
    Validate IP Configuration Failed
    Validate Network Communication Success
    Validate Windows Firewall Configuration Success

     

    Friday, March 16, 2007 3:15 PM
  • I noted in your validation reports that your PnP Drivers indicated a Teredo Pseudo Tunneling Interface and it had an error associated with it on both nodes in the cluster.  The interface that should be reported is a 6TO4 Adapter.  If there are errors with the device, I would expect the networking tests that are run as part of cluster validation would have some problems.

     

     

     

    Friday, March 16, 2007 6:30 PM
    Moderator
  • So, based on our 'offline' conversation, it appeared that the problem was a fibre optic cable, and once that was replaced, everything worked fine and you were able to create a cluster and move forward.

     

    Thanks.

     

     

    Tuesday, April 24, 2007 11:01 AM
    Moderator
  • HI guys

     

             I ran into the same issue, the validate IP configuration failed with the same error. Would like to know about the offline discussion you had which resolved the problem. I too have a FC connectivity, my quorum disk is in a SAN in a Xiotech storage device. If I remove the FC connection the quorum will be lost and the disk validation might fail.

    Please let me know the solution to this problem.

     

    Thanks & regards

    Wednesday, September 26, 2007 1:04 PM
  • Hello Sir

     

                I too ran into same issue and couldn't resolve it. From the discussion it appears that something has to be done with FC connectivity, I do not understand the relationship between NIC for private connection for the clustrer and the HBA.

    Please let me know how the issue was resolved.

     

    I appreciate your help.

     

    Thanks

     

    Wednesday, September 26, 2007 1:10 PM
  • We cannot assume your problem is the same.  So, we need to know some information like, are you running the recently released RC0 build, which you will need to run and duplicate the problem to even move forward?  Also, what happens with the cluster validation report, and are you showing a Teredo interface or a 6TO4 Tunnel interface in the validation report and in ipconfig /all?

     

    Thanks.

     

    Chuck

    Wednesday, September 26, 2007 1:19 PM
    Moderator
  • Hi

     

      I got it resolved by disabling the terodo from device manager. We don't support or need IPV6. It would be great if someone point more thoughts on the root cause of issue and about terodo.

     

    thx

    Wednesday, September 26, 2007 2:05 PM
  •  

    Part of my point is you should not be seeing a 'Toredo' device.  You should see a 6TO4 adapter and perhaps several isatap adapters.

     

    Chuck

    Wednesday, September 26, 2007 3:24 PM
    Moderator
  • HI

     

      Thanks for prompt resonse. I am running the BEta build 6001. Here is what the cluster validation report says:

     

    Item Name
    Adapter Name Local Area Connection* 11
    Adapter Description Teredo Tunneling Pseudo-Interface
    Physical Address 02-00-54-55-4E-01-00-00
    Status Not Operational
    IP Address fe80::100:7f:fffe%13
    Prefix Length 64

     

     

    followed by

    Verifying that a node does not have multiple adapters connected to the same subnet.
    Verifying that each node has at least one adapter with a defined default gateway.
    Verifying that there are no node adapters with the same EUI-48 physical address.
    Verifying that there are no duplicate IP addresses between any pair of nodes.
    Found duplicate IP address fe80::100:7f:fffe%13 on node solsrvhyd242.mptest.dom adapter Local Area Connection* 11 and node solsrvhyd243.mptest.dom adapter Local Area Connection* 11.
    Checking that nodes are consistently configured with IPv4 and/or IPv6 addresses.
     
     
    ****************************
     
    ipconfig /all
     
    ----- ----
    ------  ----
    Tunnel adapter Local Area Connection* 8:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{14D8BD68-BD1B-41DD-8AC5-A3A7DFFA7
    F5F}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:10.64.132.242%12(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 10.64.132.53
                                           10.64.3.10
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter Local Area Connection* 9:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:10.10.10.123%16(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
    Tunnel adapter Local Area Connection* 13:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{D6D06EBC-9DF2-40C3-89D2-A34D05F89
    FB1}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:169.254.1.117%15(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Disabled
     
     
     
    Thanks & regards
    Waymoon 
    Thursday, September 27, 2007 4:37 AM
  • OK, run this command and post the output

     

    netsh interface ipv6 show teredo

     

    Thanks.

     

    Chuck

     

    Thursday, September 27, 2007 1:35 PM
    Moderator
  • HI


    C:\>netsh interface ipv6 show teredo
    Teredo Parameters
    ---------------------------------------------
    Type                    : default
    Server Name             : teredo.ipv6.microsoft.com.
    Client Refresh Interval : 30 seconds
    Client Port             : unspecified
    State                   : offline
    Error                   : client is in a managed network

     

     

    Thanks

    Friday, September 28, 2007 3:56 AM
  • Confirm also for me that you are not running the cluster in virtual Server or VMWARE.

     

    Thanks.

     

    Monday, October 01, 2007 3:01 PM
    Moderator
  • I get the exact same error when validating my cluster configuration, during "Valid IP configuration"


    Found duplicate IP address fe80::100:7f:fffe%14 on node water.xxx.com adapter Local Area Connection* 11 and node wind.xxx.com adapter Local Area Connection* 11.

    I'm using Windows Server 2008 (Version 6.0 Build 6001: Service pack 1). This is not a cluster running under VMWare or Virtual Server.
    Wednesday, February 27, 2008 10:27 PM
  • I was able to resolve the issue with my Validating IP configuration step failing because of duplicate IP address. The ipv6 address of a teredo network interface on both nodes of my cluster were identical (fe80::100:7f:fffe).

    Steps
    1.Run 'netsh' from command prompt
    2. type "interface ipv6"
    3. type "show address" and view the IPv6 address of allinterface on the machine
    4. Run this on the other nodes of the cluster and identify the duplicate ipv6 address
    5. Set ipv6 address of this interface to something else, and remove existing ipv6 address
    6. Run Validate cluster configuration again, and select only "validating IP configuration" step.
    7. You should not see any duplicate ip address at this point
    Thursday, February 28, 2008 1:49 PM
  • Hi,

    Got the same issue with a release of Datacenter edition, an ethernet only network, 3 nodes and 3 NIC per node.
    Validation report that all nodes have the same IPV6 address for
    Local Area Connection* 12.

    Here is an ipconfig output for 2 nodes. Note that MAC address is the same for all nodes for
    Teredo Tunneling Pseudo-Interface adapter, and there's no IP shown for this interface.

    This is for information, disabling NIC and/or IPV6 will probably solve the problem.

    NODE1:

    Windows IP Configuration



       Host Name . . . . . . . . . . . . : win2

       Primary Dns Suffix  . . . . . . . : windows

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

       DNS Suffix Search List. . . . . . : windows

                                           toulouse paris wifi xendomain



    Ethernet adapter Local Area Connection* 8:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter

       Physical Address. . . . . . . . . : 02-1A-64-6D-84-52

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes



    Ethernet adapter Local Area Connection 3:



       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #3

       Physical Address. . . . . . . . . : 00-10-18-2E-34-95

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80::591f:f549:1208:5e3%12(Preferred)

       IPv4 Address. . . . . . . . . . . : 172.21.2.1(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Lease Obtained. . . . . . . . . . : jeudi 27 mars 2008 12:01:59

       Lease Expires . . . . . . . . . . : dimanche 30 mars 2008 00:01:53

       Default Gateway . . . . . . . . . : 172.21.254.1

       DHCP Server . . . . . . . . . . . : 172.16.254.1

       DNS Servers . . . . . . . . . . . : 192.168.0.2

       NetBIOS over Tcpip. . . . . . . . : Enabled



    Ethernet adapter Local Area Connection 2:



       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2

       Physical Address. . . . . . . . . : 00-1A-64-6D-84-51

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80:Big Smile16d:b4:611a:abcc%11(Preferred)

       IPv4 Address. . . . . . . . . . . : 172.17.2.1(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Lease Obtained. . . . . . . . . . : jeudi 27 mars 2008 12:01:59

       Lease Expires . . . . . . . . . . : dimanche 30 mars 2008 00:01:53

       Default Gateway . . . . . . . . . : 172.17.254.1

       DHCP Server . . . . . . . . . . . : 172.16.254.1

       DNS Servers . . . . . . . . . . . : 172.17.1.1

                                           192.168.0.2

       NetBIOS over Tcpip. . . . . . . . : Enabled



    Ethernet adapter Local Area Connection:



       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet

       Physical Address. . . . . . . . . : 00-1A-64-6D-84-52

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80::a46e:939:663d:b441%10(Preferred)

       IPv4 Address. . . . . . . . . . . : 172.19.2.1(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Lease Obtained. . . . . . . . . . : jeudi 27 mars 2008 12:01:59

       Lease Expires . . . . . . . . . . : dimanche 30 mars 2008 00:01:53

       Default Gateway . . . . . . . . . : 172.19.254.1

       DHCP Server . . . . . . . . . . . : 172.16.254.1

       DNS Servers . . . . . . . . . . . : 192.168.0.2

       NetBIOS over Tcpip. . . . . . . . : Enabled



    Tunnel adapter Local Area Connection* 11:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft ISATAP Adapter

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes



    Tunnel adapter Local Area Connection* 9:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : isatap.toulouse paris wifi xendomain

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes



    Tunnel adapter Local Area Connection* 12:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

       Physical Address. . . . . . . . . : 02-00-54-55-4E-01

       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes


    NODE 2:


    Windows IP Configuration



       Host Name . . . . . . . . . . . . : win3

       Primary Dns Suffix  . . . . . . . : windows

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

       DNS Suffix Search List. . . . . . : windows

                                           toulouse paris wifi xendomain



    Ethernet adapter Local Area Connection* 8:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter

       Physical Address. . . . . . . . . : 02-1A-64-6D-84-4C

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes



    Ethernet adapter Local Area Connection 3:



       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #3

       Physical Address. . . . . . . . . : 00-10-18-2E-4D-B2

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80:Big Smile96f:1f7c:ce7d:4f4e%12(Preferred)

       IPv4 Address. . . . . . . . . . . : 172.21.3.1(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Lease Obtained. . . . . . . . . . : jeudi 27 mars 2008 12:00:54

       Lease Expires . . . . . . . . . . : dimanche 30 mars 2008 00:00:53

       Default Gateway . . . . . . . . . : 172.21.254.1

       DHCP Server . . . . . . . . . . . : 172.16.254.1

       DNS Servers . . . . . . . . . . . : 192.168.0.2

       NetBIOS over Tcpip. . . . . . . . : Enabled



    Ethernet adapter Local Area Connection 2:



       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2

       Physical Address. . . . . . . . . : 00-1A-64-6D-84-4B

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80::54e5:9baf:1827:eaf3%11(Preferred)

       IPv4 Address. . . . . . . . . . . : 172.17.3.1(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Lease Obtained. . . . . . . . . . : jeudi 27 mars 2008 12:00:54

       Lease Expires . . . . . . . . . . : dimanche 30 mars 2008 00:00:53

       Default Gateway . . . . . . . . . : 172.17.254.1

       DHCP Server . . . . . . . . . . . : 172.16.254.1

       DNS Servers . . . . . . . . . . . : 172.17.1.1

                                           192.168.0.2

       NetBIOS over Tcpip. . . . . . . . : Enabled



    Ethernet adapter Local Area Connection:



       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet

       Physical Address. . . . . . . . . : 00-1A-64-6D-84-4C

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80::5d5f:355d:815c:b412%10(Preferred)

       IPv4 Address. . . . . . . . . . . : 172.19.3.1(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Lease Obtained. . . . . . . . . . : jeudi 27 mars 2008 12:00:54

       Lease Expires . . . . . . . . . . : dimanche 30 mars 2008 00:00:53

       Default Gateway . . . . . . . . . : 172.19.254.1

       DHCP Server . . . . . . . . . . . : 172.16.254.1

       DNS Servers . . . . . . . . . . . : 192.168.0.2

       NetBIOS over Tcpip. . . . . . . . : Enabled



    Tunnel adapter Local Area Connection* 11:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft ISATAP Adapter

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes



    Tunnel adapter Local Area Connection* 9:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . : toulouse paris wifi xendomain

       Description . . . . . . . . . . . : isatap.toulouse paris wifi xendomain

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes



    Tunnel adapter Local Area Connection* 12:



       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

       Physical Address. . . . . . . . . : 02-00-54-55-4E-01


       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes

    Thursday, March 27, 2008 1:44 PM
  • Teredo is an IPv6 transition technology which provides IPv6 connectivity to clients on an IPv4 network, it is a technology intended for consumers (e.g. home users). It enables NAT traversal for peer-to-peer applications. Teredo is not intended for use in enterprise or any server environment.  Teredo uses a static IPv6 address that is consistent across all machines, and because the address on all nodes is the same the Validate wizard detects it as a duplicate IP Address.

    Teredo is disabled by default on server installations. There may be something about your environment that enabled it, unless you need it I would recommend disabling it.

     

    To Turn Off Teredo:

    1. Open Device Manager
    2. Click View, then Show Hidden Devices
    3. Under Network Adapters find "Teredo Tunneling Pseudo-Interface"
    4. Right Click and select Disable

     

    You can find additional instructions to disable Teredo in this TechNet article: http://technet2.microsoft.com/WindowsVista/en/library/91d35c9f-3049-44f4-b711-743dc152c7c31033.mspx?mfr=true.

     

    Thanks!!
    Elden Christensen
    Lead Program Manager
    Windows Failover Cluster Group
    Microsoft Enterprise Server Products

     

    Of course, this posting wouldn’t be complete without a nice, juicy disclaimer from our lawyers: This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use. © 2008 Microsoft Corporation. All rights reserved.
    http://www.microsoft.com/info/cpyright.htm

    Sunday, March 30, 2008 10:31 PM
    Owner
  • I am having a similar issue.  I have an Exchange 2007 SP1 CCR cluster setup with Windows 2008 server.  When I send en email to an external orgnization...I am seeing the link local IPV6 addresses in the message header.  I have turned off IPv6 on the interfaces, but I notice that is is showing up on the Microsoft Failover Cluster Virtual Interface.  Is there something else I need to do?

     

    I believe the Teredo suff is set up...I didn't want to destroy my cluster by turning it off?  What do you recommend?

     

     

    Thank you for your help

     

    Jonathan

    Tuesday, April 22, 2008 9:28 PM
  • I am having the same issue.  the error is the exact same down to the IP address!

    Found duplicate IP address fe80::100:7f:fffe%11 on node e2008mbx1.test.local adapter Local Area Connection* 9 and node e2008mbx2.test.local adapter Local Area Connection* 9.

     

    I ran 'netsh int teredo set state disabled'

    C:\Users\chefadmin>netsh int teredo set state disabled
    Ok.


    C:\Users\chefadmin>netsh int teredo show state
    Teredo Parameters
    ---------------------------------------------
    Type                    : client
    Server Name             : teredo.ipv6.microsoft.com.
    Client Refresh Interval : 30 seconds
    Client Port             : unspecified
    State                   : offline
    Error                   : client is in a managed network

     

    And am still getting the error.  I am running this in a VMware environment.

     

    Brad

    Friday, May 16, 2008 7:22 PM
  • When setting up Win2008 cluster in a VMware environment make sure that you do not clone nodes. Install OS on both nodes from the scratch. If you clone nodes you may and probably will end up with this error.
    Friday, May 16, 2008 8:00 PM
  • No luck with "netsh int teredo set state disabled". MS Cluster validation tool still finds duplicate teredo IPv6 addresses.

     

    Did the following to get Cluster validation tool without fails (had already done int teredo set state disabled).

     

    netsh interface teredo set state enterpriseclient

     

    If I've understood it correctly teredo is for home users & this settings tells teredo that we are running in an enterprise environment so stop setting same IP on NIC's  Verified that teredo got unique IPv6 address after "netsh interface teredo set state enterpriseclient".

     

    /Zensig

    Wednesday, May 21, 2008 10:27 AM
  • Give this a try to diasble off Teredo:

    1. Open Device Manager
    2. Click View, then Show Hidden Devices
    3. Under Network Adapters find "Teredo Tunneling Pseudo-Interface"
    4. Right Click and select Disable

     

    Friday, May 23, 2008 3:59 PM
    Owner
  • Hi

    I received the same error too on Local Area Connection* 9 which is the Microsoft Failover Cluster Virtual Adapter. I did computer duplication, but using the built-in sysprep.
    First I installed hyper-v, failovercluster and drivers and then did the sysprep. Both node looked good except this error message. The cluster validation showed that the MAC address and the IP address of this adapter is the same on both node. I could solve this issue with reinstalling failovercluster feature.
    After the reinstall I just received a warning: Node "node 1" does not have an adapter with a defined default gateway, but I think this warning belongs to other configuration issue at my side.
    regards
    bg.
    • Proposed as answer by _BG_ Wednesday, November 19, 2008 4:25 PM
    Wednesday, November 19, 2008 4:18 PM
  • the issue with ipv6 conflicts in 2008 clustering is clarified here with a workaround:

    http://blogs.msdn.com/clustering/archive/2008/07/26/8773796.aspx
    Sunday, November 23, 2008 2:37 PM
  • The cloning issue is a seperate issue, not related to Teredo (or this thread).

    It is not supported to SysPrep / Clone OS images once the Failover Clustering feature has been installed.  The NetFT adapter generates it's MAC address off a hash of the local interface.  If you clone post-feature install, the adapters will generate valid errors.  You need to SysPrep / Clone, then you can have a script to install the Failover Clustering feature in the Run / Run Once.

    Thanks!
    Elden
    Sunday, November 23, 2008 9:29 PM
    Owner