All right, it's time to get physical.
We're gonna take a look at the physical infrastructure here
to make sure that these VLANs exist,
specifically VLAN 11 and 12 and 13,
and also that we have a default gateway IP address
associated with our top of rack switch here,
connected in association with those VLANs.
And we also wanna make sure that we have NAT support
out to the internet, either here at this top of rack switch,
if it supports it or here at this router,
as that traffic is going out to the internet.
So with this topology in mind, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So with this topology in mind,
let's verify VLAN 11, 12 and 13.
So here we are at the CLI for my top of rack switch.
As I mentioned, I'm using a Cisco catalyst
multiplayer switch.
So whatever you wanna use for the functionality here
for the default gateway,
and also for connectivity to these VLANs,
is perfectly fine.
Whether it's Cisco products or products from HP,
or products from some else like Fortinet,
once again, it really doesn't matter which vendor you're using,
as long as you can provide the services that you need.
So let's start off by verifying that we have these VLANs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's start off by verifying that we have these VLANs
that they exist here on my top of rack switch.
So on this Cisco multiplayer switch,
I'm gonna do a show VLAN brief, just like that,
just to verify that the VLANs exist.
So here I've got VLANs 11, 12 and 13,
and while I'm here, I'm gonna go ahead
and just rename those so that when I see them,
I won't just be a number,
but I can also remember what they're for.
So I'm gonna go into configuration mode
on this multiplayer switch,
and then from here, type in VLAN 11,
and say name is gonna be management,
and then for VLAN 12, the name is gonna be front end, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and then for VLAN 12, the name is gonna be front end,
and then for VLAN 13, the name is gonna be workload.
Not workload, whatever that is, but workload,
and let's do a do show VLAN brief,
just to verify this took,
and check this out, there's VLAN 11's name,
and VLAN 12's name,
and they need to exit out here before that third rule takes.
So now if we do a show VLAN brief, press enter,
then I've got the appropriate names here
on those three VLANs.
So the actual names aren't too important,
what's really important is the actual VLAN numbers WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
what's really important is the actual VLAN numbers
that they exist.
Next, let's take a look at this multiplayer switch,
just to verify that I had the IP address of .1
on each of those respective subnets associated
with these three VLANs.
So on this multiplayer switch,
we're gonna do a show IP interface for VLAN 11,
and so for the output,
let me go ahead and actually only include output
that has the text address in it, a press enter,
just to confirm.
So this is the IP address for the logical layer three interface
that's part of our associate with VLAN 11
on this multiplayer switch,
but we'll specify VLAN 12 right there, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
but we'll specify VLAN 12 right there,
and that's 10, 12, 12, 1, that looks good as well.
And then a similar treatment for VLAN 13,
and that looks good as well.
So the next thing I wanna verify
is that I have a network address translation set up.
So also from the top of rack switch,
from a routing perspective,
let's verify we can get to the internet
that's through a ping out to 8.8.8.8,
and that works.
We could also a trace out to 8.8.8.8.
And let me go ahead and do a break there.
I just wanna verify WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I just wanna verify
we're actually getting out to the internet.
So this top of rack switch can get out to the internet,
which also implies that this router right here
is providing network address translation services.
So I also wanna verify that this router here
is not only doing address translation
for clients that are on this common network,
but also for clients that are going to the internet
sourcing it from the 10 address space as well.
So let me take you over to this router here,
which in my topology happens to be a little
4 to 8 firewall.
So here on this router,
this is the 4 to 8 device providing these routing services.
Here it shows us that it's configured to do NAT WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Here it shows us that it's configured to do NAT
for traffic source from 10 anything.
So not only can the top of rack switch
get out to the internet,
but if traffic is sourced from any of these clients here
going out to the internet,
it's gonna be able to provide address translation services
as well.
I also wanna verify that this router
knows how to forward back to the 10 network address space.
And to do that, let me verify its static routes.
So if we go to network on the left here
and we go to static routes.
So what I'm doing here on this router
is I've got a static route that says to get to 10 anything,
hand it back to the top of rack switch, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
hand it back to the top of rack switch,
who can then forward it to the intended party.
Now we also could have used dynamic routing protocols
like OSPF or BGP, et cetera.
However, for the lab environment,
I thought a simple static route with no games involved
would be more than enough, which it is.
Also, one of my intentions in this set of videos
is to make sure you see every single part that's involved.
So we've taken a look now at the top of rack switch.
It has the appropriate logical IP addresses
for these three networks here.
And also our routing device here
is employing address translation WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is employing address translation
and also has a route back to the 10 address space.
Now, another thing I'd love to do is set up DHGP services
for these three networks, the management, front end
and workload.
Now, even though it's not required,
we don't have to use DHGP for Kubernetes services.
However, if we have DHGP,
it'll make it very easy to drop in a VM
on any of these networks.
And verify from that perspective of that VM connectivity,
including DNS name resolution and connectivity
out to the internet.
So in the next video, let's work with our top of rack switch WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in the next video, let's work with our top of rack switch
once again and set up the DHGP services
for the management, front end and workload networks.