Hyper V Windows Server 2022 DL380 Gen11 Virtual Switch LinkSpeed

[FayeM]

Hi all.

we have configured a new Hyper-V infrastructure (Windows Server 2022) two DL380 Gen11 servers. We noticed that the Virtual Switch, consisting of 4 x 1Gbps interfaces, shows LinkSpeed at 1Gbps instead of 4Gbps (total). Does anyone have experience with this setting?

Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
---- -------------------- ------- ------ ---------- ---------
Prod3 Broadcom NetXtreme Gigabit Ethernet #2 15 Up 04-32-01-5F-C1-31 1 Gbps
Prod1 Broadcom NetXtreme Gigabit Ethernet 14 Up 04-32-01-5F-C1-33 1 Gbps
Prod4 Broadcom NetXtreme Gigabit Ethernet #4 11 Up 04-32-01-5F-C1-30 1 Gbps
Prod2 Broadcom NetXtreme Gigabit Ethernet #3 3 Up 04-32-01-5F-C1-32 1 Gbps

Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
---- -------------------- ------- ------ ---------- ---------
vEthernet (vSwitchProd) Hyper-V Virtual Ethernet Adapter 18 Up 04-32-01-5F-C1-33 1 Gbps

Name : vSwitchProd
Id : 45a2864b-422a-4ae8-90d5-2fc2ecda6e98
Notes :
Extensions : {Microsoft Windows Filtering Platform, Microsoft NDIS Capture}
BandwidthReservationMode : Absolute
PacketDirectEnabled : False
EmbeddedTeamingEnabled : True
AllowNetLbfoTeams : False
IovEnabled : False
SwitchType : External
AllowManagementOS : True
NetAdapterInterfaceDescription : Teamed-Interface
NetAdapterInterfaceDescriptions : {Broadcom NetXtreme Gigabit Ethernet #2, Broadcom NetXtreme Gigabit
Ethernet #3, Broadcom NetXtreme Gigabit Ethernet #4, Broadcom
NetXtreme Gigabit Ethernet}
NetAdapterInterfaceGuid : {7f7c6ab7-a3e9-4c2c-9e61-f2085a3694a5,
23af38c1-abaa-4313-b577-f03246f12f8c,
507c0681-e890-4224-b51f-5d96a586dad5,
6eecd0cc-fd6d-4549-bc15-566a003bfb34}
IovSupport : False
IovSupportReasons : {This network adapter does not support SR-IOV.}
AvailableIPSecSA : 0
NumberIPSecSAAllocated : 0
AvailableVMQueues : 0
NumberVmqAllocated : 0
IovQueuePairCount : 0
IovQueuePairsInUse : 0
IovVirtualFunctionCount : 0
IovVirtualFunctionsInUse : 0
PacketDirectInUse : False
DefaultQueueVrssEnabledRequested : True
DefaultQueueVrssEnabled : False
DefaultQueueVmmqEnabledRequested : True
DefaultQueueVmmqEnabled : False
DefaultQueueVrssMaxQueuePairsRequested : 16
DefaultQueueVrssMaxQueuePairs : 0
DefaultQueueVrssMinQueuePairsRequested : 1
DefaultQueueVrssMinQueuePairs : 0
DefaultQueueVrssQueueSchedulingModeRequested : StaticVrss
DefaultQueueVrssQueueSchedulingMode : Dynamic
DefaultQueueVrssExcludePrimaryProcessorRequested : False
DefaultQueueVrssExcludePrimaryProcessor : False
SoftwareRscEnabled : True
RscOffloadEnabled : False
BandwidthPercentage : 10
DefaultFlowMinimumBandwidthAbsolute : 100000000
DefaultFlowMinimumBandwidthWeight : 0
CimSession : CimSession: .
IsDeleted : False
DefaultQueueVmmqQueuePairs : 0
DefaultQueueVmmqQueuePairsRequested : 16

Thanks for your feedback

Regards

Faye

[shiva_jr]

Hi @FayeM , 
Note that, if the physical NIC card has 4 ports of 1Gbps. Then, they will work as 1Gbps ports only. You configured the ports as ‘Teamed-Interface’ which makes them to work as load balancing, but you can’t get consolidated link speed of 4Gbps in 1 port.]

Verify the following -

• Setting the link speed to ‘Auto-negotiation’ and check the speed.
• Verify both physical NIC and virtual switch will support the required speed.
• Verify the Virtual machine should not be configured with ‘Legacy NICs’ that are limited to the less speed.
  
  Regards,
  Shiva_jr

[support_s]

System recommended content:

1. Implementing Microsoft Windows Server Hyper-V Release Candidate 1 (RC1) on HP ProLiant servers

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[FayeM]

Hi Shiva_jr, thanks for your message.

1) all Network are set to “Auto-negotiation”  (speed & duplex option)

2) Yes is supported

3) No Legacy NICs are userd

Have you other suggestions?

Thanks! Regards

Faye

[Cali]

Hi,

you need to configure LACP on the Server and Switch also.
The default is "Switch independent" and gives not 4GB.

Please try this:

First, create NIC teaming using Server Manager with LACP mode and dynamic load balancing.

Execute the following PowerShell command to create the virtual switch based on the teaming:

New-VMSwitch -Name "VMSWITCH-1" -NetAdapterName "SR-LAG-1" -AllowNetLbfoTeams $true -AllowManagementOS $true

Open Server Manager, select "Local Server," and under NIC Teaming, click "Disabled." Then click "Tasks" and choose "New Team" to configure NIC teaming.

If you encounter issues with NIC teaming applying a private connection, try disabling one of the NICs and then re-enabling it.

Cali

[FayeM]

Thanks Cali, this is exactly the right point!

Regards

Faye

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".