In the Hyper-V Manager GUI you will not find a way to define a trunk on an vNIC attached to a vSwitch. Trunking & VLAN’s are the way we deal with this in the network hardware world and we can do the same in Hyper-V. As you can imagine when doing redundant (teaming) cabling with HA load balancers you’re consuming 10Gbps ports and not all VLANs warrant a dedicated 10Gbps uplink, even if you had ‘m. I for one have used this on 10Gbps ports on bot physical and virtual load balancers in the uplink to the switches. This leads us to trunking with Hyper-V networking So even, before you run out of physical ports on your Hyper-V host to work with we leverage them to mimic the real live environment. These tend to be limited in usable ports in real life. In my experience I use trunking in Hyper-V mostly to mimic real world scenarios where trunking is used (firewall, routers, load balancers). Networking means you’ll you’ll be dealing with Link Aggregation Groups, Trunking, MLAG, routing, LACP … in short the tools of the trade when doing networking. This is especially true when using virtual network appliances. When doing lab work, or real life implementations you’ll need to go beyond the basic 101 stuff to build solutions every now and then.