1
00:00:01,140 --> 00:00:01,440
All right,

2
00:00:01,440 --> 00:00:06,510
let's work a bit with Hyper‑V switches and Hyper‑V virtual network adapters.

3
00:00:06,510 --> 00:00:08,780
Let's go to Hyper‑V Manager,

4
00:00:08,780 --> 00:00:12,230
and let's right‑click ARC2 and go to Virtual Switch

5
00:00:12,230 --> 00:00:14,140
Manager from the shortcut menu.

6
00:00:14,140 --> 00:00:17,270
We created an External Switch earlier in this course,

7
00:00:17,270 --> 00:00:19,440
and as I mentioned, when you do that,

8
00:00:19,440 --> 00:00:23,690
you associate that External Switch with one and only one of

9
00:00:23,690 --> 00:00:26,650
the host server's physical network adapters.

10
00:00:26,650 --> 00:00:29,930
If you've got a NIC team defined at the operating system level,

11
00:00:29,930 --> 00:00:32,140
then you'll have that multiplexer option.

12
00:00:32,140 --> 00:00:35,800
In my case, I just have the Hyper‑V network adapter.

13
00:00:35,800 --> 00:00:38,820
But there's two other options, internal and private.

14
00:00:38,820 --> 00:00:43,320
Private, in my experience, is a pretty limited use case, almost always.

15
00:00:43,320 --> 00:00:45,060
I can't think of an exception, actually,

16
00:00:45,060 --> 00:00:48,370
where I wouldn't want to communicate between host and VMs.

17
00:00:48,370 --> 00:00:51,470
So what we'll do is we'll go back to Virtual Switch Manager,

18
00:00:51,470 --> 00:00:53,330
I don't know why I closed the dialog,

19
00:00:53,330 --> 00:00:57,300
and let's create a new virtual network switch that uses internal,

20
00:00:57,300 --> 00:01:01,980
and let's click Create Virtual Switch, and I'll call this Internal Switch.

21
00:01:01,980 --> 00:01:04,460
It's connected to the internal network.

22
00:01:04,460 --> 00:01:07,050
Now, one thing that takes some getting used to,

23
00:01:07,050 --> 00:01:12,590
if you're familiar with ESXi, which is VMware and VMware Workstation,

24
00:01:12,590 --> 00:01:17,540
if you've used the desktop hypervisor, is that with VMware products,

25
00:01:17,540 --> 00:01:21,100
you get full access to the underlying networks,

26
00:01:21,100 --> 00:01:24,190
the private IP address ranges that are used.

27
00:01:24,190 --> 00:01:27,490
Unfortunately, we don't have that flexibility here.

28
00:01:27,490 --> 00:01:30,910
Look in the exercise files because I give you some docs links.

29
00:01:30,910 --> 00:01:35,350
Hyper‑V will look to see if there's going to be a conflict between the

30
00:01:35,350 --> 00:01:38,500
range that it automatically selects and your host,

31
00:01:38,500 --> 00:01:41,400
and if so, it will choose another private range,

32
00:01:41,400 --> 00:01:45,130
but you don't get anywhere near the flexibility that you do with VMware.

33
00:01:45,130 --> 00:01:46,440
That's unfortunate.

34
00:01:46,440 --> 00:01:48,480
So now that we have that Internal Switch,

35
00:01:48,480 --> 00:01:50,780
let's click OK, and we can make a change.

36
00:01:50,780 --> 00:01:55,000
Now let me boot up server1, and we'll go to Settings first,

37
00:01:55,000 --> 00:01:57,420
and let's take a look at its Network Adapter.

38
00:01:57,420 --> 00:02:01,690
We can see at a glance that it's connected to the External Switch right now.

39
00:02:01,690 --> 00:02:05,180
We can do bandwidth management, we can do virtual LANs,

40
00:02:05,180 --> 00:02:06,790
hardware acceleration,

41
00:02:06,790 --> 00:02:11,500
there's an SR‑IOV option where we would turn this on in the VM.

42
00:02:11,500 --> 00:02:14,600
Advanced Features, I showed you this in the previous lesson,

43
00:02:14,600 --> 00:02:17,660
you can adjust your MAC address there as a main idea.

44
00:02:17,660 --> 00:02:22,010
But I wanted to start just to quickly run an IP config so you can see

45
00:02:22,010 --> 00:02:24,960
what's happening when you're on an External Switch.

46
00:02:24,960 --> 00:02:27,730
Now at the same time on my Hyper‑V host,

47
00:02:27,730 --> 00:02:32,340
I'm going to open up my ncpa.cpl, my network properties,

48
00:02:32,340 --> 00:02:36,410
and we can see in this case I have the host's main interface,

49
00:02:36,410 --> 00:02:39,730
and then a virtual interface for each of my switches.

50
00:02:39,730 --> 00:02:41,770
Let me quickly sign into the VM.

51
00:02:41,770 --> 00:02:45,080
I changed the default administrator account name to Tim.

52
00:02:45,080 --> 00:02:47,460
So we've got our external and internal.

53
00:02:47,460 --> 00:02:50,080
Let's go to External and Details,

54
00:02:50,080 --> 00:02:56,520
and I'm here to tell you that my internet‑connected LAN uses the range 10.1.10.

55
00:02:56,520 --> 00:03:02,410
So we can see that this virtual interface has another 10.1.10 address,

56
00:03:02,410 --> 00:03:05,640
in addition to the main interface on this system,

57
00:03:05,640 --> 00:03:10,090
and my VMs will also, if they're connected to the External Switch,

58
00:03:10,090 --> 00:03:14,930
should via DHCP dynamic address allocation be able to pick up an address.

59
00:03:14,930 --> 00:03:17,790
So I can in the VM now do the same thing,

60
00:03:17,790 --> 00:03:21,030
ncpa.cpl, I have to spell it correctly, though,

61
00:03:21,030 --> 00:03:23,570
ncpa, I still did it again.

62
00:03:23,570 --> 00:03:24,390
There we go.

63
00:03:24,390 --> 00:03:27,590
And if we go into here and look at details,

64
00:03:27,590 --> 00:03:33,220
we've got 10.1.10, etc, and we've got, those are my Comcast DNS servers,

65
00:03:33,220 --> 00:03:34,860
so we have internet connectivity.

66
00:03:34,860 --> 00:03:39,360
We can see that listed on the Ethernet status dialog, as you can see.

67
00:03:39,360 --> 00:03:41,930
So let me close my VMConnect session.

68
00:03:41,930 --> 00:03:46,650
Then let's look here at the Internal Switch It says unidentified network.

69
00:03:46,650 --> 00:03:50,960
Let's go in here, take a look at our details, and we have an APIPA address.

70
00:03:50,960 --> 00:03:53,990
So whereas there's no, as I mentioned,

71
00:03:53,990 --> 00:03:57,860
there's not a central control plane in Hyper‑V for the

72
00:03:57,860 --> 00:04:02,100
virtual networks like VMware has, and I think that's a significant weakness,

73
00:04:02,100 --> 00:04:02,480
myself.

74
00:04:02,480 --> 00:04:06,260
That APIPA address might work in a pinch, but that's not what we need.

75
00:04:06,260 --> 00:04:09,440
So let's go to the properties of this adapter,

76
00:04:09,440 --> 00:04:14,220
and let me go to TCP/IPv4, and let me choose a non‑overlapping range.

77
00:04:14,220 --> 00:04:22,560
I'll do 192.168.200.200, 255.255.255, and we'll close out of all of those,

78
00:04:22,560 --> 00:04:25,240
and now we'll come back to the Settings of server1,

79
00:04:25,240 --> 00:04:27,640
we'll come down to the Network Adapter,

80
00:04:27,640 --> 00:04:29,840
and we'll connect it to our Internal Switch.

81
00:04:29,840 --> 00:04:31,430
We'll apply that change.

82
00:04:31,430 --> 00:04:35,500
We may need to reset the VM for this change to go into effect.

83
00:04:35,500 --> 00:04:37,700
Let me right‑click and Reset.

84
00:04:37,700 --> 00:04:40,930
And if we go to Networking here, once the VM is available,

85
00:04:40,930 --> 00:04:44,930
we should be able to see the Network Adapter is on the Internal Switch,

86
00:04:44,930 --> 00:04:47,800
it looks like it's just got basically the equivalent,

87
00:04:47,800 --> 00:04:49,970
yeah, there it is, the APIPA address,

88
00:04:49,970 --> 00:04:54,570
which is what Microsoft Windows will auto‑assign a machine

89
00:04:54,570 --> 00:04:57,050
when it can't get an IP address otherwise.

90
00:04:57,050 --> 00:04:58,380
So let me make a connection.

91
00:04:58,380 --> 00:05:03,850
And we'll just go ahead and do a static address allocation for this box now.

92
00:05:03,850 --> 00:05:06,170
Then we'll go back to our network properties,

93
00:05:06,170 --> 00:05:10,290
we'll go to Properties, TCP/IP, and it's 192.168.

94
00:05:10,290 --> 00:05:13,260
Did I say 200 and 201?

95
00:05:13,260 --> 00:05:14,430
Something like that.

96
00:05:14,430 --> 00:05:17,770
Now you'll notice that I'm pointedly ignoring DNS for now.

97
00:05:17,770 --> 00:05:18,490
Yeah.

98
00:05:18,490 --> 00:05:21,490
Let's open up a PowerShell prompt.

99
00:05:21,490 --> 00:05:24,200
Let me right‑click, open up an administrative PowerShell.

100
00:05:24,200 --> 00:05:27,150
Local host is coming back okay on IPv6.

101
00:05:27,150 --> 00:05:30,930
Let me do an ipconfig to remind myself of the address,

102
00:05:30,930 --> 00:05:35,040
and now let me do a ping IPv4 192.168.200.202.

103
00:05:35,040 --> 00:05:36,930
Okay.

104
00:05:36,930 --> 00:05:40,390
And lastly, let's see if we can reach up to the server 200.

105
00:05:40,390 --> 00:05:41,320
Yep, we can.

106
00:05:41,320 --> 00:05:45,240
So we now have private connectivity between our VMs,

107
00:05:45,240 --> 00:05:49,980
presumably, and our host, but it did require some manual intervention.

108
00:05:49,980 --> 00:05:51,740
It was not very cleanly done.

109
00:05:51,740 --> 00:05:51,890
Now,

110
00:05:51,890 --> 00:05:58,160
I'm sure that we could stand up DHCP and get to work on automating stand up DNS,

111
00:05:58,160 --> 00:06:01,910
you know, all of that kind of stuff, but there I am complaining a little bit.

112
00:06:01,910 --> 00:06:05,840
If you know me, I like to tell it as I see it with this technical stuff,

113
00:06:05,840 --> 00:06:11,000
but you might also read that as complaining. Your mileage may vary.