All right,
let's work a bit with Hyper‑V switches and Hyper‑V virtual network adapters.
Let's go to Hyper‑V Manager,
and let's right‑click ARC2 and go to Virtual Switch
Manager from the shortcut menu.
We created an External Switch earlier in this course,
and as I mentioned, when you do that,
you associate that External Switch with one and only one of
the host server's physical network adapters.
If you've got a NIC team defined at the operating system level,
then you'll have that multiplexer option.
In my case, I just have the Hyper‑V network adapter.
But there's two other options, internal and private.
Private, in my experience, is a pretty limited use case, almost always.
I can't think of an exception, actually,
where I wouldn't want to communicate between host and VMs.
So what we'll do is we'll go back to Virtual Switch Manager,
I don't know why I closed the dialog,
and let's create a new virtual network switch that uses internal,
and let's click Create Virtual Switch, and I'll call this Internal Switch.
It's connected to the internal network.
Now, one thing that takes some getting used to,
if you're familiar with ESXi, which is VMware and VMware Workstation,
if you've used the desktop hypervisor, is that with VMware products,
you get full access to the underlying networks,
the private IP address ranges that are used.
Unfortunately, we don't have that flexibility here.
Look in the exercise files because I give you some docs links.
Hyper‑V will look to see if there's going to be a conflict between the
range that it automatically selects and your host,
and if so, it will choose another private range,
but you don't get anywhere near the flexibility that you do with VMware.
That's unfortunate.
So now that we have that Internal Switch,
let's click OK, and we can make a change.
Now let me boot up server1, and we'll go to Settings first,
and let's take a look at its Network Adapter.
We can see at a glance that it's connected to the External Switch right now.
We can do bandwidth management, we can do virtual LANs,
hardware acceleration,
there's an SR‑IOV option where we would turn this on in the VM.
Advanced Features, I showed you this in the previous lesson,
you can adjust your MAC address there as a main idea.
But I wanted to start just to quickly run an IP config so you can see
what's happening when you're on an External Switch.
Now at the same time on my Hyper‑V host,
I'm going to open up my ncpa.cpl, my network properties,
and we can see in this case I have the host's main interface,
and then a virtual interface for each of my switches.
Let me quickly sign into the VM.
I changed the default administrator account name to Tim.
So we've got our external and internal.
Let's go to External and Details,
and I'm here to tell you that my internet‑connected LAN uses the range 10.1.10.
So we can see that this virtual interface has another 10.1.10 address,
in addition to the main interface on this system,
and my VMs will also, if they're connected to the External Switch,
should via DHCP dynamic address allocation be able to pick up an address.
So I can in the VM now do the same thing,
ncpa.cpl, I have to spell it correctly, though,
ncpa, I still did it again.
There we go.
And if we go into here and look at details,
we've got 10.1.10, etc, and we've got, those are my Comcast DNS servers,
so we have internet connectivity.
We can see that listed on the Ethernet status dialog, as you can see.
So let me close my VMConnect session.
Then let's look here at the Internal Switch It says unidentified network.
Let's go in here, take a look at our details, and we have an APIPA address.
So whereas there's no, as I mentioned,
there's not a central control plane in Hyper‑V for the
virtual networks like VMware has, and I think that's a significant weakness,
myself.
That APIPA address might work in a pinch, but that's not what we need.
So let's go to the properties of this adapter,
and let me go to TCP/IPv4, and let me choose a non‑overlapping range.
I'll do 192.168.200.200, 255.255.255, and we'll close out of all of those,
and now we'll come back to the Settings of server1,
we'll come down to the Network Adapter,
and we'll connect it to our Internal Switch.
We'll apply that change.
We may need to reset the VM for this change to go into effect.
Let me right‑click and Reset.
And if we go to Networking here, once the VM is available,
we should be able to see the Network Adapter is on the Internal Switch,
it looks like it's just got basically the equivalent,
yeah, there it is, the APIPA address,
which is what Microsoft Windows will auto‑assign a machine
when it can't get an IP address otherwise.
So let me make a connection.
And we'll just go ahead and do a static address allocation for this box now.
Then we'll go back to our network properties,
we'll go to Properties, TCP/IP, and it's 192.168.
Did I say 200 and 201?
Something like that.
Now you'll notice that I'm pointedly ignoring DNS for now.
Yeah.
Let's open up a PowerShell prompt.
Let me right‑click, open up an administrative PowerShell.
Local host is coming back okay on IPv6.
Let me do an ipconfig to remind myself of the address,
and now let me do a ping IPv4 192.168.200.202.
Okay.
And lastly, let's see if we can reach up to the server 200.
Yep, we can.
So we now have private connectivity between our VMs,
presumably, and our host, but it did require some manual intervention.
It was not very cleanly done.
Now,
I'm sure that we could stand up DHCP and get to work on automating stand up DNS,
you know, all of that kind of stuff, but there I am complaining a little bit.
If you know me, I like to tell it as I see it with this technical stuff,
but you might also read that as complaining. Your mileage may vary.