So in this video, let's head over to the vSphere client.
Just to verify we have ESXi host to work with.
And I currently have some ESXi hosts
which are connected over here on this management segment.
I also have my vCenter here as well.
So my vCenter server is at dot 111.
And then I have some ESXi hosts here at dot 101 and dot 102
and et cetera.
In fact, I have six ESXi hosts that are sitting here
on this management network under the control
of this vCenter.
So they go ahead and redraw this just a little bit WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So they go ahead and redraw this just a little bit
to represent I have more than just two hosts here.
So I'll put a dot ETC
and then I'll put the vCenter right there at dot 111.
Also as a heads up, I intentionally removed
NSX manager from the equation.
Just to help reinforce the concept
that this infrastructure we're building
for the NSX application platform
and the Kubernetes that it runs on,
this is all implemented on VLANs
with traditional routers and switches.
And in combination with that, we're using vSphere
that is also aware of those vLANs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that is also aware of those vLANs.
So here's our little topology in the upper right hand corner.
And here is the vSphere client.
One of the very first things I'd recommend is that
if you can, please do a remediation on your clusters
just to make sure that everybody is up to snuff.
So if we go here to the cluster
and then over here we click on updates,
we can confirm that we are all updated.
In fact, let me put this right down here.
So that's likely to get in the way down there.
So and for these ESXi hosts, if we go to the networking tab here
and we click on the distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we click on the distributed switch
and we get a configure.
One of my favorite views here is the topology view.
Then we get on here to VLAN 11 and just expand that.
It's showing us here the IP addresses
for each of our six hosts on that management network,
which is VLAN 11.
And the vCenter server appliance
is actually running on a different system,
but it's connected logically here to VLAN 11 as well,
right there.
So back here in the hosting clusters view,
let's create a new cluster.
So right click and we'll create a new cluster
and we'll call this cluster host for nap. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and we'll call this cluster host for nap.
We'll go ahead and use DRS on this cluster.
So for now let me go ahead and move that little topology
out of the way and let me click on next.
And we'll be using this latest and greatest version
of ESXi as the image and we'll click on next
and click on finish.
So if we look at recent tasks that is now done,
there is our new cluster host for nap.
And let's go ahead because these are all maintenance mode.
Let's go ahead and put in blue four, five and six.
Let's drag them up and put them into that new cluster
and click on okay for each one of them.
There's four, there's five and here is six and click on okay. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There's four, there's five and here is six and click on okay.
And there they are.
And let's also before I bring them out of maintenance mode,
I was gonna go ahead and with that cluster selected,
we'll click on updates and go ahead and click on check
compliance.
And then if we need remediation, we'll go ahead
and remediate.
I just wanna make sure before we get to the point
of adding NSX and adding our workloads
as part of a Kubernetes cluster that all of our ESXi hosts
are starting from a really good starting point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
are starting from a really good starting point.
So for the recent tasks, we're currently checking compliance
as shown right there.
And that is done fantastic and it shows as compliant.
So all three of those hosts four, five and six
in this host for nap cluster, they're all using
the exact same version of ESXi of the hypervisor,
which is fantastic.
And they also have some shared storage they can all get to.
So let me go ahead and take them out of maintenance mode,
each one of them like that, right click maintenance mode,
exit, right click maintenance mode and exit. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
exit, right click maintenance mode and exit.
And then this also verifies shared storage.
So if we go to the storage tab here,
if we take a look at ISCSI one,
all six hosts have access to that storage
and ISCSI two, all six hosts have access to that storage.
And this is a three raid five,
all six once again have access to that shared storage.
Fantastic.
So next, let's take a look at the networking
tab, and hopefully bring back our little topology right here.
And let's go to the networking tab
inside the VCR client,
distributed switch called VDS one.
And I'm going to once again move that topology
right down here out of the way, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
right down here out of the way,
or hopefully out of the way a little more.
So for this distributed switch, if we click on hosts,
here it shows us that all six hosts
have been configured to use that distributed switch.
And also I've got some port groups that are being used
specifically for ISCSI access and for provisioning
and for V motion, and they have respective VM kernel adapters
to support that as well.
So here is the management network
and that is this green one right here
that they are connected to.
However, what we don't yet have
is we don't have the port groups associated with the VLAN 12 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is we don't have the port groups associated with the VLAN 12
or VLAN 13 yet.
So let's go ahead and create those.
So we'll right click on the distributed switch
and we'll simply click on distributed port group
and then we'll click on new distributed port group.
And this first of all, create one for VLAN 12.
So I'm going to call this VDS one
so that when we see it, we'll know exactly where it is
as part of that parent switch.
And for this, we'll just go ahead and call it VLAN 12
and I'll call it front end as well
because we're going to be using it for the front end
as part of our Kubernetes cluster
with the NSX application platform. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with the NSX application platform.
So I'll move this to topology up to the top
so I can go ahead and click on next.
And then for the details of this new port group,
I want it to be supporting VLAN number 12.
So we'll go ahead and put that in as 12
and then I'll scroll down.
I want to go ahead and look at all the other properties
as well.
And then I'm going to go ahead and allow MAC address changes
and force transmits and also enable MAC learning
and click on next.
Then I'm going to leave the traffic shaping alone.
And then currently I have four uplinks
associated with that distributed switch.
And just for the lab, I'm going to say,
let's just use VMNIC zero. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
let's just use VMNIC zero.
So I'm going to take all the rest
and put them in the unused category.
So the port group for VLAN 12 is the fact
that we're just going to use that one uplink,
which is going to be fine and we'll click on next.
Then we'll click on next and next and finish.
Boom, we now have our port group right here
to support the front end.
So let's go ahead and create one more port group
for VLAN 13.
So we'll go back to the virtual distributed switch,
right click on distributed port group from the menu,
click on new distributed port group.
And we'll call this one VDS-1, VLAN 13. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we'll call this one VDS-1, VLAN 13.
And I'm also going to put the word workload in there as well.
That way when we see it, it'll remind us
of what it's being used for, what it will be used for,
and we'll click on next.
And then this is going to be supporting VLAN 13.
So we'll put that in.
And then we'll click on the check box
for customized default policy config next.
And I'm going to say accept to the port's transmits
and Mac address changes, enable Mac learning, click on next,
leave traffic shaping up this default, click on next.
And then for the uplink, so I'm going to use a single uplink.
So I'll take the others as part of the distributed switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'll take the others as part of the distributed switch
and put them out of the picture,
click on next and next and next and finish.
Now in a production environment,
you may want to have like a primary uplink
then a backup and so forth.
However, in a lab environment,
I would recommend just using one to make it nice and clean
so you know exactly where your traffic is flowing.
So now we have our port groups for VLAN 11,
a port group for VLAN 12, and a port group for VLAN 13.
Now in this vSphere environment,
if we were to also deploy the DNS server upon VLAN 10,
we'd also want to make sure we have a port group for VLAN 10. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we'd also want to make sure we have a port group for VLAN 10.
However, in my topology, I've got that Windows server
at dot 100 on the 10, 10, 10 network hosted on a different server.
So before we're all done, we'll verify that DNS
and NTP services are working in conjunction
with that server up on the Blue network on VLAN 10.
So let's check our work.
So we have these three hosts,
Blue four, five and six that we can use as compute resources.
We have port groups associated with the management network,
VLAN 11, the front end network, VLAN 12,
and the workload network, which is VLAN 13. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and the workload network, which is VLAN 13.
So now that VMWare and vSphere are aware of those VLANs,
we need to make sure in the physical topology
that those VLANs actually exist,
including the default gateway on the top of Rec Switch
that we want to use.
So we're going to shift over to the physical side of the house
in the very next video and verify those components.
So we'll see you there in just a moment.