none
Public IPv6 address

    Question

  • Hi 

    I've been trouble shooting an issue with a hyper V failover cluster and I've been skimming through the network config for the VM hosts.

    It's a 2 node cluster and comprised of 2 X dell FC630's in an FX-2 chassis. The only difference in config that I can see is that when the NICS presented to the OS are placed into a NIC team, the team get an IPv6 that is not a local link address (fe80). 

    The other node does however and this is what i would expect as the VLAN associated with getting out of the local subnet is not configured.

    One of the outcomes is that this cluster network is appearing incorrectly in my cluster configuration with the wrong address.

    Thursday, April 11, 2019 4:16 PM

Answers

  • Hi,

    I got to the bottom of this. The SLAAC address was being picked up on a node that was configured with a different NIC teaming mode to what it should have been. It was on lacp as opposed to switch independent.

    The config for the cluster is now consistent for all cluster networks. 

    • Marked as answer by gjwalsh Monday, April 15, 2019 2:43 PM
    Monday, April 15, 2019 2:43 PM

All replies

  • Hi,

    Thanks for your question.

    Would you mind providing a detailed information of your current situation please? Or you can post a screenshot for the configuration here? So that we can get further troubleshooting.

    Furthermore, any error message in the cluster events or in the event viewer of the nodes?

    Please note, you need to cover up your sensitive privacy information when uploading the screenshots here for your security.

    Highly appreciate your effort and time. If you have any question or concern, please feel free to let me know.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, April 12, 2019 3:24 AM
    Moderator
  • Hi

    I've tried to attach a diagram of the cluster. It keeps saying i need to verify my account. I've attached an output from powershell below that shows the difference between the nic teams on each node

    Output from node that is correctly configured

    InterfaceAlias       : FaultDomain1+2
    InterfaceIndex       : 20
    InterfaceDescription : Microsoft Network Adapter Multiplexor Driver
    NetProfile.Name      : Unidentified network
    IPv4Address          : 169.254.6.151
    IPv6DefaultGateway   :
    IPv4DefaultGateway   :
    DNSServer            : fec0:0:0:ffff::1
                           fec0:0:0:ffff::2
                           fec0:0:0:ffff::3

    Output from node that is incorrectly configured

    InterfaceAlias       : FaultDomain1+2
    InterfaceIndex       : 18
    InterfaceDescription : Microsoft Network Ad
    NetProfile.Name      : Unidentified network
    IPv6Address          : 2001:770:20:42c2:7de
    IPv4Address          : 169.254.83.145
    IPv6DefaultGateway   :
    IPv4DefaultGateway   :
    DNSServer            : fec0:0:0:ffff::1
                           fec0:0:0:ffff::2
                           fec0:0:0:ffff::3

    Both adapters are configured in exactly the same way but one seems to be picking up a valid ipv6 address even though they both have local link addresses for ipv4

    Friday, April 12, 2019 1:43 PM
  • The output below shows the vlan info associated with each adapter on the node that is picking up this unwanted address.

    PS C:\Users\gjwalsh> Get-NetAdapter | select interfacealias,vlanid

    InterfaceAlias                        vlanid
    --------------                        ------
    vEthernet (VM traffic 122)
    FaultDomain1+2 - VLAN122 Mgmt+Traffic 122
    FaultDomain1+2 - VLAN125 LivMig       125
    FaultDomain1+2 - VLAN123 ISCSI1       123
    FaultDomain1+2 - VLAN126 ISCSI2       126
    FaultDomain1+2
    NIC3                                  0
    NIC1                                  0
    NIC4                                  0
    NIC2                                  0

    Friday, April 12, 2019 2:04 PM
  • Theses seem to match on both nodes. VLAN 122 is the one associated with getting out of the local subnet.

    PS C:\Users\gjwalsh>  Get-NetAdapter | select interfacealias,vlanid

    InterfaceAlias                      vlanid
    --------------                      ------
    FaultDomain1+2 VLAN 125 LivMig         125
    NIC4                                     0
    FaultDomain1+2
    vEthernet (VM Traffic 122)
    FaultDomain1+2 VLAN123 ISCSI1          123
    FaultDomain1+2 VLAN122 Mgmt+Traffic    122
    NIC3                                     0
    NIC2                                     0
    FaultDomain1+2 VLAN126 ISCSI2          126
    NIC1                                     0

    Friday, April 12, 2019 2:09 PM
  • What does the cluster validation report say about the network configuration?  It often provides fairly decent explanations of issues it finds.

    tim

    Saturday, April 13, 2019 12:32 PM
  • Hi,

    How are things going on? 

    As Tim's said, we can run a validation for the cluster, and check the network configuration with the report.


    Meanwhile, we can check the following link to verify your TN account. Later you can upload something like screenshots. Please remember to cover up the information if it is sensitive related to your privacy for your security.                                                                                                                                                                              

    https://social.msdn.microsoft.com/Forums/en-US/090972cb-b81f-498f-b718-948caca975c4/verify-account-41?forum=reportabug

    Please feel free to let us know if you need further assistance.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, April 15, 2019 9:17 AM
    Moderator
  • Hi,

    I got to the bottom of this. The SLAAC address was being picked up on a node that was configured with a different NIC teaming mode to what it should have been. It was on lacp as opposed to switch independent.

    The config for the cluster is now consistent for all cluster networks. 

    • Marked as answer by gjwalsh Monday, April 15, 2019 2:43 PM
    Monday, April 15, 2019 2:43 PM
  • Hi,

    Thanks for your sharing and support.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, April 29, 2019 2:29 PM
    Moderator