Hyper-V networking and NIC teaming - catch 22?

Question

Hyper-V networking and NIC teaming - catch 22?

Calum Morrison 1

I'm trying to get to grips with NIC teaming and Hyper-V but there seems to be a catch 22 situation on my host. It's an HP box so has 4 LOM - Lights Out Module - ports (one in use) and four Broadcom PCIe NICs - also one in use. This is a test rig for the production box that has four of the latter connected - it's a setup I've inherited, coming from a VMWare background.

As I understand it, I the PCIe NIC will become a Virtual Switch under Hyper-V and the best practice is to team the NICs together however, the NICs don't show up in the the NIC teaming window unless they are assigned to a virtual switch and, when assigned to a virtual switch can't be teamed.

What am I missing? I'm finding the whole area of networking in Hyper-V a bit confusing so go easy with me ;-)

thanks

2 answers

Your answer

Answer 1

Anonymous

Something here could help.
https://www.altaro.com/hyper-v/virtual-networking-configuration-best-practices/

--please don't forget to upvote and Accept as answer if the reply is helpful--

Calum Morrison 1 Reputation point

2022-12-20T16:52:44.757+00:00

thanks for the link - that was one of the articles I read before posting here tbh though ;-)

Will take another look through it.
Eric Siron 1,586 Reputation points MVP

2022-12-20T21:10:20.487+00:00

That article is old. It's not useless, but the teaming situation changed dramatically in WS2016+. Everything there still logically applies and the commands still work, but switch-embedded teaming is easier to implement.

Try this article instead, I've linked right to the SET portion: https://www.altaro.com/hyper-v/complete-guide-hyper-v-networking/#Working_with_Hyper-V_Switch_Embedded_Teams

The original process was to first create an LBFO team and then create a virtual switch on the logical team NIC. SET builds a team and a virtual switch in a single pass. The VMware concept of networks does not carry through to Hyper-V. You'll get a virtual switch out of the SET creation. You can then create virtual adapters for the management OS so that it can directly communicate on the network (happens automatically unless you specify otherwise). Virtual machines are created with their network adapters by default, which you must connect to the virtual switch. You can make changes to these and add/remove as needed, so nothing is irreversible. If you need a virtual adapter to belong to a VLAN, you assign that to the virtual adapter instead of placing the virtual adapter into a network like you would on ESX.

Answer 2

Hi,

Thank you for posting your query.

Kindly follow the steps provided below to resolve your issue.

This document refers to the section titled “Hyper-V Networking” and discusses new networking features included in Windows Server® 2012 including load balancing and failover, single-root I/O virtualization (SR-IOV), Quality of Service (QoS) bandwidth management, and the new extensible Hyper-V® virtual switch.

Go to this link for your reference and other troubleshooting procedures https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn641211(v=ws.11)

Do not hesitate to message us if you need further assistance.

If the answer is helpful kindly click "Accept as Answer" and up vote it.

Share via

Hyper-V networking and NIC teaming - catch 22?

2 answers

Your answer