(theatrical music)
- So in the last set of videos,
I had a pretty good what I think as an example
of using GNS3 to build up a CCNA level EIGRP routing lab.
So, but we also have to know a little bit about
switching for the CCNA, so let's do that as well.
Let's build up a CCNA level switching lab.
So as usual, step number one for you
if you were going to design a lab of your own
is to write out your objectives,
what you want to accomplish.
Step number two, draw your topology diagram
on a piece of paper or something so you have it plotted out
and you know what you're going to build.
Then open up GNS3 and actually start building it.
So what kind of objectives do we have for this?
Well, this is gonna be pretty much
an all encompassing lab here.
We're gonna have a lot of stuff going on.
So in this particular topology,
we're gonna create three routers and three switches.
Of those switches,
one of them will be the built-in Ethernet Switch Node
and the other two will be EtherSwitch Routers.
So if you're trying to replicate this lab yourself,
you're definitely gonna need some IOS software version
that's capable of supporting the EtherSwitch module
like the 2600 series or the 3700 series
or something like that.
Okay, so here are the objective we wanna do.
Number one, as far as the EtherSwitch Routers are concerned,
whenever you connect them together,
the ports on both sides have to be the same.
In other words, what I mean by that is
you're not to build this lab
where one side of the cable is connecting to port 1/6
and the other side is connecting to port 1/2.
They should be the same port number
and that's gonna be relevant
because when we manipulate spanning tree,
that's gonna be important.
Next, we cannot manually configure VLANs-4 or 5
on the VTP Client and I'll show you in just a second
what the topology is that we're gonna build up,
but we're gonna be using VTP in here
and one of the switches is gonna be a VTP Client
so basically that client is gonna have to dynamically learn
about these VLANs-4 and 5 via VTP, from the VTP server.
And then the second to the last bullet,
ensure that packets send between router one and router two
on VLAN-5 traverse across the two EtherSwitch Routers
on the higher-numbered ports.
I'll clarify that in just a second
when I show you the topology diagram.
And then we're not gonna use any routing here
other than static routes.
This is not a dynamic routing lab
so we're just gonna use simple static routes
for end-to-end connectivity.
So this is what we're actually going to build right here.
So how is this gonna work?
Well, so as far as the built-in
Ethernet Switch Node is concerned,
these Ethernet Switch Nodes do not do spanning tree,
so you never want to connect an Ethernet Switch Node
to an EtherSwitch Router because this is like a hub.
It could lead you to have bridging loops
because it doesn't implement spanning tree,
but we still wanna get experience with it,
with how to use it in GNS3 so that's why I put it in here,
although technically you're not gonna be tested on that
at the CCNA level.
So here, we're gonna test your ability to implement
the Ethernet Switch Node,
make sure that one of the links is trunking with 802.1q,
the other two links are access ports in VLANs-2 and 3
and they'll pretty much max out the capabilities
that you can do in the EtherSwitch Node.
And then as far as these two
EtherSwitch Routers are concerned,
you're gonna have two links.
We're gonna have some redundant links here
and that's gonna allow us to do
some spanning tree manipulation.
One of them, the guy in the top is gonna be my VTP Server.
The device on the bottom will be a VTP Client.
Once you have your 802.1q links functional,
VLANs-4 and 5 which will be configured up here on the server
should be propagated downstream to the client
and you should see that.
And then lastly, whatever port numbers you select
are completely up to you,
but let's say for example, just to put something in here,
we had port 1/2 here
which would then connect to 1/2 down herea
and let's say this one was 1/4 connecting to 1/4.
As far as spanning tree manipulation is concerned,
the objective here is that when router one,
so router one knows,
both of these routers are gonna participate in two VLANs
so they're actually gonna have two IP addresses.
Router one will be 1.2.4.1 and he'll also have 1.2.5.1.
And over here, router two on this interface,
he'll have 1.2.4.2 and 1.2.5.2.
That's why these links have to be 802.1q trunks
so they support two separate subnets.
So the idea is when router one on VLAN-5
pings router two on VLAN-5,
in other words, when from router one you ping 1.2.5.2,
those packets should take this path here.
They should take the highest-numbered port,
whatever that is in your particular topology.
And then of course the return traffic
should also take that particular path.
As far as spanning tree is concerned,
this link here should be blocked.
There should not be any traffic on VLAN-5 only
going across that link.
It should be blocked.
Okay, so that being the case,
that concludes this particular video.
In the next video,
we're gonna start building this topology within GNS3.
(theatrical music)