Hyper‑V networking.
We need to understand some points about the Hyper‑V network
adapter and Hyper‑V virtual switches.
First of all, the virtual network adapter,
this is going to be the software interface that's attached to each of your VMs,
and then you'll also have a logical software adapter on the Hyper‑V host,
in fact,
you might have more than one if you've deployed multiple virtual switches.
SR‑IOV, stands for single root input/output virtualization,
is a way to dramatically increase throughput by allowing
your virtual machines to bypass the virtual switch and
address a hardware NIC in your host.
Now that involves configuration in your host hardware,
as well as in your virtual machine.
You just need to know what those initials mean.
Just basically,
it's going to give you enhanced network performance if
you have multiple NICs in your server, and you have that business need.
More to the point for our exam objectives,
we need to know about the three types of virtual switches.
There is the external switch that gives your guest
VMs access to the physical network, in other words,
the same network that the host is on.
So if you're using dynamic host configuration protocol on your host network,
then in an external switch scenario, your VMs will pick up IPs in that range,
and if your host network has internet access,
that would give your Hyper‑V VMs internet access.
Now internal switch is not going to involve the internet,
this is where the guest VMs can communicate only
with the host and with other VMs.
And lastly,
the private switch is VMs only where the VMs can't
even communicate with the host.
You can, in fact,
have more than one switch on the same Hyper‑V host if your needs dictate.
Another thing we can do with Hyper‑V for enhancing network performance actually,
NIC Teaming not only gives you enhanced throughput,
but also provides high availability for your virtual machines networking stack.
This is where you can group between 1 and 32 physical network
interfaces on your host into 1 or more software vNICs,
virtual NICs, that you attach to your virtual machines.
Like I mentioned, the advantages of NIC Teaming are both speed,
as well as fault tolerance, particularly the fault tolerance piece.
So you might have say two physical network interfaces that
you've combined into a single software interface,
and you have a web server VM, let's say,
that's using that software team interface,
well, if on the hardware host, one of those two interfaces,
the physical interfaces goes belly up,
your VM is still in business because the other healthy
physical NIC is still in that team.
You see the idea?
We don't have to deep dive too much on setting up NIC teaming.
Let me show you the process from a very high level.
You define the NIC team on the Hyper‑V host,
you can do so right in the server manager utility.
You'll also need to create an external switch, and note that when you do that,
you need to associate the Hyper‑V external switch
with one of the hosts adapters, and when you create a team,
the team interface will show up as an MS network adapter multiplexor driver.
Then you create your vNICs, you do that programmatically with PowerShell,
and then, lastly, you can attach those virtual network interfaces to Hyper‑V VMs, that's the high‑level process.