WS2019 cluster Error 106 - available processor set of the underlying physical NICs not configured correctly because processor sets overlap when LBFO is configured with sum-queue mode

Question

Hello!
In event viewer i have this error in my WS2019 cluster of two nodes. Available processor sets of the underlying physical NICs belonging to the LBFO team NIC /DEVICE/{1A5602OS02-H2E4-46C6-09OA-1WEON5473890} (Friendly Name: Microsoft Network Adapter Multiplexor Driver #3) on switch 098BHS7E-D5R6-9O34-N2E4-12O9DGJU73W4 (Friendly Name: VM_NETWORK) are not configured correctly. Reason: The processor sets overlap when LBFO is configured with sum-queue mode.

I've read something here: https://charbelnemnom.com/the-available-processor-sets-of-the-underlying-physical-nics-belonging-to-the-lbfo-team-nic-are-not-configured-correctly-hyperv-vmq-rss-lbfo/ about this error but I do not know is it applicable to WS2019. If yes, do I need to set it up or I can go without this configuration? Will there be any problems if I do not configure it? Is any other way to resolve this, maybe some other network configuration. My network team configuration inside servers is:
2x10Gb Management, 2x10Gb HeartBeat, 2x10Gb VM_NETWORK.

Thank you!

Best regards.

Answer 1

Hi there,

If Error 106 says, "Reason: The processor sets overlap when LBFO is configured with sum-queue mode," you have to 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 can also try additional troubleshooting steps from this article 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--

Answer 2

Thank you for your answer! What could potentially happen if I don't configure it?

Your link is for WS2012, I don't know is it also applicable to WS2019?

Best regards!