To improve Windows Server I suggest you ...

Make LACP NIC teaming comply with LACP standard for NIC speeds (all same)

Currently LBFO using LACP allows the NICs to renegotiate to different speeds which is not allowed in LACP standard.

We've just had a 4 x 1Gb LACP team change to a 3 x 1Gb + 1 x 100 Mb team. LACP requires all link speeds are the same. If NIC was unable to stay at 1Gb, it should have been faulted and dropped from team. Allowing one NIC to drop to 100Mb reduced effective link speed to 100Mb. Gigabit standard requires (?) autonegotiation of individual link speeds - but LBFO should ensure compliance of team with LACP standard. This occurred while moving VMs off this host to another - thankfully I was watching the throughput graph when NIC changed to 100 Mb.

<Team running at 100Mb effective - two main flows, 2 VMs both moving from host 1 to host 2>

PS C:\Windows\system32> Get-NetLbfoTeam

Name : HV-Team
Members : {NIC3_LAG1, NIC4_LAG1, NIC5_LAG1, NIC2_LAG1}
TeamNics : LAG1_4Gb_Trunk_(NIC2-5)
TeamingMode : Lacp
LoadBalancingAlgorithm : Dynamic
Status : Up

PS C:\Windows\system32> Get-NetLbfoTeamMember

Name : NIC3_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC4_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #56
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC5_LAG1
InterfaceDescription : Intel(R) PRO/1000 PT Server Adapter
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC2_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #54
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Mbps) : 100
ReceiveLinkSpeed(Mbps) : 100
FailureReason : NoFailure

<Disabled NIC @ 100 Mb via GUI>

PS C:\Windows\system32> Get-NetLbfoTeam

Name : HV-Team
Members : {NIC3_LAG1, NIC4_LAG1, NIC5_LAG1, NIC2_LAG1}
TeamNics : LAG1_4Gb_Trunk_(NIC2-5)
TeamingMode : Lacp
LoadBalancingAlgorithm : Dynamic
Status : Degraded

PS C:\Windows\system32> Get-NetLbfoTeamMember

Name : NIC3_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC4_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #56
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC5_LAG1
InterfaceDescription : Intel(R) PRO/1000 PT Server Adapter
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC2_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #54
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Failed
TransmitLinkSpeed(Mbps) : 0
ReceiveLinkSpeed(Mbps) : 0
FailureReason : NicNotPresent

<Team now running reliably at 3 x 1 Gb>

1 vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Alex Heylin shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base