Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

Hyper-V-VmSwitch event 106

$
0
0

Hi everybody,

I have a problem with my nic teaming in Hyper-V.
In eventlog I do have events with id 106:

Available processor sets of the underlying physical NICs belonging to the LBFO team NIC /DEVICE/{GUID} (Friendly Name: Microsoft Network Adapter Multiplexor Driver #2) on switch GUID (Friendly Name: HS-vSwitch) are not configured correctly. Reason: The processor sets overlap when LBFO is configured with sum-queue mode.

I have read the following blogs:

http://blogs.technet.com/b/networking/archive/2013/09/24/vmq-deep-dive-1-of-3.aspx
http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-2-of-3.aspx
http://blogs.technet.com/b/networking/archive/2013/10/22/vmq-deep-dive-3-of-3.aspx

I do have 2 CPU-Sockets with 12 cores per socket and hyperthreading enabled.
That makes 48 logical processors.
My NIC-Team is switchindependent with "Hyper-V Port" load balancing mode.

As far as I understand I have to configure the VMQs to use seperate logical processors (lp) per NIC.
I do this with the following commands in powershell:

Set-NetAdapterVMQ –Name NIC01 –BaseProcessorNumber 0 –MaxProcessors 24
Set-NetAdapterVMQ –Name NIC02 –BaseProcessorNumber 24 –MaxProcessors 24

After this command I still get the error in eventlog :(

I tried a bit after that and used the following commands:

Set-NetAdapterVMQ –Name NIC01 –BaseProcessorNumber 0 –MaxProcessors 12
Set-NetAdapterVMQ –Name NIC02 –BaseProcessorNumber 24 –MaxProcessors 12

There should be no overlapping anymore but error is still there.

My NICs are VMQ enabled. This is verified with get-netadaptervmq and the above settings are correctly displayed (BaseVmqProcessor and MaxProcessors).

What am I getting wrong?

Thanks for your help.

Greetings from germany,

torsten


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>