1
00:00:01,040 --> 00:00:03,340
Hyper‑V networking.

2
00:00:03,340 --> 00:00:06,670
We need to understand some points about the Hyper‑V network

3
00:00:06,670 --> 00:00:09,600
adapter and Hyper‑V virtual switches.

4
00:00:09,600 --> 00:00:12,010
First of all, the virtual network adapter,

5
00:00:12,010 --> 00:00:17,680
this is going to be the software interface that's attached to each of your VMs,

6
00:00:17,680 --> 00:00:22,520
and then you'll also have a logical software adapter on the Hyper‑V host,

7
00:00:22,520 --> 00:00:22,960
in fact,

8
00:00:22,960 --> 00:00:27,700
you might have more than one if you've deployed multiple virtual switches.

9
00:00:27,700 --> 00:00:32,240
SR‑IOV, stands for single root input/output virtualization,

10
00:00:32,240 --> 00:00:36,140
is a way to dramatically increase throughput by allowing

11
00:00:36,140 --> 00:00:39,510
your virtual machines to bypass the virtual switch and

12
00:00:39,510 --> 00:00:42,400
address a hardware NIC in your host.

13
00:00:42,400 --> 00:00:45,710
Now that involves configuration in your host hardware,

14
00:00:45,710 --> 00:00:47,660
as well as in your virtual machine.

15
00:00:47,660 --> 00:00:50,380
You just need to know what those initials mean.

16
00:00:50,380 --> 00:00:51,180
Just basically,

17
00:00:51,180 --> 00:00:54,390
it's going to give you enhanced network performance if

18
00:00:54,390 --> 00:00:58,470
you have multiple NICs in your server, and you have that business need.

19
00:00:58,470 --> 00:01:00,780
More to the point for our exam objectives,

20
00:01:00,780 --> 00:01:03,890
we need to know about the three types of virtual switches.

21
00:01:03,890 --> 00:01:06,630
There is the external switch that gives your guest

22
00:01:06,630 --> 00:01:09,550
VMs access to the physical network, in other words,

23
00:01:09,550 --> 00:01:11,640
the same network that the host is on.

24
00:01:11,640 --> 00:01:16,380
So if you're using dynamic host configuration protocol on your host network,

25
00:01:16,380 --> 00:01:22,070
then in an external switch scenario, your VMs will pick up IPs in that range,

26
00:01:22,070 --> 00:01:24,950
and if your host network has internet access,

27
00:01:24,950 --> 00:01:28,040
that would give your Hyper‑V VMs internet access.

28
00:01:28,040 --> 00:01:31,690
Now internal switch is not going to involve the internet,

29
00:01:31,690 --> 00:01:34,550
this is where the guest VMs can communicate only

30
00:01:34,550 --> 00:01:36,470
with the host and with other VMs.

31
00:01:36,470 --> 00:01:37,240
And lastly,

32
00:01:37,240 --> 00:01:41,060
the private switch is VMs only where the VMs can't

33
00:01:41,060 --> 00:01:43,440
even communicate with the host.

34
00:01:43,440 --> 00:01:44,430
You can, in fact,

35
00:01:44,430 --> 00:01:48,940
have more than one switch on the same Hyper‑V host if your needs dictate.

36
00:01:48,940 --> 00:01:53,420
Another thing we can do with Hyper‑V for enhancing network performance actually,

37
00:01:53,420 --> 00:01:56,560
NIC Teaming not only gives you enhanced throughput,

38
00:01:56,560 --> 00:02:01,360
but also provides high availability for your virtual machines networking stack.

39
00:02:01,360 --> 00:02:05,100
This is where you can group between 1 and 32 physical network

40
00:02:05,100 --> 00:02:09,650
interfaces on your host into 1 or more software vNICs,

41
00:02:09,650 --> 00:02:12,930
virtual NICs, that you attach to your virtual machines.

42
00:02:12,930 --> 00:02:16,990
Like I mentioned, the advantages of NIC Teaming are both speed,

43
00:02:16,990 --> 00:02:20,810
as well as fault tolerance, particularly the fault tolerance piece.

44
00:02:20,810 --> 00:02:24,970
So you might have say two physical network interfaces that

45
00:02:24,970 --> 00:02:28,030
you've combined into a single software interface,

46
00:02:28,030 --> 00:02:30,790
and you have a web server VM, let's say,

47
00:02:30,790 --> 00:02:33,310
that's using that software team interface,

48
00:02:33,310 --> 00:02:37,040
well, if on the hardware host, one of those two interfaces,

49
00:02:37,040 --> 00:02:39,300
the physical interfaces goes belly up,

50
00:02:39,300 --> 00:02:42,860
your VM is still in business because the other healthy

51
00:02:42,860 --> 00:02:44,970
physical NIC is still in that team.

52
00:02:44,970 --> 00:02:45,930
You see the idea?

53
00:02:45,930 --> 00:02:49,100
We don't have to deep dive too much on setting up NIC teaming.

54
00:02:49,100 --> 00:02:51,750
Let me show you the process from a very high level.

55
00:02:51,750 --> 00:02:54,400
You define the NIC team on the Hyper‑V host,

56
00:02:54,400 --> 00:02:57,240
you can do so right in the server manager utility.

57
00:02:57,240 --> 00:03:01,320
You'll also need to create an external switch, and note that when you do that,

58
00:03:01,320 --> 00:03:04,770
you need to associate the Hyper‑V external switch

59
00:03:04,770 --> 00:03:08,490
with one of the hosts adapters, and when you create a team,

60
00:03:08,490 --> 00:03:13,640
the team interface will show up as an MS network adapter multiplexor driver.

61
00:03:13,640 --> 00:03:18,340
Then you create your vNICs, you do that programmatically with PowerShell,

62
00:03:18,340 --> 00:03:27,000
and then, lastly, you can attach those virtual network interfaces to Hyper‑V VMs, that's the high‑level process.