WEBVTT

0:00:08.140000 --> 0:00:11.600000
 In this video, I'd like to talk about
 an alternative way of doing switching

0:00:11.600000 --> 0:00:15.720000
 in your GNS3 Topology by using
 the Ether switch router.

0:00:15.720000 --> 0:00:19.400000
 And if you want to practice iOS commands
 that relate to switches, this

0:00:19.400000 --> 0:00:20.600000
 is what you're going
 to want to do.

0:00:20.600000 --> 0:00:24.340000
 So, before we actually look at how
 to do this, let's talk about how do

0:00:24.340000 --> 0:00:26.420000
 I get this into my topology
 in the first place.

0:00:26.420000 --> 0:00:28.800000
 This is not a built-in node.

0:00:28.800000 --> 0:00:33.360000
 This is a special iOS image, support
 on a certain range of routers that

0:00:33.360000 --> 0:00:35.060000
 give the routers this ability.

0:00:35.060000 --> 0:00:37.000000
 So, how do we figure that out?

0:00:37.000000 --> 0:00:43.200000
 Well, the first thing you're going
 to want to do is go to GNS3.com.

0:00:43.200000 --> 0:00:46.420000
 And go ahead and log in.

0:00:46.420000 --> 0:00:54.620000
 And then from there, you're going to
 want to click on Support, followed

0:00:54.620000 --> 0:00:57.800000
 by Documentation.

0:00:57.800000 --> 0:01:03.400000
 And then from here, click on where
 it says Adding iOS Images.

0:01:03.400000 --> 0:01:09.140000
 We already saw this window before a couple
 videos back when we were talking

0:01:09.140000 --> 0:01:12.380000
 about what iOS images were
 suitable for GNS3.

0:01:12.380000 --> 0:01:14.880000
 So, I'm going to go back to that exact
 same document that we were looking

0:01:14.880000 --> 0:01:19.620000
 at next time, which is viewable right
 here from where it says in this

0:01:19.620000 --> 0:01:24.180000
 document. We're going to want to click
 on those words, which will bring

0:01:24.180000 --> 0:01:26.140000
 up another document.

0:01:26.140000 --> 0:01:31.640000
 Okay, so the EtherSwitch module is an
 actual module that goes in a network

0:01:31.640000 --> 0:01:34.480000
 module slot within a router.

0:01:34.480000 --> 0:01:39.620000
 So any of the routers that you see in
 this list that support NM's or network

0:01:39.620000 --> 0:01:43.380000
 modules will support the
 EtherSwitch module.

0:01:43.380000 --> 0:01:45.260000
 So for example, look
 at the 1700 series.

0:01:45.260000 --> 0:01:51.780000
 It says it supports two sub slots
 for Wix and no network slots.

0:01:51.780000 --> 0:01:55.880000
 So if you get yourself a 1700 series
 iOS software image, you will not

0:01:55.880000 --> 0:01:59.020000
 have access to the
 EtherSwitch module.

0:01:59.020000 --> 0:02:03.660000
 So if we scroll down past all of these,
 past the 7200s at the bottom,

0:02:03.660000 --> 0:02:08.000000
 it actually has a section right there
 on Cisco Catalyst switches.

0:02:08.000000 --> 0:02:10.640000
 And it says that you can, as long as you
 can get an iOS image that supports

0:02:10.640000 --> 0:02:17.980000
 the 2600s, or 3700 series, then you
 will have access to the EtherSwitch

0:02:17.980000 --> 0:02:21.440000
 module. In my particular example in
 this video, I'm going to be using

0:02:21.440000 --> 0:02:24.340000
 a 3725 for the EtherSwitch.

0:02:24.340000 --> 0:02:27.700000
 Now one other thing that's important
 to know about this is knows that

0:02:27.700000 --> 0:02:32.780000
 it says that the EtherSwitch module,
 because it's not an ASIC-based, a

0:02:32.780000 --> 0:02:38.100000
 hardware-based switch like a Catalyst
 6500 or a Catalyst 4500 or something

0:02:38.100000 --> 0:02:41.920000
 like that, it's not going to support
 the full range of features that you

0:02:41.920000 --> 0:02:44.900000
 would have in a real
 physical switch.

0:02:44.900000 --> 0:02:49.120000
 And right here in this document, it actually
 tells you, if I zoom in here

0:02:49.120000 --> 0:02:54.040000
 a little bit, these are all the features
 which are not supported by the

0:02:54.040000 --> 0:02:55.140000
 EtherSwitch module.

0:02:55.140000 --> 0:02:58.240000
 So there are quite a bit of them.

0:02:58.240000 --> 0:03:00.380000
 And it's just a limitation
 of that particular module.

0:03:00.380000 --> 0:03:05.100000
 Even if you had a real 3700 router and
 you had a real EtherSwitch module

0:03:05.100000 --> 0:03:09.020000
 plugged into it, you would still have
 a series limitation on these switches

0:03:09.020000 --> 0:03:11.480000
 right here, on these
 various features.

0:03:11.480000 --> 0:03:14.460000
 So let me, there's a lot of stuff in
 here, especially if you're a CCNA

0:03:14.460000 --> 0:03:17.500000
 candidate, I want to point out some
 of the features that unfortunately

0:03:17.500000 --> 0:03:22.680000
 are missing from this device that you are
 going to want to have some practice

0:03:22.680000 --> 0:03:24.080000
 with if you can.

0:03:24.080000 --> 0:03:27.980000
 So number one, and I'm sure it's somewhere
 here on this list, I just am

0:03:27.980000 --> 0:03:32.580000
 not looking at it right now, but when
 it comes to trunking, 802.1Q trunking,

0:03:32.580000 --> 0:03:37.480000
 you're going to want to learn how to
 configure and monitor dynamic trunks

0:03:37.480000 --> 0:03:41.000000
 that use DTP, the dynamic
 trunking protocol.

0:03:41.000000 --> 0:03:45.880000
 So in a real switch, it would be switch
 port mode dynamic, and then you'd

0:03:45.880000 --> 0:03:49.980000
 select auto or desirable, switch port
 mode dynamic auto or desirable.

0:03:49.980000 --> 0:03:51.320000
 That's not available here.

0:03:51.320000 --> 0:03:55.360000
 In the EtherSwitch module, all you
 can do is statically configure and

0:03:55.360000 --> 0:03:58.120000
 interface as a trunk with
 switch port mode trunk.

0:03:58.120000 --> 0:03:59.500000
 There is no dynamic option.

0:03:59.500000 --> 0:04:04.360000
 Another thing, when it comes to EtherChannels,
 you can create EtherChannels

0:04:04.360000 --> 0:04:07.540000
 in here, but you cannot create
 dynamic EtherChannels.

0:04:07.540000 --> 0:04:10.740000
 So once again, with EtherChannels in
 a real switch, you have a choice

0:04:10.740000 --> 0:04:16.180000
 if you want to have used either the
 port aggregation protocol or LACP.

0:04:16.180000 --> 0:04:21.620000
 Once again, that would be like desirable
 or auto or something like that,

0:04:21.620000 --> 0:04:26.360000
 passive active. Those keywords also not
 available in the EtherSwitch module.

0:04:26.360000 --> 0:04:31.980000
 In, when it comes to VTP, the VLAN trunking
 protocol, what I've noticed

0:04:31.980000 --> 0:04:35.220000
 is that in real switches, and you'll
 see this in documentation, if one

0:04:35.220000 --> 0:04:38.840000
 switch is configured with a VTP domain
 name, and then it trunks with a

0:04:38.840000 --> 0:04:42.940000
 second switch, there's a functional
 trunk here, and the second switch

0:04:42.940000 --> 0:04:45.040000
 has no VTP domain name.

0:04:45.040000 --> 0:04:46.400000
 It's empty, it's null.

0:04:46.400000 --> 0:04:51.400000
 The second switch can learn of the VTP
 domain name from the first switch.

0:04:51.400000 --> 0:04:54.360000
 That's not going to happen
 in this particular case.

0:04:54.360000 --> 0:04:57.640000
 I'm not exactly sure in the background
 why that's not happening because

0:04:57.640000 --> 0:05:01.480000
 these do support VTP
 to a limited extent.

0:05:01.480000 --> 0:05:06.580000
 They support VTP version 1 and 2, not
 VTP version 3, but still for a CCNA

0:05:06.580000 --> 0:05:10.800000
 candidate, pretty much all the VTP stuff
 you'd want to do is support on

0:05:10.800000 --> 0:05:14.100000
 here, but not the dynamic
 learning of domain names.

0:05:14.100000 --> 0:05:19.880000
 At the CCNA level, you have to learn
 about rapid spanning tree or rapid

0:05:19.880000 --> 0:05:25.760000
 PVST. Unfortunately, these Ether switch
 modules only support 802.1D or

0:05:25.760000 --> 0:05:30.140000
 PVST normal, PVST
 plus with 802.1D.

0:05:30.140000 --> 0:05:33.580000
 They do not support rapid spanning
 tree, they do not support multiple

0:05:33.580000 --> 0:05:37.120000
 spanning trees, and MST is something
 you have to learn to configure and

0:05:37.120000 --> 0:05:41.460000
 troubleshoot at the CCNP
 level and above.

0:05:41.460000 --> 0:05:45.200000
 One big feature that's missing from
 here, which is unfortunate because

0:05:45.200000 --> 0:05:48.600000
 the CCNA, a lot of times it's going
 to hit you hard on this feature, is

0:05:48.600000 --> 0:05:52.160000
 port security. When you're learning
 about switching, one of the features

0:05:52.160000 --> 0:05:56.220000
 that they're expecting to know is port
 security, how to configure it,

0:05:56.220000 --> 0:06:00.120000
 the various different keywords and gotchas
 that go along with port security.

0:06:00.120000 --> 0:06:05.040000
 Unfortunately, this Ether switch module
 also does not support port security.

0:06:05.040000 --> 0:06:09.080000
 Now when you get up to the CCNP level,
 this big list here takes on even

0:06:09.080000 --> 0:06:12.600000
 more relevance. There's a lot more features
 that are not supported here.

0:06:12.600000 --> 0:06:16.900000
 So if you're at the CCNP level studying
 for your switch exam or beyond,

0:06:16.900000 --> 0:06:21.200000
 like the CCIE level and you need access
 to all these missing features,

0:06:21.200000 --> 0:06:24.720000
 unfortunately at that point, you're
 going to only have two options.

0:06:24.720000 --> 0:06:29.400000
 Either get yourself a real physical
 switch, which is the ideal option.

0:06:29.400000 --> 0:06:32.340000
 And there are ways you can actually
 connect a real physical switch into

0:06:32.340000 --> 0:06:35.220000
 your GNS3 topology if
 you need to do that.

0:06:35.220000 --> 0:06:38.620000
 Or get your hands on L2IOU.

0:06:38.620000 --> 0:06:43.800000
 But even L2IOU doesn't have all the
 things supported in a real switch.

0:06:43.800000 --> 0:06:46.580000
 There are some features in L2IO
 that are not supported.

0:06:46.580000 --> 0:06:49.940000
 So if you want the full range of everything,
 you're going to have to have

0:06:49.940000 --> 0:06:51.720000
 a real physical switch.

0:06:51.720000 --> 0:06:54.860000
 So now that we've spent enough time on
 talking about what this thing can't

0:06:54.860000 --> 0:06:57.880000
 do, let's take a look
 at what it can do.

0:06:57.880000 --> 0:07:02.580000
 So we know now that any router that supports
 network modules will support

0:07:02.580000 --> 0:07:05.900000
 this Ether switch module.

0:07:05.900000 --> 0:07:09.600000
 So what I'm going to do if I haven't
 already done this, I'm going to go

0:07:09.600000 --> 0:07:12.280000
 to Edit and Preferences.

0:07:12.280000 --> 0:07:15.260000
 Under Dynamips, I'm going
 to click on iOS routers.

0:07:15.260000 --> 0:07:18.440000
 And I want to add a new router because
 if you had an Ether switch router,

0:07:18.440000 --> 0:07:19.420000
 it would show up here.

0:07:19.420000 --> 0:07:20.800000
 You would see it in this list.

0:07:20.800000 --> 0:07:21.940000
 But we don't see one.

0:07:21.940000 --> 0:07:24.160000
 So I'm going to click on New.

0:07:24.160000 --> 0:07:28.360000
 And I'm going to use my
 existing image, 3725.

0:07:28.360000 --> 0:07:35.020000
 In this particular case, I'm just going
 to say C3725, let's say Ether

0:07:35.020000 --> 0:07:39.520000
 switch. But this is the
 key part right here.

0:07:39.520000 --> 0:07:43.260000
 When adding this, you want to select
 this option where it says this is

0:07:43.260000 --> 0:07:44.920000
 an Ether switch router.

0:07:44.920000 --> 0:07:47.060000
 And actually by doing that,
 it changes the name for you.

0:07:47.060000 --> 0:07:48.400000
 I didn't even need
 to change the name.

0:07:48.400000 --> 0:07:51.000000
 So that is the critical
 component right there.

0:07:51.000000 --> 0:07:55.680000
 If you don't select that, that Ether
 switch network module will not be

0:07:55.680000 --> 0:07:58.360000
 available to you on
 the next screen.

0:07:58.360000 --> 0:07:59.620000
 So we need to select that.

0:07:59.620000 --> 0:08:03.440000
 And now when I hit Next, select the
 appropriate amount of memory, which

0:08:03.440000 --> 0:08:06.700000
 I think is 256 for this
 particular image.

0:08:06.700000 --> 0:08:11.340000
 And now you can see by default, it populates
 one of your network module

0:08:11.340000 --> 0:08:14.560000
 slots with a 16 port
 Ether switch module.

0:08:14.560000 --> 0:08:17.320000
 Now if you want to, if 16 ports is
 not enough, you could populate with

0:08:17.320000 --> 0:08:21.120000
 another one. Or certainly, if you want
 to use this router for routing

0:08:21.120000 --> 0:08:26.120000
 as well as switching, let's put in
 a four port serial card as well.

0:08:26.120000 --> 0:08:30.080000
 And because this is a 3725, we
 have some wick slots available.

0:08:30.080000 --> 0:08:33.020000
 I'm just going to leave these empty
 because I don't care about those for

0:08:33.020000 --> 0:08:34.900000
 this demonstration.

0:08:34.900000 --> 0:08:38.500000
 And we're going to want
 to find an idle PC.

0:08:38.500000 --> 0:08:39.740000
 And this is normal.

0:08:39.740000 --> 0:08:41.020000
 Don't worry too much about this.

0:08:41.020000 --> 0:08:44.340000
 We'll just have to wait for
 about, oh, 30 seconds or so.

0:08:44.340000 --> 0:08:50.200000
 And then it should find an idle PC
 value for this particular platform.

0:08:50.200000 --> 0:08:53.700000
 And there we go.

0:08:53.700000 --> 0:08:56.260000
 It has found an idle PC value, which
 is what we were looking for.

0:08:56.260000 --> 0:08:59.840000
 So click OK and finish.

0:08:59.840000 --> 0:09:02.840000
 And now we can see up in
 the available platforms.

0:09:02.840000 --> 0:09:06.700000
 Now we have, if I expand this a little
 bit, it actually won't let me,

0:09:06.700000 --> 0:09:08.600000
 we have an Ether switch router.

0:09:08.600000 --> 0:09:12.860000
 So click OK. So now in this particular
 topology, which is the topology

0:09:12.860000 --> 0:09:16.320000
 we just saw in the last video, I'm
 going to accomplish the same thing.

0:09:16.320000 --> 0:09:19.200000
 But this time, I'm going to use the
 Ether switch router so I can have

0:09:19.200000 --> 0:09:23.080000
 a little bit more experience configuring
 iOS switching commands.

0:09:23.080000 --> 0:09:27.760000
 So click once again on your switching
 tab or switching button.

0:09:27.760000 --> 0:09:34.000000
 And now we have an Ether
 switch router.

0:09:34.000000 --> 0:09:37.360000
 OK. And so let's go ahead and
 connect its interfaces.

0:09:37.360000 --> 0:09:40.460000
 Now let's talk a little bit about
 its interfaces for just a second.

0:09:40.460000 --> 0:09:41.960000
 We'll zoom in here.

0:09:41.960000 --> 0:09:47.600000
 Because this is a 37.25, the fast ethernet
 interfaces that are on the

0:09:47.600000 --> 0:09:52.260000
 main chassis, which you see here are
 fast ethernet 0.0 and fast ethernet

0:09:52.260000 --> 0:09:56.080000
 0.1. Those are routed interfaces.

0:09:56.080000 --> 0:09:58.660000
 Those do not belong to
 the switching module.

0:09:58.660000 --> 0:10:01.880000
 So you have to look under, and you can
 see here, which ones are included

0:10:01.880000 --> 0:10:03.420000
 under these switching modules.

0:10:03.420000 --> 0:10:05.900000
 If you see that, let's
 bring that up again.

0:10:05.900000 --> 0:10:10.360000
 You can see that slot 1 has the network
 module with a 16 port ether switch.

0:10:10.360000 --> 0:10:17.260000
 So in this particular case, ports 1
 0 up to 1 15 will be my switching

0:10:17.260000 --> 0:10:20.120000
 interfaces. That's where
 I will find those.

0:10:20.120000 --> 0:10:23.740000
 So don't try to configure your switch
 port commands on the first couple

0:10:23.740000 --> 0:10:27.840000
 of interfaces because those fast ethernet
 interfaces are router interfaces,

0:10:27.840000 --> 0:10:30.120000
 not switching interfaces.

0:10:30.120000 --> 0:10:34.340000
 Now this one, if I right click, I
 don't want to select configure.

0:10:34.340000 --> 0:10:38.180000
 This is not like the built-in switch
 node that we saw before.

0:10:38.180000 --> 0:10:40.820000
 I'm not going to configure
 this thing via a GUI.

0:10:40.820000 --> 0:10:43.880000
 I'm going to configure it via
 the actual command line.

0:10:43.880000 --> 0:10:47.300000
 So let's go ahead and start it up first,
 because I won't even get the

0:10:47.300000 --> 0:10:49.180000
 command line if I don't start it.

0:10:49.180000 --> 0:10:58.140000
 There we go. And let's go ahead and
 right click and select console.

0:10:58.140000 --> 0:10:59.840000
 And here we are.

0:10:59.840000 --> 0:11:03.800000
 Let's wait for it to
 boot up a little bit.

0:11:03.800000 --> 0:11:10.380000
 Okay. Now, before I configure it, I
 can go ahead and add my connections

0:11:10.380000 --> 0:11:13.000000
 at least using the link tool.

0:11:13.000000 --> 0:11:14.280000
 So I'll click on that.

0:11:14.280000 --> 0:11:18.280000
 So here I'll select the very first
 switching port, which is 1 slash 0.

0:11:18.280000 --> 0:11:20.980000
 I'll connect that to PC 1.

0:11:20.980000 --> 0:11:24.900000
 And I'll keep doing it
 with the other ones.

0:11:24.900000 --> 0:11:36.760000
 And when I'm done here, I will move
 the port designators around a little

0:11:36.760000 --> 0:11:39.780000
 bit so they are actually clear.

0:11:39.780000 --> 0:11:41.820000
 All right. So that's that.

0:11:41.820000 --> 0:11:52.060000
 Let's go ahead and move this guy so
 that everything lines up nicely.

0:11:52.060000 --> 0:11:57.300000
 Okay. Now I can see my interface designations
 a little bit more clearly

0:11:57.300000 --> 0:12:01.380000
 at this point. Okay.

0:12:01.380000 --> 0:12:04.460000
 So in the last video, in order to create
 our VLANs and create our trunks

0:12:04.460000 --> 0:12:08.100000
 and assign it to the ports,
 it was all based on the GUI.

0:12:08.100000 --> 0:12:09.580000
 Well, now I've actually
 got a router.

0:12:09.580000 --> 0:12:12.080000
 So I have to go in there
 and configure that.

0:12:12.080000 --> 0:12:16.300000
 So let's go ahead and start with
 Fast Ethan at 1 0 and 1 1.

0:12:16.300000 --> 0:12:21.040000
 So because this is a router, I can actually
 use the interface range command,

0:12:21.040000 --> 0:12:29.760000
 interface range, fast ethernet 1 slash
 0 through 1 slash 1, switch port,

0:12:29.760000 --> 0:12:40.060000
 switch port mode, access, switch
 port, access VLAN 1, no shut.

0:12:40.060000 --> 0:12:47.700000
 Okay. Now let's go back to 1 2 and 1
 3 and let's put those into VLAN 2.

0:12:47.700000 --> 0:13:02.940000
 Switch port, switch port mode access,
 switch port access VLAN 2.

0:13:02.940000 --> 0:13:06.500000
 And notice it created VLAN 2 just like
 you would see in a real switch.

0:13:06.500000 --> 0:13:11.560000
 No shut exit. Now if I want to create
 a VLAN on this thing, some of the

0:13:11.560000 --> 0:13:15.920000
 earlier versions of GNS3 and the earlier
 versions of software said that

0:13:15.920000 --> 0:13:19.720000
 in order to create a VLAN, you had
 to go into VLAN database mode.

0:13:19.720000 --> 0:13:23.760000
 And then from there, type in
 your VLAN or whatever it was.

0:13:23.760000 --> 0:13:25.820000
 But in reality, you don't
 have to do that anymore.

0:13:25.820000 --> 0:13:28.840000
 Here from the global configuration
 mode, you can still create a VLAN.

0:13:28.840000 --> 0:13:37.280000
 It works. Now the last step, I want
 to create my 802.1Q trunk right here

0:13:37.280000 --> 0:13:40.020000
 on fast ethernet 1 slash 4.

0:13:40.020000 --> 0:13:51.320000
 So notice when I do switch port mode,
 if this was a real switch, you'd

0:13:51.320000 --> 0:13:53.960000
 have access to switch
 port mode dynamic.

0:13:53.960000 --> 0:13:55.680000
 But that's not in right here.

0:13:55.680000 --> 0:13:57.300000
 So I can't select that.

0:13:57.300000 --> 0:13:59.300000
 So switch port mode trunk.

0:13:59.300000 --> 0:14:03.080000
 Also notice that with just a regular
 switch port command, one thing that's

0:14:03.080000 --> 0:14:06.180000
 missing is switch port
 port security.

0:14:06.180000 --> 0:14:09.820000
 The port security option is not
 available here as I mentioned.

0:14:09.820000 --> 0:14:18.180000
 No shut exit. And before I leave here,
 you do have a variety of spanning

0:14:18.180000 --> 0:14:24.180000
 tree commands available to you for
 practicing spanning tree and moving

0:14:24.180000 --> 0:14:27.440000
 around your root bridge and practicing
 purvey land spanning tree plus

0:14:27.440000 --> 0:14:29.600000
 and all that good stuff.

0:14:29.600000 --> 0:14:34.220000
 Now one other thing that's
 sort of different in here.

0:14:34.220000 --> 0:14:41.660000
 If you were in a real switch and you wanted
 to see what VLANs were available,

0:14:41.660000 --> 0:14:43.580000
 you would just simply
 type show VLAN.

0:14:43.580000 --> 0:14:45.100000
 Well, that's not the
 correct command.

0:14:45.100000 --> 0:14:47.840000
 And actually it tells you up at the
 very beginning if I can go through

0:14:47.840000 --> 0:14:53.160000
 there when it first came up right here,
 it says to view existing VLANs,

0:14:53.160000 --> 0:14:56.020000
 use the command show
 VLAN dash switch.

0:14:56.020000 --> 0:15:01.900000
 Switch, brief. Show VLAN
 dash switch, brief.

0:15:01.900000 --> 0:15:03.780000
 And that's how I can see my VLANs.


0:15:03.780000 --> 0:15:07.920000
 And the output is pretty much identical
 to the output you would see on

0:15:07.920000 --> 0:15:11.520000
 a regular physical switch.

0:15:11.520000 --> 0:15:19.840000
 Okay, so nothing's showing up under show
 interface trunk, which is a little

0:15:19.840000 --> 0:15:25.960000
 bit suspicious. So
 let's take a look.

0:15:25.960000 --> 0:15:29.040000
 Switch trunking, it's possible it's
 not coming up because the other end

0:15:29.040000 --> 0:15:31.400000
 of the line is currently down.

0:15:31.400000 --> 0:15:35.640000
 Router one right now is in a shutdown state,
 so that might be why FastEthernet1

0:15:35.640000 --> 0:15:37.120000
 slash four is not coming up.

0:15:37.120000 --> 0:15:40.080000
 So let's just bring everything else
 up, give it just a couple of seconds

0:15:40.080000 --> 0:15:44.160000
 in the background for router
 one to finish loading.

0:15:44.160000 --> 0:15:53.840000
 Show run interface FastEthernet1
 slash four.

0:15:53.840000 --> 0:15:57.520000
 Okay, switch port mode trunk
 duplex full speed 100.

0:15:57.520000 --> 0:15:59.420000
 That looks good, it
 is not shut down.

0:15:59.420000 --> 0:16:04.260000
 Show interface, FastEthernet1
 slash four.

0:16:04.260000 --> 0:16:06.620000
 So what about the physical
 layer properties?

0:16:06.620000 --> 0:16:08.620000
 Ah, okay, so here
 we have a problem.

0:16:08.620000 --> 0:16:12.740000
 FastEthernet1 slash four is up, but the
 line protocol is down, most likely

0:16:12.740000 --> 0:16:17.360000
 because something is not configured
 correctly on the router's side.

0:16:17.360000 --> 0:16:21.340000
 So let's just go back to the router
 here and get that working.

0:16:21.340000 --> 0:16:25.540000
 So here's my router.

0:16:25.540000 --> 0:16:32.300000
 Show run interface FastEthernet, actually
 I'll just do show run and we'll

0:16:32.300000 --> 0:16:40.300000
 begin at interface FastEthernet0
 slash one.

0:16:40.300000 --> 0:16:47.000000
 All right, speed is
 100 full duplex.

0:16:47.000000 --> 0:16:49.940000
 Looks like that should be okay.

0:16:49.940000 --> 0:16:52.440000
 And our subinterfaces are
 correctly configured.

0:16:52.440000 --> 0:16:57.660000
 Let's just take a look at the actual
 status of that interface.

0:16:57.660000 --> 0:17:01.360000
 Okay, it says it's up,
 line protocol is up.

0:17:01.360000 --> 0:17:05.620000
 Now these Ether switch modules do support
 the Cisco Discovery protocol,

0:17:05.620000 --> 0:17:12.660000
 so show CDP Okay, so we do have some
 problem here because router one is

0:17:12.660000 --> 0:17:16.460000
 not seeing the Ether
 switch module.

0:17:16.460000 --> 0:17:18.340000
 Let's just double
 check everything.

0:17:18.340000 --> 0:17:21.180000
 So once again, start with the
 topology summary window.

0:17:21.180000 --> 0:17:22.300000
 Is everything green?

0:17:22.300000 --> 0:17:23.720000
 Do we see any red lights?

0:17:23.720000 --> 0:17:26.420000
 Nope, everything's green,
 everything says it's on.

0:17:26.420000 --> 0:17:28.680000
 Okay, so I can get out of there.

0:17:28.680000 --> 0:17:32.360000
 Verify that my interfaces
 are correct.

0:17:32.360000 --> 0:17:37.060000
 So if I just hover over the switch,
 the Ether switch module and take a

0:17:37.060000 --> 0:17:40.780000
 look at the interfaces,
 let's see here.

0:17:40.780000 --> 0:17:46.600000
 So it looks like I scroll
 over that again.

0:17:46.600000 --> 0:17:52.340000
 Okay, so FastEthernet1 slash four, we
 can see right down there is connected

0:17:52.340000 --> 0:17:56.180000
 to router one on port FastEthernet0
 slash one.

0:17:56.180000 --> 0:17:58.740000
 So that is correct.

0:17:58.740000 --> 0:18:03.620000
 All right, let's save my project
 before I go any further.

0:18:03.620000 --> 0:18:08.100000
 Sometimes what I've seen is you have
 to play around with the speed and

0:18:08.100000 --> 0:18:12.560000
 the duplex of the interfaces to get
 everything lined up correctly.

0:18:12.560000 --> 0:18:16.600000
 So even though we saw, let's
 go ahead and do this again.

0:18:16.600000 --> 0:18:19.580000
 So we saw on router one.

0:18:19.580000 --> 0:18:26.520000
 Let's do that again.

0:18:26.520000 --> 0:18:33.600000
 Router one, we see that he is full duplex
 100 megabits per second, which

0:18:33.600000 --> 0:18:37.680000
 I believe is the exact same
 thing as the Ether switch.

0:18:37.680000 --> 0:18:42.620000
 Ah, auto duplex auto speed.

0:18:42.620000 --> 0:18:46.140000
 Okay, so we're having a mismatch here
 because on one side it's hard coded

0:18:46.140000 --> 0:18:48.460000
 for full duplex and speed.

0:18:48.460000 --> 0:18:51.920000
 On this side it is using
 auto negotiation.

0:18:51.920000 --> 0:18:53.920000
 So let's just change that.

0:18:53.920000 --> 0:18:57.100000
 Shut the interface down.

0:18:57.100000 --> 0:19:00.240000
 Change the speed to 100.

0:19:00.240000 --> 0:19:03.920000
 Change the duplex to full.

0:19:03.920000 --> 0:19:08.780000
 No shut. And hopefully that
 will fix our problem.

0:19:08.780000 --> 0:19:09.320000
 Ah, there we go.

0:19:09.320000 --> 0:19:11.140000
 That looks good.

0:19:11.140000 --> 0:19:13.640000
 Has become .1Q trunk.

0:19:13.640000 --> 0:19:15.620000
 Show interface trunk.

0:19:15.620000 --> 0:19:19.740000
 And now it confirms it that our interface
 is actually in trunking state.

0:19:19.740000 --> 0:19:23.620000
 So that concludes this particular
 video on the Ether switch module.

0:19:23.620000 --> 0:19:25.760000
 As you can see to recap
 what we talked about.

0:19:25.760000 --> 0:19:30.940000
 Number one, you have to select an iOS
 image for router that supports network

0:19:30.940000 --> 0:19:34.360000
 modules. And I showed you on the GNS3
 website how to get to that page

0:19:34.360000 --> 0:19:37.080000
 that specifically talks about
 the routers that support that.

0:19:37.080000 --> 0:19:39.880000
 So get a hold of the
 correct iOS image.

0:19:39.880000 --> 0:19:44.680000
 Number two, import that iOS image into GNS3
 and when you get to the appropriate

0:19:44.680000 --> 0:19:50.600000
 screen that was required.

0:19:50.600000 --> 0:19:56.520000
 Number three, within GNS3 itself, once
 that router is there, you can once

0:19:56.520000 --> 0:20:00.300000
 that switch is there, you can now go
 to the switching section and you'll

0:20:00.300000 --> 0:20:02.400000
 see it available as an
 Ether switch router.

0:20:02.400000 --> 0:20:04.820000
 Just drag and drop that
 into your topology.

0:20:04.820000 --> 0:20:08.080000
 And then number four, just go into the
 console that just like you go into

0:20:08.080000 --> 0:20:11.720000
 the console of any other router in your
 device and start configuring the

0:20:11.720000 --> 0:20:16.400000
 appropriate interfaces in the network
 module as switch ports and configure

0:20:16.400000 --> 0:20:19.480000
 your spanning tree and everything
 else that you need to do.

0:20:19.480000 --> 0:20:24.140000
 So that concludes this particular video
 on how to use switching in GNS3.

