none
Windows cluster 2008 - Add node 2 error

    Pregunta

  • Hi All,

    I have 1 issue when I add node 2 to the cluster in windows 2008 enterprise. I give you some information:

    This is an error when I validate:

    Validate IP Configuration:

    Found duplicate physical address 02-1E-90-BD-1A-42 on node ims01.acb.com adapter Local Area Connection* 9 and node ims02.acb.com adapter Local Area Connection* 9.

    I show ipconfig /all on two nodes. The result of adapter Local Area Connection* 9 is the same (Physical Address. . . . . . . . . : 02-1E-90-BD-1A-42):


    Ethernet adapter Local Area Connection* 9(node1):

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-1E-90-BD-1A-42
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::3507:475e:d5c4:7e5d%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 169.254.1.34(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       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. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection* 9 (node2):

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-1E-90-BD-1A-42
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Please help me!

    Thanks in advance.


    lunes, 13 de octubre de 2008 2:43

Todas las respuestas

  • Hi,

    The servers are created on Hyper-V? If so please add legacy adapter instead of network adapter from the Virtual machine property and assign alternate MAC address.

    Mac address never be same for the physical adapter before adding to the NLB cluster.
    jueves, 04 de diciembre de 2008 16:45
  •   If you are using a sysprep'd image and the Failover Cluster feature was installed before you sysprep'd, then that is your problem.  You cannot have the Failover Cluster feature installed and then sysprep a machine.

    Chuck Timon Senior Escalation Engineer (SEE) Microsoft corporation
    viernes, 05 de diciembre de 2008 12:10
  • Hi,

    Assuming you are sysprep free, have you disabled the Teredo adapter?  

    http://blogs.msdn.com/clustering/archive/2008/07/26/8773796.aspx


    Thanks,
    Symon Perriman
    Program Manager
    Clustering & HA
    SymonP_MSFT
    martes, 30 de diciembre de 2008 0:56
  • If you're tearing your hair out trying to make this work in VMware (or similar), disabling Teredo doesn't work, removing/sysprepping/reinstalling failover clustering doesn't help, and reinstalling Windows from scratch doesn't help, try the following as it just worked for me!

    1. Remove failover clustering
    2. I created a new VM with a different NIC type and attached the original disk. Removing the network adaptor and replacing (perhaps with a different type) may also work - I don't plan to test this.
    3. Reinstall failover clustering.

    Hope this helps.

    Ed
    miércoles, 17 de junio de 2009 20:27
  • I agree with Chuck Timon, but solution exists. The fastest way could be:

    Search the MAC address string inside Windows registry at point "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class".

    Backup founded current settings and change the string.

    lunes, 11 de junio de 2012 10:05