1

I'm a newbie here. I have a Windows 2019 server with two 10G fiber lines. I created a NIC team for the host with LACP / Dynamic mode.

Can I use this team for both the host and Hyper-v VMs? Or do I need a separate physical NIC and lines for VMs?

I encountered an error when I ran this command:

New-VMSwitch -Name External -NetAdapterName "NIC1","NIC2" -EnableEmbeddedTeaming $true

The error shows "A protocol on the network adapter prevented it from binding to the virtual switch".

Please help.

Improve this question
6
  • What happens if you try to create a virtual switch using the team from the Hyper-V GUI management console?
    – joeqwerty
    Nov 17 at 21:44
  • In Hyper-V GUI management console, I selected "Microsoft Network adapter multiplex Driver", and created it. It went through, but the host network connection became offline. I deleted the virtual switch I had just created, and the host connection returned online. It looks like a NIC team can't be shared with both.
    – Jay
    Nov 17 at 21:55
  • When you created the virtual switch did you enable the option "Allow management operating system to share this network adapter"?
    – joeqwerty
    Nov 17 at 23:01
  • As an aside, you can create virtual switches that are shared with the management OS or not shared. It's up to you. If you create a virtual switch that is not shared with the management OS then you need a dedicated NIC for the management OS.
    – joeqwerty
    Nov 17 at 23:03
  • -AllowManagementOS "Specifies whether the parent partition (i.e. the management operating system) is to have access to the physical NIC bound to the virtual switch to be created." When a new switch is created, the Internet protocols are removed from the physical adapters. If those are in use, it may produce unexpected results. Additionally, if you created a "legacy" team, those were deprecated 10 years ago. Switch Embedded Teams are preferred. learn.microsoft.com/en-us/powershell/module/hyper-v/…
    – Greg Askew
    Nov 19 at 15:16

2 Answers 2

Reset to default
1

You can - but bandwidth can be a problem. A SET (Switch embedded team) with QoS profiles is a must - as is a not low-end switch (10g++). 2022 upward strongly adviced.

Improve this answer
-1

Do you know what the purpose is of NIC Teaming and where it's used for?

NIC Teaming is usually done on the Hyper-v host. In a VM just add multiple virtual nics. NIC Teaming relies as far as I know on the psychical nic, so I think with a virtual nic you might get very strange and undesired effects.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .