Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Microsoft failover cluster virtual adapter MAC address does not match any MAC address of the machine's NIC

Answered Microsoft failover cluster virtual adapter MAC address does not match any MAC address of the machine's NIC

  • Thursday, July 26, 2012 9:59 AM
     
     
    Sign In to Vote
    0

    Hi, Everyone.

    Please help me with this problem currently on one of the cluster node, the Microsoft Failover Cluster Virtual Adapter has a MAC address that is different from the physical NIC mac address of the machine. Below are the info from ipconfig /all:

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : HP NC326m PCIe Dual Port Adapter #2
       Physical Address. . . . . . . . . : 00-23-7D-38-95-D7
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : xx.2xx.28.40(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.192.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter :

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : HP NC326m PCIe Dual Port Adapter
       Physical Address. . . . . . . . . : 00-23-7D-38-95-D6
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : xx.1xx.1xx.33(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : xx.1xx.1xx.1
       DNS Servers . . . . . . . . . . . : xx.1xx.1xx.30
                                           xx.1xx.1xx.31
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection* 8:

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-21-5A-B0-AA-44
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 169.254.1.248(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Private LAN:

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter #46
       Physical Address. . . . . . . . . : 00-23-7D-58-43-68
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.255.254.12(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Management LAN:

       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter #41
       Physical Address. . . . . . . . . : 00-23-7D-58-43-6A
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : xx.1xx.2xx.25(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.252.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Also to add the details when I go to device maanger it show 2 Microsoft fail-over cluster virtual adapter. One is the regular Microsoft fail-over cluster virtual adapter and the 2nd is Microsoft Failover cluster virtual adapter - Teefer2 Miniport. Was this causing the problem?



     

All Replies

  • Thursday, July 26, 2012 10:48 AM
     
     
    Sign In to Vote
    0

    Hello,

    Microsoft Failover Cluster Virtual Adapter is a virtual adapter and you can see in device manager and other places.

    Also MAC Address is not associated with Physical Network adapters also it is virtual.

    If you try to connect the server with Cluster Name, it has different IP address and you can connect on active node.

    Virtual IP Address and adapters are bounded to active node.

    FYI.

    Murat Demirkiran

    If the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. www.scvmm2012.com (TR Language) Please note that I'm not a Microsoft Representative or SpokesPerson.

     
  • Thursday, July 26, 2012 12:44 PM
     
     
    Sign In to Vote
    0

    Hi, Murat.

    Thank you for your response, but your response is different for what I have read in this article: http://blogs.technet.com/b/askcore/archive/2009/02/13/what-is-a-microsoft-failover-cluster-virtual-adapter-anyway.aspx (please correct me if I misunderstood the statement in the article), where it states: "The MAC address that is assigned to the Microsoft Failover Cluster Virtual Adapter is based on the MAC address of one of the physical NICs" also when I check the partner cluster node the Microsoft Failover Cluster Virtual Adapter indeed use one of the MAC address of the physical NIC of the machine.

     
  • Friday, July 27, 2012 12:25 AM
     
     
    Sign In to Vote
    0
    bumping this question.
     
  • Monday, July 30, 2012 8:38 AM
     
     
    Sign In to Vote
    0
    bump again.
     
  • Monday, July 30, 2012 12:41 PM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Was the O/S installed using an image from a different host? Assuming the answer is yes, was it imaged with the "Failover Clustering" feature already installed? If so, that would explain why your MAC address is so different as it's based on the host where the image was originally collected.

    If this is a cluster that is not in production, you can remove the Failover Clustering feature and then re-install this feature. This will re-install this virtual NIC and use a MAC address that follows the guidelines described in Jeff's blog post.

    Hope this helps.

    Visit my blog about multi-site clustering

     
  • Tuesday, July 31, 2012 8:29 AM
     
     
    Sign In to Vote
    0

    Hi, John.

    Thank you so much for the quick response but unfortunately the machine is already in production. I cannot remove it from the cluster is there any other way to refresh Microsoft Virtual Fail-over cluster adapter?

     
  • Wednesday, August 01, 2012 1:38 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Sorry, removing the Failover Clustering feature and re-adding the feature is the only way to re-install this virtual adapter.

    Visit my blog about multi-site clustering