All right, now it's time for our last discussion of the day and that is on
inter-VLAN routing. Okay, so inter-VLAN routing is about what? Inter-VLAN routing
is about us routing in and out of our VLANs. That's what it's about, right? Many
people just think, oh, inter-VLAN routing, routing from one VLAN to another VLAN.
Okay, wait, what is a VLAN? A VLAN is what? A VLAN is a subnet. A VLAN is a
broadcast domain. If you want to route from a VLAN to anywhere else, you have to
or if you want to go from your VLAN to anywhere else, you need a route. So it's
not just between VLANs, it's to everything in this entire world. If
you're in VLAN 10 and you want to go to the internet, you need inter-VLAN
routing. If you're in VLAN 10 and you want to talk to somebody in VLAN 30, you need
inter-VLAN routing. So we're going to look at two different options today. We're
going to look at inter-VLAN routing from an actual router standpoint and then
we're going to look at it from the perspective of using our multi-layer
switches. So let's go to our branch office right now. This diagram we looked
at earlier today. And when it comes to setting up inter-VLAN routing in this
type of scenario, what are we dealing with? Well, we're dealing with a router
interface. That is a layer 3 interface. That's what that is, a layer 3 router
interface that can support what? IP addresses. And down here we're dealing
with a layer 2 interface that supports what? That supports VLANs. That's kind of
a discrepancy, don't we, right? And by default this works because if this is
VLAN 1 and even though this is layer 3, right, there's no tagging, there's no
nothing, it works because VLAN 1 doesn't tag by default, doesn't do any of that. So
that's why this just works right out of the box for us if you only have what? One
subnet. One subnet and it's VLAN 1. Everything would work just fine. But when
all of a sudden we have multiple subnets, multiple VLANs, multiple broadcast
domains with one interface here going down to a switch, this is where things
have to get creative for us. And so now we're going to set up what is called
router on a stick or router on a trunk. So what do we need to do? Well let's
pretend we have VLAN 255 down here. Let's pretend we have VLAN 254 down here. So
we're gonna have to create a trunk link here for that. But then how in the world
do we configure that interface? Let's come back to that after we configure ASW2
rapidly here. So why rapidly? Because we've already seen all of this so far
today. So I'm with the magic, oh look at that, okay, so ASW2 now folks is over in
branch. I'm just reusing the same switch, magic of virtualization. Alright so
pretend this is the switch over here ASW2 just to give you an idea what's
going on. So what's happening is that we'd go to configure terminal, we'd have
to create our VLAN, so VLAN 254 and VLAN 255. And then what else might we want to
do? We'd have to go to interface, gigabit ethernet, 1 slash 0 slash 31 and we
would have to type in switchport mode trunk switchport no negotiate. Why?
Because these routers here do not support DTP. So switchport mode trunk
switchport no negotiate. What else might we type in? Oh switchport trunk allowed
VLAN 254 and 255 right? What about switchport trunk native VLAN? Let's say
we're using native VLAN 99 right? All of that stuff. So just like we did back in
our VLAN and trunking discussion, same thing here on our switchport. So nothing
new there, not a big deal. And whatever access ports here you want to configure,
like maybe for example interface gigabit 1 slash 0 slash 35, we'll say switchport
mode access switchport access VLAN let's say 254. Alright so again we have
interface 35 here and there's a PC connected to it as an example. That's
what we've done. Alright so no surprise there. So if this comes up
in the exam you already know how to do that. You've seen it in our trunk and
VLAN configuration plus here as well. But now the branch configuration is going to
be slightly different for you. What did I just do? Alright branch configuration is
gonna be slightly different for you now. So the port is fastethernet 0 slash 0
slash 0 on branch. Notice that this port is up up right now. Why? Because we're
connected to our ASW2 switch in our branch office on gigabit ethernet 1
slash 0 slash 31 and it's already configured as it needs to be configured.
But now what we're going to do is we're going to show you how to configure
fastethernet 0 slash 0 slash 0 to support these two different VLANs. So
first of all what we need is we need to come over their IP addressing space. So
our IP addressing space for VLAN 255 is going to be 10.0.255.0 slash 24. And
then our IP addressing space for VLAN 254 let's say we do 10.0.254.0 slash 24.
Alright so notice there's two different IP addressing spaces there. So I need two
default gateways therefore I need two interfaces. How many interfaces do I have
on my router right now? Just one. That's all I have. So what I need to do now is I
need to create virtual interfaces. I need a virtual interface for this and I need
a virtual interface for this. So how do we do that on our physical routers?
We create what are called sub interfaces. And we're going to create one sub
interface for each of these. So I'll create let's say fastethernet 0 slash 0
slash 0.24 for this one. And we'll go with fastethernet 0 slash 0 slash 0.25
for this one. That's what we're going to do. So type in configure terminal
interface fastethernet 0 slash 0 slash 0. Notice that I can put a period. So
let's put a period question mark. And now it's asking for the sub interface. So
we said we're going to use sub interface 24. Now I'm in sub interface configuration
mode. Let's do interface fastethernet 0 slash 0 slash 0.25 as well. And then
let's type in do show IP interface brief. And you'll see we have two sub
interfaces created now. So anytime you see a period that is a sub interface for
that physical interface. Now you might be asking hey why are these ones deleted?
These ones are deleted because they were created and they have been removed. But
the router hasn't been rebooted yet. So if you ever delete a sub interface it'll
say delete it in the output. But it won't be removed until you reboot the device.
That's not exam relevant. But I get that question asked a lot. Why delete? What
does that mean? All right so .24 .25 there they are. So we got to configure them
now. So let's go back into the interface configuration mode for those. Let's go
24 first. And what are we going to type in here? Well if I type in the IP address
you're going to see it won't let me do that. So let's type in 10.0.254.1
255.255.255.0. Some bad typing on my part right there. Right and we
got a perfect preface that with IP address. Right and you'll see I can't do
it. Why can't I do that? Because I haven't specified the VLAN. You got to specify
the VLAN first. So it's encapsulation. Exactly Jeffrey. Thank you. So
encapsulation. And on this device we support only .1Q for this. So .1Q
and then what is the VLAN? We said it's going to be VLAN 254. All right so let's
do now the IP address and you'll see it takes it. So do show run interface fast
Ethernet 0.0.0.0.24
Right so there you go. There's the configuration to create the sub
interface. We'll do the same thing for .25. So .25 but instead we'll do
encapsulation 255 and then the IP address is going to be what? We said the
IP address is going to be 255.1.
All right so there we go. All right and then also if you want to do the native
VLAN. I wanted to show you here do show VLANs is a command that will show me
the VLANs that are now on the router. So branch a router and you'll see that
VLAN 1 is automatically there. It's for the physical interface and you'll see
that it's automatically the native VLAN. So VLAN 1 is automatically the native
VLAN on the Cisco devices. So if you ever want to change that and remember we set
the native VLAN here to 99 right? What you would have to do is you'd have to
create another sub interface for that particular VLAN. So I'm just going to
create a sub interface of 99. You could do whatever you want but I'm going to do
99 in this case. And now we're going to say encapsulation.1q and we'll type in
99 and we'll type in native. That makes it the native VLAN. Now I'm not going to
put an IP address within it because I don't want to route for the native VLAN
in this scenario. If you had a need to go ahead if not then don't worry about it.
But I'm not going to put an IP address for safety and security reasons because
we're not going to have traffic in that VLAN. But again we're dealing with a
chunk link right? VLAN 99 here's the native VLAN therefore VLAN 99 that
should be there as a native VLAN. So do show VLANs you'll now see that the VLAN
1 is no longer the native VLAN. If we go to VLAN 99 you'll see it's now the
native VLAN. If we scroll down a little bit more you'll see VLAN 254 is
associated with this sub interface and has this IP address. VLAN 255 using 802.1q
encapsulation associated with this sub interface with this IP address.
Now if we look at do show IP interface brief you'll see that we have an IP
address on an interface and the interface is up up. What does that mean?
That would mean folks that we should have an entry in our routing table for
these networks. Network 10.0.254.0.24 and 10.0.255.0.24.
Let's type in do show IP route and you're going to see that that is true.
Why does this happen? Because when you have an IP address on an
interface and the interface is up up that means the network ID of that
interface gets installed in the routing table. You would have learned that in
your CCNA days. So as a result of that we now have those in a routing
table. So let's just give you a little example of what would happen in regards
to router decision-making process and traffic flow in this particular case. So
for example let's say we have traffic coming to let's say there's a device
here 10.0.255.25. So you have a packet with a destination IP of 10.0.255.25.
Arrives at the router branch. Branch A now does a routing table lookup and when
it does a routing table lookup it realizes that the best entry is this one.
Directly connected network out fast Ethernet 0.0.0.25. So what does it
need to do now? It needs to create an ART message to get the MAC address of this
PC. So how does it do that? Well it's going to have to encapsulate the
ART message in what? An 802.1Q tag. So it's going to have to do. Because what it
needs to do is it needs to send an ART message out asking hey if you're 10.0.255
10.0.255.25 give me your MAC address but it has to stay in what VLAN? It has to
stay in VLAN 255. How does it know that? With the output of show VLANs. Show VLAN
says what? Anything out this interface has to be tagged with 255 using 802.1Q.
So now it tags it the ART message with 802.1Q therefore it only ends up
going to those devices in VLAN 255 and no one else and therefore this PC gets
it responds back with the ART reply and the switch would tag it as it needs to
right and eventually comes back. And now what can I do? I can write the packet now
so I can go ahead and build the the new frame so source MAC the source MAC would
be what? The MAC address of fastethernet 0 0 0 dot 25 and in the destination MAC
is the one we just got back in the ART message which is the MAC address of that
device and now we can send the frame out on the network oh after we tag it 802.1Q
tagging right and then we tag it with 255 so this switch knows it stays in 255
and then we can forward it out and so the same thing would happen in reverse
traffic arrives inbound on this interface it's part of VLAN 255 it gets
forwarded up to our default gateway default gateway gets it it looks at the
tag the tag says VLAN 255 since the tag is VLAN 255 the router knows it belongs
to this sub interface and therefore I can check the destination MAC address of
the frame compared to the destination MAC address of the sub interface and
therefore in the end it has everybody's abiding by our what our switch rules
when it's all said and done. All right so that is a configuration example of
interview and routing with router on a trunk. You know more than you need to
know to pass anything on the certification exam about that. Right now
let's talk about interview and routing in regards to our multi-layer switches
because things are significantly different here compared to what we just
discovered and we just discussed. We're going to be using things called SVIs
instead and routed ports. SVIs and routed ports two different things for two
different purposes but we need them both. So when we're dealing with interview and
routing on a multi-layer switch what are we doing we are creating these virtual
interfaces that are going to ultimately in the end give us the opportunity to
route traffic. So SVIs routed ports pay very close attention to how I have
labeled these. Notice how I'm pointing right to the middle of the switches for
SVIs but the routed ports I'm actually pointing to the physical ports. Big
significant difference there. Routed ports are really important because if we
go back to our architecture or diagram that we have here what I want you to
realize is that in our modern-day networks where we have layer 2 layer 3
as such this is all layer 2 and the rest is all layer 3. Where do the SVIs go? The
SVIs are going to go here. The SVIs are going to go here. The SVIs are going to
go here. The SVIs are going to go here. But then every other port in that layer 3
environment has to be a routed port. That's right. Meaning this is a routed
port. This is this is this is this is this is this is this is this is this is
this is this is this. All of these are routed ports. Why? Because I want to route.
We can run OSPF on a routed port. We can run EIGRP on a routed port. We can run
BGP on a routed port. We can run ISIS on a routed port. So routing. Routed
ports. So we would create for example like your slash 30 networks. Slash 30
networks can go on routed ports between those two devices. I can run OSPF and
EIGRP on them as an example. So no trunks, no VLANs there. Trunks and VLANs
are only here. Trunks and VLANs are only here. Everywhere in here is what? Routed
ports and dynamic routing protocols. So that's why over here right I'm showing
you your routed ports as they are. So how do we do that? Well first of all we have
to realize that on a multi-layer switch typically what we're gonna have is we
are gonna have if I type in stew show interface gigabit ethernet 1 size 0
size 13 switch port you're gonna see that I am a layer 2 switch port. When you
see this output folks this means layer 2. This means we do not support IP
addressing. We do not support dynamic routing protocols. So if I type in
interface gigabit 1 size 0 size 13 and I'm like hey I want to put a slash 30
network here like we have in our diagram. So 10.40.23.2. 255.255.255.252.
Why do I keep forgetting IP address today?
You're gonna see it's not even a valid command. Why is it not a valid command?
Because I am a layer 2 switch port. I support VLANs. I support trunks. I support
spanning tree protocol. How do I convert a layer 2 switch port on my devices my
multi-layer switches to layer 3? Another one I want to show you is do show
interface status. When look at the output of show interface status for this port
you're gonna see right now it says I am connected but I'm in VLAN 1. I'm in
VLAN 1 okay. Then you might be saying why not make it a trunk port because I
don't want VLANs up there. I don't want trunks up there. Right this is our
distribution to core area. Fast fast fast fast. That spanning tree protocol is slow.
Spanning tree protocol blocks more than 50% of our links. Dynamic routing
protocols don't do that. So I don't want trunks and VLANs up in my distribution
and core nowadays. Yeah Jeffrey says you know what we got to type no switch port
to make this happen. All right so no switch port. So don't confuse this on the
exam if you've never seen this before. No switch port means layer 3 port. That's
what it means. So I'm gonna now type in do show interface gig 1 size 0 size 13
switch port. Look at this. Disable. Now again on the exam don't let that trick
you. If it says switch port disabled that doesn't mean it's not on. It means
layer 3. Layer 3. That's what it means. So let's look at the output of show
interface status now and you'll see it no longer shows that I'm in VLAN 1. It
shows I'm a routed port. Routed port. Now that means I can support IP addressing.
Boom. Now that means I can support a dynamic
routing protocol like OSPF which I think is already running on this device. So I
might be able to form an OSPF neighborship really really soon. All
right maybe not. Let's type in IP OSPF 1 area 0. Let's see if that helps me out.
Maybe the other devices aren't configured yet properly. That's why.
Because I haven't configured the whole environment. All right I'm just gonna
leave that alone. 10.40.23.2.
2.5. 2.5. 2.5. .
That looks right. I do have my previous commands typed here. Let me just double
check that. 10.40.23.2 there you go. So yeah there you go. I'm running OSPF it
just took a while. I'm impatient. And there you go. Right so I want a routed
port here on gigabit 1 0 14 as well. So I'm just going to copy
and paste it out of my notepad file. I'm going to paste it in just to make it a
little quicker. Alright so there you go. Another routed port. IP OSPF 1 area 0 as
well. And now we can participate in OSPF and all that fun stuff. So we need to do
the same thing on DSW 2 as well. So I've got my everything previously typed in
here. So interface gig 1 size 0 size 13. No switch port but the IP address. 14 no
switch port but the IP address. So let's go and do that on DSW 2 now. And I'll
have my environment the way I want it. So for the exam think about it anytime you
are beyond the distribution layer. If this is our demarcation point. If they're
telling you on the exam or even in the real world that this is layer 3 up here
and this is layer 2 down here. Right typically these are all going to be
routed ports then for you. And on the certification exam because that's
configuration best practices. And in here these are all going to be what VLANs
trunks. So what do you need now over here? We need SVIs. Now folks if you're
looking at the time we are almost out of time but I'm going to finish this
discussion because we need to get through it. And there's not much left to
cover here. So SVIs. This is a confusing point for a lot of people in the
industry. SVIs. I find there's a lot of people who are a little foggy on SVIs
and they don't understand the full purpose of what an SVI is. So I'm going
to clarify that for everybody here who has any at all fogginess about SVI. So
what is an SVI? It is a virtual layer 3 interface that has the ability to route
traffic in and out of the VLANs they're configured for. For any link that is a
member of that VLAN. So what I want you to realize right now is that this is a
trunk. This is a trunk. This is a trunk. This is a trunk. This is a trunk. This is a
trunk. This is a trunk. This is a trunk. All of these trunk ports are supporting
which VLANs? 10, 20, 50, 200 in my environment. Therefore I need an SVI for
10. That's 50. This one is 20 and this one is 200. What this means now is that
this SVI, think of it as a virtual layer 3 router interface, that is now going to
be able to route traffic in and out of that VLAN on any one. Any one of those
trunk links. It is your default gateway and every access port or trunk port that
can pass traffic for that VLAN is allowed to use it. There are way too many
interfaces here to do routed ports. You can't do sub interfaces on multi-layer
switches. So what do you use? SVIs. So if I had a hundred trunk links for VLAN and
they all supported VLAN 10, then that one SVI for VLAN 10 can take traffic on and
off all 100 of those trunk links. Every single one of them and route for them. That's what
an SVI does for us. It's that simple. That's all it does. So it's gonna have an
IP address. It's gonna have a subnet mask. It's gonna have a MAC address. Why?
Because it is going to be the default gateway. The default gateway. Conrad says,
are they quicker? Quicker than what? Quicker than what? There is no alternative.
That's the thing, right? There is no alternative. I can't do routed ports
because a routed port is for one interface, which means that only one
interface could be used then for that subnet, for that VLAN, for that broadcast
So I can't use routed ports. Some interfaces are not even allowed. So can't even do those.
SVI is the only option. So they're not quicker because there's no other way.
There's no other option. This is what you have to do.
You could, Jeffrey, but not designed for that purpose. And as a result,
you're not going to get the benefits you necessarily need. All right? They weren't
designed for that. Weren't designed for that. Always keep that in mind, right?
The SVI is designed specifically to be your default gateway for your VLANs.
Not a routed port as an Ether channel bundle. Okay?
Because, Jeffrey, I would not technically be allowed to what? Bundle all of these together.
Unless I was doing VSS and stacking. Unless I was doing VSS and stacking,
I would not be allowed to do that. Anyways, so that would only allow me to do these two
ports together in that particular case, which would not have the same benefit as using the SVI.
Right? But also, you're saying routed Ether channel. The problem is,
if we're doing routed Ether channel down to here, that now messes with Spanachy protocol,
messes with a lot of different things. So it really changes what's going on,
and can create a lot of issues that have to be solved after the fact.
So we're not going to go down that path. But SVIs, exam, this is what you're doing.
Real world, this is what you're supposed to do. So let me show you how easy it is to do this now.
DSW1. Let's create an SVI. Interface, VLAN, 10. Done. There you go. I'm done. I just created it.
And on this platform, they automatically go up. Right? As long as conditions are met,
and that is what? They're not shut down. So they're not shut down by default on this device.
They're automatically enabled. Okay? So number two, the VLAN exists. Does VLAN 10 exist on this device?
Oh, my gosh. All right. Yes, it does. VLAN 10 does exist on this device. Okay. What else?
Do show interface trunk. Do you have at least one interface that is in the spanning tree
forwarding state? In the spanning tree forwarding state for VLAN 10? Yes, I do. Yes, absolutely.
Hunter, yes. I have at least one. So if those three conditions are met, then my SVI is up.
Now I got to put an IP address on that. So what is the IP address of this particular subnet going
to be? Or the IP address of this interface in our subnet? Well, we said this is going to be
10.0.0.0 size 24. So let's put an IP address 10.0.0.1, 255, 255, 255, 0. You can do anything
you want as long as it's in the right subnet as the users. So what is the IP addressing space
you created for VLAN 10? You're going to want an IP address for that on your SVI.
Now what can I do? I can route traffic in and out of this particular SVI.
We've done a lot today, but I have a device here with the IP address 10.0.0.10.
It's in the same subnet as that interface. We've done a lot.
Okay, I've messed around a lot. I've made some changes. Here's hoping the ping works.
Okay, so what does that mean? It successfully means this is configured right, this is right,
this is right, this is right, this is okay. Uh-oh, we got a bunch of stuff right, and that SVI
is taking whatever interface that frame came in on and has processed it successfully for me.
And there you go. It could be my default gateway for my subnet.
It could be my default gateway for my subnet. So if we look at the open to do show
IP interface brief, you're going to see that it shows up now as an interface with its IP address,
and it's up up. Why? Because the VLAN exists, it's not shut down, and there's at least one
interface in the spanning tree forwarding state for that VLAN, so we're perfect there.
This is beautiful. I love it. Looking good. Let's type in show IP interface VLAN 10.
All right, so there's our IP address, our subnet mask, any multi-cast groups we join, that's for
OSPF because I have OSPF to automatically get enabled on my interfaces on my device,
right, MTU. So even though it's a virtual interface, it still has to abide by MTU.
If I want to set up access control lists on an SVI, why? It's the default gateway.
It's no different than a physical router interface that's being used as a default gateway,
except it's virtual in this case. That's it. So I can still set up ACLs on it to control
traffic coming in and out of the subnet. What else do we want to do? Take a look at show
interface VLAN 10, and we're going to see that it even gets its own MAC address. That was
dynamically assigned from a pool MAC addresses that are available on this platform. So that way,
anytime it wants to build a frame and send it to somebody in the subnet VLAN or broadcast domain,
it can use it as its source MAC address. Anytime somebody wants to talk to this device
at 10.0.0, it's going to have to learn the MAC address. So that way, they can talk to it. So
we should be able to see our minus A. There it is. There's that MAC address. That is on the SVI,
9647, 9647. Yep, there it is, 9647. So again, right, we're going to be able to see our MAC
address. So again, right, sending out our ARP message from PC, getting the MAC address of that
device's IP address, return to us. Now we can talk to that device in our own subnet. So yeah,
it's great. Right now, it's not set up as the default gateway on my client, as you can see.
My client is using a different address as its default gateway. It's configured with 10.0.0.254.
Why? Because that'll be something we talk about tomorrow, not today. But we'll get back to that
later on. MTU for the physical interface, bandwidth of the interface that we have. It's
a gigabit Ethernet interface, the SVIs, because this is a gigabit platform device.
It even keeps track of the packets that are coming in and out of the interface,
just like a physical interface would. Right, so this is great. This is our SVI. This is our
default gateway for the subnet to VLAN broadcast domain. Traffic comes in and out of that subnet
VLAN broadcast domain through here. So if we look at do show IP route now, you'll see that there's
an entry in our routing table for it as well. 10.0.0.0.24 directly connected to VLAN 10. So
anybody in 10.0.0.0.24 can be reached through SVI, interface VLAN 10, not VLAN 10. I don't like the
way that is worded. It should say interface VLAN 10, but it doesn't. Okay, it's interface VLAN 10,
not VLAN 10, interface VLAN 10. There's a difference, right? Because VLAN 10 is a layer
two thing. Interface VLAN 10 is a layer three thing. Interface VLAN 10 routes traffic in and
out of VLAN 10. Good stuff. All right, so let's create the rest of them. So that way,
there we can wrap up today's class. So we've got interface VLAN 20. And that's going to be
IP address 10.0.2, according to my diagram up there, 10.0.2.1, 255.255.255.0. What did I do wrong?
I need one more D. Yep. Okay, now let's go interface VLAN 50. And that's going to be 1.1.
And now let's do interface VLAN 200. And according to my, it's going to be 3.1.
All right, so now we've got all the SVIs configured here. But look, we've got another router,
another router that could also be an entry exit point in our environment, right? We want redundancy,
we want high availability. So does that mean over on DSW2, we want to create SVIs as well?
Absolutely. One for each and every single one of our subnets, VLAN broadcast domains.
So interface VLAN 10. Now, we want to, we're going to put in the exact same subnet. So 10.0,
10.0.0.1. Can't use that, right? Why? Because who else is using that? DSW1. So I got to
use an address that's not being used in the same subnet. Now I'm going to ping
10.0.0.1. Successful. Okay, the question is, did we go through the layer two environment or the
layer three environment? Okay, I'm pretty confident we went through the layer two environment, not the
layer three environment, meaning I was able to test connectivity through here. That's what I've
done. But to be sure, let's do a trace instead to 10.0.0.1. And if the trace route only shows
one hop, it means we went through the layer two environment and that's it.
One hop, we went through from here, stayed in the layer two environment, hit the next router,
the next router was 10.0.0.1. We're good. So we know we have basic connectivity between our
default gateways now. One's 10.0.0.2, the other one's 10.0.0.1. So let's go ahead and create,
for example, interface VLAN 20. Over here, we'll do the same thing, but in this case,
it's going to be 2.1 or 2.2, pardon me, not 2.1, 2.2. We'll do the same thing for 50. And so we
said this was going to be 1.2 now on this side. And then we're going to do the same thing for
VLAN 200, and it's going to be 3.2, right? So now we have our SVI set up on both sides,
interface VLAN 10, 20, 50, 200, 10, 20, 50, 200, 10.0.0.1, 10.0.0.1.2, 10.0.0.2, right?
And so on and so forth for our addressing that we need. So those addresses are now reserved for
our default gateway. We would not hand them out to any clients in those particular subnets,
but we have ourselves in a really good spot now, in a really, really, really good spot.
Jeffrey says, do a source ping, Raymond, if you can. Sure, absolutely. We can do that.
So if we did, for example, ping, where was that ping we did? Do ping 10.0.0.1 from source,
10.0.0.2. There you go. And we trace.
It won't let me do that. What command do I got to do here for traceroute?
That's all you're going to let me do?
Yep. There you go. Okay. So we're pinging through the layer two environment, which is beautiful.
It's exactly what we want. So folks, what I want you to realize is today we've successfully set
up our VLANs on all of our four switches. We set up all of our trunks. We played around with VTP,
and we've set up, what, our default gateways for each of those VLANs we created,
and we set up our routed ports as well to connect us up to the core of our environment.
So all of these configs, all of these core elements of your network are extremely important
for your certification exam success. So if there's anything we covered today where you're a
little bit foggy on, make sure you go back and review what we've covered at some point in time.
And if you have any questions, comments, or concerns, make sure you reach out using the
request mentoring option anytime. So that way there we can clarify anything about these topics
for you, and therefore you're going to be successful in the real world as well as on the
certification exam. All right. Great job there today, folks. Well done.