(intense music)
- Okay, here we are on Part 3 of our CCNA Switch Lab,
and now we're finally gonna start doing some switching stuff
by jumping over to those EtherSwitch modules and our Routers
and configuring the switching component of that.
So, here we're gonna configure VTP and VLANS on the routers.
By the time we're done with this,
we should have end-to-end connectivity all the way across,
from one router to the other at the far side.
We won't be done yet, because we still have to manipulate
a little spanning tree,
we'll do that in the final video,
but we should have end-to-end connectivity
by the time we're done with the required tasks here.
Okay, so looking at our topology diagram.
We can see that right now, what's left for us
is that we have to configure VLANs 4 and 5
in this router right here.
We wanna make sure that VTP is set up
so this guy's a client,
and he learns of the VLANs
via VTP.
So let's start with VTP and then do the VLANs.
So I'm gonna go on to the EtherSwitch Router 2,
which in this particular case...
Now before I do this,
I've been saving my configs all along the way,
so I'm gonna take a snapshot.
I'm gonna turn everybody off,
take a snapshot right now,
and we'll call this
No-VLAN-or-STP.
Okay, close, let's bring everything back online.
The majority of the configuration for this
is gonna be between EtherSwitch 1 and EtherSwitch 2.
So, let's just bring both of those up.
Alright, let's put them in the correct order here.
Okay, EtherSwitch 1, which is the guy on top.
Let's start with EtherSwitch 2 as the VTP client.
So, here with VTP, first we have to create
a VTP domain name.
We'll just give it INE.
And we'll make it the same here.
Okay.
EtherSwitch 1 is gonna be a VTP server by default,
because that's the way Cisco works it,
so we just have to configure EtherSwitch 2
as a client.
Okay, great.
Now, in order for VTP to work,
it has to work over functional VLAN trunks.
Now, these EtherSwitch modules,
unlike real physical switches,
do not support the dynamic trunking protocol.
If these were real switches, the lengths between them
quite possibly would already be 802.1q trunks,
without us having to do anything.
Because they probably dynamic and have exchanged DTP.
Or maybe not.
But in this particular case, in order to form a trunk,
we have to manually do it on EtherSwitch modules.
We cannot use dynamic desirable, or dynamic auto.
Those keywords don't even exist for us.
So, that being the case,
if I go back to my topology diagram,
we've got 1/9 and 1/15.
So I'll just go ahead and use the Interface Range command
for that.
Interface range, fast Ethernet 1/9,
and because it's a non-contiguous range,
I have to use the comma.
And we'll just say switchport mode trunk.
No shut, just for good measure.
Save our configuration.
Okay, so that's EtherSwitch 2.
Now, let's just do the same thing
in EtherSwitch 1.
Interface range, fast Ethernet 1/9, 1/15.
Switchport mode trunk.
Save it.
Okay, and for the CCNA Routing and Switching exam,
you should be aware of what command you would type
to verify if the trunks are actually functional.
There's actually a couple things you could do,
but my favorite command is show interfaces trunk.
And it shows us,
right here.
You could also do show interface,
type in the interface name,
and then switchport.
And what you're looking for is operational mode.
Administrative mode means, what am I configured to do?
Operational mode means, what am I actually doing?
And right now, it says, trunk.
So, we're good to go there.
So now the last thing we should be able to do is
here in our VTP server,
we should be able to create our two VLANs,
VLANs 4 and 5, and we should see them propagated downstream
to our VTP client.
Vlan 4-5.
That allows us to create multiple VLANs at the same time.
Save our configuration.
Now, if we were in a regular switch,
we could just do the show VLAN command
to see what VLANs are in here.
But in this particular case,
we have to do show VLAN-switch,
and we can see that VLANs 4 and 5 have been created.
Show interface trunk,
verifies for us that those VLANs are allowed on the trunk.
They're actually, right now, they are active.
We can see that.
And so now if we go down to switch 2,
hopefully it has learned of those VLANs via VTP.
Show VLAN-switch.
And he has.
He has learned of those.
Save our configuration.
So, at this point now, our trunks are functional
all the way across.
Whatever VLANs we are going to be using
have been configured and have been propagated.
If we go to our diagram,
Router 1 now should be able to ping
either one of these IP address on Router 3,
and he should be able to get a response back.
So, let's see if that is indeed the case.
Alright, let's bring up Router 1.
Here's the moment of truth,
ping 2.3.2.3.
Okay, this is good though.
This is gonna give us a little bit of troubleshooting
experience.
Okay, so step number one.
We previously configured some static routes in here,
but let's verify.
Does he actually have the routing information to get there?
Show IP route.
Okay, so he does have a static route.
Can he ping his neighbor?
His next hop neighbor.
Ping 1.2.4.2.
Okay, he is not pinging.
Ah, I think I know what the problem is.
We forgot one little step, I believe.
I think the problem is
we forgot to configure this interface right here
on EtherSwitch 2 as a trunk.
I think that's our problem.
So let's go back to EtherSwitch 2.
Show run interface fast Ethernet 1/0.
And yes, it is not configured as a trunk.
Okay, so, config T interface fast Ethernet 1/0.
Switchport mode trunk.
And that should be all we have to do.
Now, it's carrying all the VLANs.
So now, we should be able to ping,
Router 1 should be able to ping Router 2.
Might take a little bit of time,
cause remember spanning tree has to converge
and go from listening to learning to forwarding,
and that takes a little bit of time.
Let's verify that spanning tree for VLANs 4 and 5
does have a forwarding path.
So what we should see...
I don't know which one of these switches
is gonna be the spanning tree root bridge,
we'll get into that in the very last video of this section,
but what we should see is that VLANs 4 and 5
are both allowed on this interface
because it's trunking.
This interface should be in the forwarding state.
It should be designated for both VLANs 4 and 5.
Same thing over here.
Ah, I think that's the other problem.
I forgot to configure this as an 802.1q trunk.
That's probably what's the problem.
Let's go over to my diagram here,
my GNS-3,
and I need to configure fast Ethernet 1/0 on EtherSwitch 1.
Switchport mode trunk.
Alright, let's wait for it to go into the forwarding state.
Show spanning-tree, interface fast Ethernet 1/0.
Right now it says that it is listening,
so we have to wait until it goes forwarding.
And now it is learning,
and now it is forwarding.
Alright, so now, we should have end-to-end connectivity.
First of all, can Router 1 ping Router 2.
Well, we might need a little more troubleshooting here.
Alright, let's see if we can troubleshoot this.
Starting with the physical layer.
Show IP interface brief.
And fast Ethernet 0/0 is what we're looking for.
It is up,
the very subinterfaces are up.
And the very subinterfaces have been allocated
that IP addresses in the correct
VLANs and subnets,
so, that looks right.
We already confirmed that he has the correct static routes.
Okay, so there's nothing wrong on Router 1.
Okay, let's move down the chain now.
Let's go over to EtherSwitch 2.
EtherSwitch 2, let's make sure that fast Ethernet 1/0
is trunking.
Show interface fast Ethernet 1/0, switchport.
Operational mode is trunk.
Show interface trunk.
1/0 is on, and it is allowing VLANs 4 and 5.
Okay, that's good.
We also see these other two interfaces leading upstream to
EtherSwitch 1 are on, also allowing VLANs 4 and 5.
Let's look at the spanning tree state of VLAN 4.
VLAN 4 is executing, basically, 802.1d,
and what we're looking for here
is it says that 1/0, which goes down to Router 1,
is forwarding.
1/9, which goes upstream to EtherSwitch 1,
is forwarding.
And 1/15 is blocking.
That's fine.
We just need one of those upstream interfaces.
So, right now, the one here on the left
is the one that's in the forwarding state.
That's for VLAN 4, what about VLAN 5.
I would expect VLAN 5 to look exactly the same.
Yep, the port going to the router is forwarding,
and the lower numbered port
is forwarding going upstream.
Everything looks fine on EtherSwitch 2.
Now, let's go over to EtherSwitch 1.
Show spanning-tree VLAN 4.
Okay, so 1/0, which goes across to Router 2 is forwarding.
1/9 is forwarding,
1/15 is forwarding.
Okay, so this guy's probably the root bridge.
Okay, so, so far everything looks fine.
Now let's go across to Router 2.
Last thing to check here.
Show run, let's take a look at his fast Ethernet 0/0.
Okay, ah, here's our problem.
Fast Ethernet 0/0, I forgot to bring it up.
It's shut down.
That could explain our problem.
Show IP interface brief.
Alright, fast Ethernet 0/0, which is trunking, is up,
and the other two interfaces are up.
Okay, so now, which was a good troubleshooting exercise,
we should be able to ping
end-to-end from R1.
Ping 2.3.2.3, let's go for the gold here.
Let's try to ping all the way.
Come on, you can do it.
There we go.
Fantastic.
And ping the other side, 3.2.3.3.
He has to arp for it.
Actually, he doesn't have to arp for it,
he does have to arp for his next hop.
And then we have success.
Okay, so at this point, let me bring the diagram over here.
Let me just renumber these interfaces for a second
because these are not correct.
Okay, so we have
1/9,
1/15,
1/9,
1/15,
and this over here I believe is 1/0.
Okay, so right now,
because of the way spanning tree is configured,
by the way, just ended up,
we didn't configure it this way,
what we've got is
this right here is in the blocking state.
The remaining three interfaces are forwarding.
And so when Router 1 pings anything over here,
everything he pings
is gonna have to take the forwarding path.
It's gonna go this way,
both the pings and the reply packets.
However, if you remember,
if we go right back to our original lab
specifications, our objectives,
it said, as we can see here,
ensure that packets sent between Router 1 and Router 2
traverse across the higher-numbered ports.
So right now, it's going across
the lowest-numbered ports, 1/9.
But reality, we're supposed to be having it go across
the highest-numbered ports.
Which in this case,
means we need to somehow get this path forwarding
and this path blocking.
And that's the last thing we're gonna do
in the very next video.
(intense music)