The server manufacturer support team will be your best resource to debug this issue with your new hardware.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have New windows server 2019 With Hyper-V hosting installed and NIC Team.
My issue is I'm getting this Event ID 106
Event ID 106 , "Available processor sets of the underlying physical NICs belonging to the LBFO team NIC /DEVICE/{48F95971-A3F0-4C21-9906-7F9B497BF548} (Friendly Name: Microsoft Network Adapter Multiplexor Driver #2) on switch FE9E3F5E-1E59-4F12-8CE5-3129157B038F (Friendly Name: Microsoft Network Adapter Multiplexor Driver #2 - Virtual Switch) are not configured correctly. Reason: The processor sets overlap when LBFO is configured with sum-queue mode."
When I use the Set netadpatevmq it will fix the 106 and give me Event is 113
"Failed to allocate VMQ for NIC 4CA31743-380C-4CFD-960D-F1DD0336098B (Friendly Name: Microsoft Network Adapter Multiplexor Driver #2 - Virtual Switch) on switch FE501B4B-1282-4041-B877-87CCC6CFF19F (Friendly Name: Microsoft Network Adapter Multiplexor Driver #2 - Virtual Switch). Reason - Failed to set the VMQ affinity processor for NIC. Status = {Operation Failed}
The requested operation was unsuccessful."
The issue that I have when I fix the 113 I get back the 106???
I'm back at event ID 106 that I need to get it fix since I will deploy this server in next week into production.
My server is Intel server with
What I have is duel processors 12 core/ 24 logic each for total of 24 and 48 respectively.
I have 2 SPF ( Ethernet and ethernet3) 10 GB Nic's that I'm using as NIC Team for total of 10 Gb.
NIC team is set
Teaming Mode "Switch Independent"
Load Balancing Mode "Dynamic"
Standby adapter " none"
Name InterfaceDescription Enabled BaseVmqProcessor MaxProcessors NumberOfReceive
Queues
Ethernet 4 Intel(R) Ethernet Connection...#2 False 0:0 32 93
VM Team Microsoft Network Adapter Mu...#2 True 0:0 187
Managment Team Microsoft Network Adapter Mult... False 0:0 186
Ethernet Intel(R) Ethernet Connection X... True 0:0 32 94
Ethernet3 Intel(R) Ethernet Connection...#2 True 0:0 32 93
Ethernet 2 Intel(R) Ethernet Connection X... False 0:0 32 93
get-netadapterrss
Name : VM Team
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #2
Enabled : True
NumberOfReceiveQueues :
Profile :
BaseProcessor: [Group:Number] : :
MaxProcessor: [Group:Number] : :
MaxProcessors :
RssProcessorArray: [Group:Number/NUMA Distance] :
IndirectionTable: [Group:Number] :
Name : Ethernet
InterfaceDescription : Intel(R) Ethernet Connection X722 for 10GbE SFP+
Enabled : True
NumberOfReceiveQueues : 8
Profile : NUMAStatic
BaseProcessor: [Group:Number] : :0
MaxProcessor: [Group:Number] : :10
MaxProcessors : 32
RssProcessorArray: [Group:Number/NUMA Distance] :
IndirectionTable: [Group:Number] :
Name : vEthernet (Microsoft Network Adapter Multiplexor Driver #2 - Virtual
Switch)
InterfaceDescription : Hyper-V Virtual Ethernet Adapter
Enabled : True
NumberOfReceiveQueues : 8
Profile : ClosestStatic
BaseProcessor: [Group:Number] : :0
MaxProcessor: [Group:Number] : :63
MaxProcessors : 8
RssProcessorArray: [Group:Number/NUMA Distance] :
IndirectionTable: [Group:Number] :
Name : Ethernet3
InterfaceDescription : Intel(R) Ethernet Connection X722 for 10GbE SFP+ #2
Enabled : True
NumberOfReceiveQueues : 8
Profile : NUMAStatic
BaseProcessor: [Group:Number] : :0
MaxProcessor: [Group:Number] : :
MaxProcessors : 32
RssProcessorArray: [Group:Number/NUMA Distance] :
IndirectionTable: [Group:Number] :
Thanks,
Remon
The server manufacturer support team will be your best resource to debug this issue with your new hardware.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hi there,
You can use the Set-NetAdapterVmq Windows PowerShell command to configure each network adapter in your team to use different processors. (Because LBFO teaming is set up for Sum of Queues, the network adapters in the team have to use nonoverlapping processor sets.)
You need to install the hotfix in KB article 3031598 to resolve other known issues after making these configuration changes.
Here is a link for a detailed description of the process that you must follow.
Event ID 106 when a Hyper-V virtual switch is bound to an LBFO team
https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/event-id-106-hyper-v-virtual-switch-bound-lbfo-team
---------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer--