Hyper-V 2012 R2 team NICs become disconnected


  • We are using HP Proliant DL 580 Gen9 servers with Hyper-V 2012 R2 Failover cluster. (8 nodes)

    Also we are using 10GB network cards type HP ethernet 530t adapter. 2x NIC's for VM team, and 2x NIC's for Cluster (HB, CSV, LM; Public..) team. Teaming mode on both teams is LCAP.

    Last friday (8.4.2017) during backup event arrived:

    Log Name:      System
    Source:        ebdrv
    Date:          8.4.2017 3:22:35
    Event ID:      15
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Description:
    lm_hw_attn.c 1733 (1): An assertion happened. Please note provider of this module.

    After that we recieved also event for every four adapters:

    Log Name:      System
    Source:        Microsoft-Windows-MsLbfoSysEvtProvider
    Date:          8.4.2017 3:22:37
    Event ID:      16949
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Member Nic {1f3b408b-2620-41b3-ad19-63d327d342af} Disconnected.

    The server lost all network connections. (server did not drop out of the cluster because we are using dedicated HB connecton on separated 1Gb nic's). We need to restart the server and network connections were reconnected.

    We are using latest Service Pack for Proliant (2016.10) so we are using latest drivers and fw...

    Any ideas?

    Monday, April 10, 2017 10:23 AM

All replies

  • Hi Sir,

    Based on my experiencing , this issue might be related to NIC hardware/driver .

    I'd suggest you disable the advanced feature for the physical team member NIC , then try again .

    ( the offload features ,such as , TCP Large Send Offload, TCP Connection Offload, ipv4 Checksum Offload ) 

    Best Regards,


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

    Tuesday, April 11, 2017 1:41 AM
  • Hi

    thanks for quick reply. This error happened only once in four months on our production environment. Four months ago we installed new Hp servers (DL 590 Gen9), we were using old HP servers (DL 580 G7) for three years and we did not recive any error with network.

    So I want to know as much as possible tips in case that this error will happen in future.

    Is there any more useful tips available for this kind of error?


    • Edited by Simonaa Wednesday, April 12, 2017 10:26 AM
    Wednesday, April 12, 2017 7:38 AM
  • I was curious if you ever got more information or if the issue happened again?

    We had the same issue and error code happen to us this morning.  We are using Dell servers so I don't think the hardware is the problem.



    Thursday, August 30, 2018 5:05 PM