Home
Join
check
  • Are the 2016 and 2019 both using SET (switch embedded teaming)?

    I think this display value is purely cosmetic - given teams do not aggregate single flows, the total speed is irrelevant in any form of load calculation only individual link speed. Note 3 is a strange number, you will likely get uneven loading due to the hashing.

    1 found this helpful thumb_up thumb_down
  • View Best Answer in replies below

    3 Replies

    • Are the 2016 and 2019 both using SET (switch embedded teaming)?

      I think this display value is purely cosmetic - given teams do not aggregate single flows, the total speed is irrelevant in any form of load calculation only individual link speed. Note 3 is a strange number, you will likely get uneven loading due to the hashing.

      1 found this helpful thumb_up thumb_down
    • m@ttshaw thanks for the reply. Didn't consider the likelihood of uneven loading and since the display value is purely cosmetic its a no brainer to drop it down to 2 NICs on each team simply for redundancy.

      Was this post helpful? thumb_up thumb_down
    • Try using Powershell for that purpose. The output may be more accurate and similar between different Windows Server versions which is not always the case with GUI.

      Powershell
      Get-WmiObject -Class Win32_NetworkAdapter | `
      Where-Object { $_.Speed -ne $null -and $_.MACAddress -ne $null } | `
      Format-Table -Property SystemName,Name,NetConnectionID,@{Label='Speed(GBps)'; Expression = {$_.Speed/1GB}},Speed
      

      Depending on your Powershell configuration you may need to adjust it slightly so the command above works correctly https://www.hyper-v.io/powershell-commands-scripts-not-work-can-fix/.

      Was this post helpful? thumb_up thumb_down

    Read these next...