All right, this time to jump in the lab and do some configuration and our focus
isn't
really on making sure we know how to get onto a VLAN interface and configure an
IP address
because that's more CCNA level knowledge.
What our focus should be on here is as we are configuring our SVI's and our IP
addresses
and such that we're thinking about the topology.
Again, we want to become one with layer two and layer three and one way as we
can do that
is really by making sure we're grasping the traffic flow that's going to occur
among these
different SVI's. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
different SVI's.
So let's just go ahead and go through these lab steps.
First of all, we're to configure an SVI for VLAN 10.
So I'm going to again switch one first here, do an interface VLAN 10 and we're
told to
give it an IP address of 10.0.10 and switch one gets .1 and this is a /24 and
then VLAN
interfaces on most Cisco platforms default to being in a shutdown state.
So I'm going to do a no shut.
The other big requirement for VLAN interfaces is that the layer two VLAN must WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The other big requirement for VLAN interfaces is that the layer two VLAN must
exist and it
must be enabled on an interface whether that's an access port or enabled on a
trunk but either
way we need a port in the forwarding state for that VLAN from a spanning tree
perspective
for the SVI to be online.
It has to have traffic that it can, it has to be able to go somewhere basically
.
And so with VLAN 10, if I do a show VLAN here, we'll see that VLAN 10 has
already been configured
for us in this lab environment.
So everything is good there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So everything is good there.
If I do a show interface VLAN 10, we should see that it's up and up and we do
see indeed
that it's online and operational.
Now if I go back to my topology here, let's see here if I can do this, very
good.
So what I've done now is I've configured an SVI for VLAN 10.
But because the switch knows that hey this SVI belongs to VLAN 10, it has
mapped it already
to the layer two VLAN.
But in our topology here we see we don't actually have anywhere to go. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But in our topology here we see we don't actually have anywhere to go.
I don't have an SVI down on switch three or over on switch two.
And so I can't actually ping anything other than potentially routing among
other layer
three interfaces.
If I had an SVI over here for a different VLAN, then we can switch traffic via
layer
three among any of these layer three interfaces.
That's the nature of a multi layer switch.
But this dot is the only one in our topology so far.
And so we are clearly going to need to keep configuring. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so we are clearly going to need to keep configuring.
So back to the lab we go, we're going to go over to switch two now and finish
this out
by configuring another VLAN 10 interface.
This time with an IP address of 10.0.10.2, still a slash 24.
And don't forget to no shut it.
So while that's coming online, we go back to our topology here.
And now we've configured a VLAN 10 interface here, switch two nodes to attach
that to VLAN
10. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
10.
And based on this topology, we should see that we have communication among
these different
switches.
Now, for the sake of this lab, the physical topology and the layer two
configurations
already in place.
So we can trust that everything down here is where it needs to be.
But now let's go and see if our layer three is indeed working.
And one of the best ways to do that is to simply do a ping.
So I should be able to ping 10.0.10.1 would be switch one.
I'm on switch two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm on switch two.
And once our port goes through, we have to find the MAC address of the remote
IP.
And we do indeed see that we can ping it.
So our topology, our logical topology is coming together appropriately.
But now we're told to add a secondary subnet.
And we're to add two secondary subnets actually to switch one and switch two.
So we'll do this quickly.
But as we recall in our conversation earlier, all I need to do is get on to V
LAN 10.
And now I can configure multiple subnets within this broadcast domain that we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And now I can configure multiple subnets within this broadcast domain that we
're calling
VLAN 10.
So this command is very similar.
This time it's going to be an IP address of 10.0.11 for the subnet still slash
24.
But now I add this secondary term to the end.
And I can do the same thing with the dot 12.
And so we just want to make sure that we can indeed assign many different
secondary IP
addresses. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
addresses.
So if I do a show run on this interface now, I should see that not only do I
have the primary
IP address, but I also have the secondary IP addresses.
One thing to note is that anytime we do pings, anytime we're doing an operation
where I need
to source traffic, unless we force it to do so, a switch will never source the
ping
or source, maybe an SSH session from a secondary IP address.
I would need to specify a source IP in that case.
But generally speaking, secondary IP addresses are just there to serve as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But generally speaking, secondary IP addresses are just there to serve as
default gateways
or whatever the situation is, but we're really not intended to be using them
for our primary
traffic flows.
So now I'm just going to go over to switch to and do the same configuration in
VLAN 10
and then 10 dot 0 dot 11 dot 2 this time for switch to.
And then same thing here for the dot 12 subnet.
And if I confirm my configuration, everything looks good now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if I confirm my configuration, everything looks good now.
So that is the configuration of our secondary subnets.
Now we go back to the topology, we're told that we are maybe not quite where we
need
to be because switch three is down here and we have no way to manage it.
So how can we manage it in this case?
Well, all we need to do is configure a layer three interface.
But yeah, we could potentially find the physical interface and convert that to
layer three. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
layer three.
But probably what we really want to do is take advantage of VLAN 10, configure
an SVI
and VLAN 10.
And this SVI will use the dot three IP address.
So let's go ahead and go over to switch three now.
Get on to VLAN 10 IP address.
Now we got to go back to the 10 dot 0 dot 10 subnet dot three for switch three
and then
do a no shut.
And if everything comes together here, VLAN 10 will come online and I should be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if everything comes together here, VLAN 10 will come online and I should be
able to
ping dot one and dot two because we're all on the same layer two domain at this
point.
So there we go.
That is the end of this lab challenge.
Again, it really was just creating VLAN interfaces and IP addresses.
And the secondaries was kind of a cool thing.
But for the most part, it really is all about maintaining in our minds as we
progress through
physical and logical topologies that we know how these logical topologies are
coming together.
And when we even look at the logical topology here, we can see directly how WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And when we even look at the logical topology here, we can see directly how
these SVI's are
able to communicate with one another because of the way that we express it by
sort of blending
the physical and logical together.
I hope this has been informative for you and I'd like to thank you for viewing.