WEBVTT

0:00:08.260000 --> 0:00:12.200000
 So in the last set of videos, I had a
 pretty good what I think is an example

0:00:12.200000 --> 0:00:18.440000
 of using GNS3 to build up a CCNA
 level EI-JRP routing lab.

0:00:18.440000 --> 0:00:22.040000
 So but we also have to know a little
 bit about switching for the CCNA.

0:00:22.040000 --> 0:00:26.900000
 So let's do that as well as build
 up a CCNA level switching lab.

0:00:26.900000 --> 0:00:30.480000
 So as usual, step number one for you
 if you were going to design a lab

0:00:30.480000 --> 0:00:34.760000
 of your own is to write out your objectives,
 what you want to accomplish.

0:00:34.760000 --> 0:00:38.720000
 Step number two, draw your topology diagram
 on a piece of paper or something

0:00:38.720000 --> 0:00:41.360000
 so you have it plotted out and you
 know what you're going to build.

0:00:41.360000 --> 0:00:45.020000
 Then open up GNS3 and actually
 start building it.

0:00:45.020000 --> 0:00:47.840000
 So what kind of objectives
 do we have for this?

0:00:47.840000 --> 0:00:51.160000
 Well, this is going to be pretty much
 all the encompassing lab here.

0:00:51.160000 --> 0:00:53.440000
 We're going to have a
 lot of stuff going on.

0:00:53.440000 --> 0:00:57.020000
 So in this particular topology, we're
 going to create three routers and

0:00:57.020000 --> 0:01:02.620000
 three switches. Of those switches, one
 of them will be the built-in Ethernet

0:01:02.620000 --> 0:01:08.080000
 switch node and the other two
 will be ether switch routers.

0:01:08.080000 --> 0:01:10.800000
 So if you're trying to replicate this
 lab yourself, you're definitely

0:01:10.800000 --> 0:01:14.920000
 going to need some iOS software version
 that's capable of supporting the

0:01:14.920000 --> 0:01:19.840000
 ether switch module, like the 2600 series
 or the 3700 series or something

0:01:19.840000 --> 0:01:23.800000
 like that. Okay, so here
 is the objectives.

0:01:23.800000 --> 0:01:25.140000
 Here are the objectives
 we want to do.

0:01:25.140000 --> 0:01:29.180000
 So number one, as far as the ether switch
 routers are concerned, whenever

0:01:29.180000 --> 0:01:33.940000
 you connect them together, the ports
 on both sides have to be the same.

0:01:33.940000 --> 0:01:37.320000
 In other words, what I mean by that is
 you're not to build this lab where

0:01:37.320000 --> 0:01:41.820000
 one side of the cable is connecting
 to port 1 slash 6 and the other side

0:01:41.820000 --> 0:01:44.380000
 is connecting to port 1 slash 2.

0:01:44.380000 --> 0:01:46.780000
 They should both be the
 same port number.

0:01:46.780000 --> 0:01:50.600000
 And that's going to be relevant because
 when we manipulate spanning tree,

0:01:50.600000 --> 0:01:52.320000
 that's going to be important.

0:01:52.320000 --> 0:01:59.260000
 Next, we cannot manually configure
 VLANs 4 or 5 on the VTP client.

0:01:59.260000 --> 0:02:02.280000
 And I'll show you in just a second what
 the topology is that we're going

0:02:02.280000 --> 0:02:05.300000
 to build up. But we're going
 to be using VTP in here.

0:02:05.300000 --> 0:02:07.500000
 And one of the switches is
 going to be a VTP client.

0:02:07.500000 --> 0:02:11.580000
 So basically, that client is going
 to have to dynamically learn about

0:02:11.580000 --> 0:02:17.860000
 these VLANs 4 and 5 via
 VTP from the VTP server.

0:02:17.860000 --> 0:02:21.440000
 And then the second to the last bullet,
 ensure that packets sent between

0:02:21.440000 --> 0:02:25.540000
 router 1 and router 2 on VLAN 5 traverse
 across the two ether switch routers

0:02:25.540000 --> 0:02:27.660000
 on the highest numbered ports.

0:02:27.660000 --> 0:02:31.160000
 I'll clarify that in just a second when
 I show you the topology diagram.

0:02:31.160000 --> 0:02:33.500000
 And then we're not going to use any
 routing here or the static routes.

0:02:33.500000 --> 0:02:35.720000
 This is not a dynamic routing lab.


0:02:35.720000 --> 0:02:38.740000
 So we're just going to use simple static
 routes for end-to-end connectivity.

0:02:38.740000 --> 0:02:43.540000
 So this is what we're actually
 going to build right here.

0:02:43.540000 --> 0:02:45.560000
 So how is this going to work?

0:02:45.560000 --> 0:02:51.800000
 Well, so as far as the built-in ethernet
 switch node is concerned, these

0:02:51.800000 --> 0:02:54.760000
 ethernet switch nodes do
 not do spanning trees.

0:02:54.760000 --> 0:03:01.100000
 So you never want to connect an ethernet
 switch node to an ether switch

0:03:01.100000 --> 0:03:04.320000
 router. Because this is
 kind of like a hub.

0:03:04.320000 --> 0:03:07.180000
 It could lead you to have bridging
 loops because it doesn't implement

0:03:07.180000 --> 0:03:11.660000
 spanning trees. So, but we still want
 to get experience with it with how

0:03:11.660000 --> 0:03:12.900000
 to use it in GNS3.

0:03:12.900000 --> 0:03:15.440000
 So that's why I put it in here, although,
 you know, technically you're

0:03:15.440000 --> 0:03:18.160000
 not going to be tested on
 that at the CCNA level.

0:03:18.160000 --> 0:03:23.100000
 So here, we're going to test your ability
 to implement the ethernet switch

0:03:23.100000 --> 0:03:27.340000
 node, make sure that one of the
 links is trunking with 802.1q.

0:03:27.340000 --> 0:03:31.440000
 The other two links are access
 ports in VLANs 2 and 3.

0:03:31.440000 --> 0:03:34.780000
 And they'll pretty much max out the
 capabilities that you can do in the

0:03:34.780000 --> 0:03:36.240000
 ether switch node.

0:03:36.240000 --> 0:03:41.280000
 And then as far as these two ether switch
 routers are concerned, you're

0:03:41.280000 --> 0:03:42.620000
 going to have two links.

0:03:42.620000 --> 0:03:44.680000
 We're going to have some
 redundant links here.

0:03:44.680000 --> 0:03:47.700000
 That's going to allow us to do some
 spanning tree manipulation.

0:03:47.700000 --> 0:03:51.220000
 One of them, though, Guy on the top
 is going to be my VTP server.

0:03:51.220000 --> 0:03:54.600000
 The device on the bottom
 will be a VTP client.

0:03:54.600000 --> 0:04:00.100000
 Once you have your 802.1q links functional,
 VLANs 4 and 5, which will

0:04:00.100000 --> 0:04:05.260000
 be configured up here on the server,
 should be propagated downstream to

0:04:05.260000 --> 0:04:08.520000
 the client. And you
 should see that.

0:04:08.520000 --> 0:04:13.240000
 And then lastly, you know, whatever port
 numbers you select are completely

0:04:13.240000 --> 0:04:18.180000
 up to you. But let's say, for example,
 just to put something in here,

0:04:18.180000 --> 0:04:23.320000
 we had port 1 slash 2 here, which would
 then connect to 1 slash 2 down

0:04:23.320000 --> 0:04:29.820000
 here. And let's say this one was 1
 slash 4 connecting to 1 slash 4.

0:04:29.820000 --> 0:04:36.440000
 As far as spanning tree manipulations
 concerned, the objective here is

0:04:36.440000 --> 0:04:42.080000
 that when router 1, so router 1 knows
 that both these routers are going

0:04:42.080000 --> 0:04:43.560000
 to participate in 2 VLANs.

0:04:43.560000 --> 0:04:46.140000
 So they're actually going
 to have two IP addresses.

0:04:46.140000 --> 0:04:53.000000
 Router 1 will be 1.2.4.1 and
 he'll also have 1.2.5.1.

0:04:53.000000 --> 0:04:59.560000
 And over here, router 2 on this interface,
 he'll have 1.2.4.2 and 1.2

0:04:59.560000 --> 0:05:04.060000
.5.2. That's why these links
 have to be 802.1q trunk.

0:05:04.060000 --> 0:05:06.740000
 So they support two
 separate subnets.

0:05:06.740000 --> 0:05:14.280000
 So the idea is when router 1 on VLAN
 5 pings router 2 on VLAN 5, in other

0:05:14.280000 --> 0:05:21.020000
 words, when from router 1 you ping
 1.2.5.2, those packets should take

0:05:21.020000 --> 0:05:26.440000
 this path here. They should take the
 highest numbered port, whatever that

0:05:26.440000 --> 0:05:28.420000
 is in your particular topology.

0:05:28.420000 --> 0:05:31.440000
 And then of course the return traffic
 should also take that particular

0:05:31.440000 --> 0:05:37.220000
 path. As far as spanning tree is concerned,
 this link here should be blocked.

0:05:37.220000 --> 0:05:42.420000
 There should not be any traffic on
 VLAN 5 only going across that link.

0:05:42.420000 --> 0:05:44.060000
 It should be blocked.

0:05:44.060000 --> 0:05:47.780000
 Okay, so that being the case, that
 concludes this particular video.

0:05:47.780000 --> 0:05:50.720000
 In the next video, we're going to start
 building this topology within

