WEBVTT

0:00:08.120000 --> 0:00:12.900000
 In the last video I introduced you
 to the concept of VLAN trunking.

0:00:12.900000 --> 0:00:18.000000
 We took a look at the VLAN tags, the
 .1Q tags in our sniffer trace.

0:00:18.000000 --> 0:00:21.140000
 And initially the way we configured our
 trunk was using the command switch

0:00:21.140000 --> 0:00:26.580000
 port mode trunk, changing it from
 an access mode to a trunking mode.

0:00:26.580000 --> 0:00:30.040000
 Now when you use switch port mode trunk,
 what you're telling the interface

0:00:30.040000 --> 0:00:33.940000
 essentially is, I don't care what you're
 connected to on the other end

0:00:33.940000 --> 0:00:37.460000
 of the cable, you
 will do trunking.

0:00:37.460000 --> 0:00:42.100000
 So theoretically if you messed up, you
 might accidentally configure that

0:00:42.100000 --> 0:00:46.840000
 command on a port leading to a host
 like a laptop, and now you have a

0:00:46.840000 --> 0:00:51.920000
 problem. Because that switch would be
 sending frames down to that laptop,

0:00:51.920000 --> 0:00:56.720000
 some of those frames having tags, and
 the laptops don't understand 802

0:00:56.720000 --> 0:00:58.940000
.1Q tags, they don't know
 what to do with it.

0:00:58.940000 --> 0:01:01.380000
 So your ethernet nit card on your laptop
 would be getting all sorts of

0:01:01.380000 --> 0:01:05.200000
 frames, they'd have to be throwing away
 because it didn't know what trunking

0:01:05.200000 --> 0:01:09.480000
 was. But when you type switch port
 mode trunk on the switch interface,

0:01:09.480000 --> 0:01:10.800000
 it has no choice.

0:01:10.800000 --> 0:01:13.800000
 It is doing VLAN trunking.

0:01:13.800000 --> 0:01:18.900000
 So another issue or potential problem
 with that from a more practical

0:01:18.900000 --> 0:01:24.360000
 standpoint, okay, is we talked earlier,
 I don't remember how many videos

0:01:24.360000 --> 0:01:29.440000
 ago, but I mentioned how interfaces, I
 think this is when I first introduced

0:01:29.440000 --> 0:01:33.200000
 the concept of switches and bridges
 and how they each port is its own

0:01:33.200000 --> 0:01:35.100000
 separate collision domain.

0:01:35.100000 --> 0:01:38.560000
 And I mentioned that the way that was
 possible was that switches and bridges

0:01:38.560000 --> 0:01:43.380000
 had memory. So that if two frames come
 at the same time on one switch,

0:01:43.380000 --> 0:01:46.780000
 they're stored in separate sections
 of memory, so they don't run into

0:01:46.780000 --> 0:01:51.340000
 each other. And that's what
 I've drawn right here.

0:01:51.340000 --> 0:01:57.640000
 So this is one cable and let's just say
 this is, I don't know, fast ethernet

0:01:57.640000 --> 0:02:02.280000
 0 slash 2 on one side, and we'll just
 keep it the same on the other side

0:02:02.280000 --> 0:02:04.740000
 just to make it easy.

0:02:04.740000 --> 0:02:10.740000
 And so on switch 1, this port, fast ethernet
 0 slash 2, has some transmit

0:02:10.740000 --> 0:02:15.020000
 buffer. In other words, if a frame
 comes in somewhere else and it has

0:02:15.020000 --> 0:02:19.060000
 to go out fast ethernet 0 2, it'll
 go into the transmit buffer first,

0:02:19.060000 --> 0:02:23.420000
 wait for like a picosecond, really,
 really fast, and then go out on the

0:02:23.420000 --> 0:02:28.300000
 wire. And the receive buffer
 is just the opposite.

0:02:28.300000 --> 0:02:32.820000
 If a frame comes in, it goes into the
 receive buffer, then gets looked

0:02:32.820000 --> 0:02:35.220000
 up and switched out.

0:02:35.220000 --> 0:02:39.160000
 So that's how these, this is memory,
 right, computer memory, and that's

0:02:39.160000 --> 0:02:41.340000
 what this is used for.

0:02:41.340000 --> 0:02:49.120000
 Well, let's say that on both sides of
 this link, I statically configured

0:02:49.120000 --> 0:02:54.160000
 these two interfaces to be trunks.


0:02:54.160000 --> 0:03:03.760000
 So I did config T, interface, fast ethernet
 0 slash 2, switch port mode

0:03:03.760000 --> 0:03:08.760000
 trunk. Okay, chugging along, it's just
 fine, it's operating as a trunk.

0:03:08.760000 --> 0:03:13.260000
 But let's say, and this doesn't happen
 a lot, thank goodness, but every

0:03:13.260000 --> 0:03:16.600000
 once in a while, memory
 gets corrupted.

0:03:16.600000 --> 0:03:19.300000
 You know, maybe there was a huge lightning
 storm and there was some power

0:03:19.300000 --> 0:03:23.240000
 surges or, you know, whatever happened,
 but some memory gets corrupted.

0:03:23.240000 --> 0:03:30.240000
 So let's say that the receive buffer
 on switch 2 becomes bad.

0:03:30.240000 --> 0:03:35.240000
 And what I mean by becomes bad is either
 as electrical energy comes in,

0:03:35.240000 --> 0:03:39.960000
 it can no longer store the ones and
 zeros in here, or as it's trying to

0:03:39.960000 --> 0:03:42.780000
 store the ones and zeros, it's corrupting
 them in some way and they're

0:03:42.780000 --> 0:03:43.800000
 getting all jumbled.

0:03:43.800000 --> 0:03:47.920000
 So basically, stuff that's coming in
 off the wire going in this direction

0:03:47.920000 --> 0:03:54.400000
 is useless, because it's just dying as
 it comes right here to the receive

0:03:54.400000 --> 0:03:58.360000
 buffer. Well, switch
 1 doesn't know that.

0:03:58.360000 --> 0:03:59.700000
 He has no idea that's a problem.

0:03:59.700000 --> 0:04:04.560000
 So as far as switch 1's concerned, he's
 happily chugging away, receiving

0:04:04.560000 --> 0:04:08.540000
 frames, and then putting them in the
 transmit buffer and then sending

0:04:08.540000 --> 0:04:12.320000
 them across here, and then they're just
 dying on switch number 2, because

0:04:12.320000 --> 0:04:16.000000
 he's got no place to store them,
 or they're being corrupted.

0:04:16.000000 --> 0:04:22.060000
 So it might be a better idea if you
 said, well, and let's say to make

0:04:22.060000 --> 0:04:29.560000
 things even more practical as an example,
 let's say that there were for

0:04:29.560000 --> 0:04:33.520000
 redundancy's sake, two cables.

0:04:33.520000 --> 0:04:37.840000
 You said, hey, you know what, if one
 trunk fails, I want to have another

0:04:37.840000 --> 0:04:39.540000
 trunk pick up the slack.

0:04:39.540000 --> 0:04:43.560000
 So I'm going to configure
 this as a trunk as well.

0:04:43.560000 --> 0:04:50.220000
 Now, when you learn about spanning tree
 at the ICND 2 level, you'll learn

0:04:50.220000 --> 0:04:51.940000
 that spanning tree
 doesn't like this.

0:04:51.940000 --> 0:04:55.560000
 When spanning tree sees two redundant
 connections between switches, it

0:04:55.560000 --> 0:05:00.000000
 says, hmm, there's a problem here,
 because if a broadcast comes in on

0:05:00.000000 --> 0:05:04.020000
 switch number 1, it can end up just
 circling around these two interfaces

0:05:04.020000 --> 0:05:07.700000
 forever. Circling and circling and circling,
 and so spanning tree says,

0:05:07.700000 --> 0:05:09.600000
 no, we're going to prevent that.

0:05:09.600000 --> 0:05:12.400000
 We're basically going to take
 down one of these ports.

0:05:12.400000 --> 0:05:13.440000
 It doesn't really do that.

0:05:13.440000 --> 0:05:16.000000
 It's called putting it in blocking state,
 but it says, I'm going to block

0:05:16.000000 --> 0:05:20.640000
 this port. So on this link up here,
 I'm not going to allow any data to

0:05:20.640000 --> 0:05:21.760000
 go back and forth.

0:05:21.760000 --> 0:05:24.500000
 We're just going to put it
 on this link down here.

0:05:24.500000 --> 0:05:30.040000
 So the idea is, if this bottom link
 fails, if I actually yanked out the

0:05:30.040000 --> 0:05:34.800000
 cable or it shut it down, then spanning
 tree would say, okay, I'm not

0:05:34.800000 --> 0:05:37.360000
 going to unblock this top link.

0:05:37.360000 --> 0:05:39.560000
 Now traffic can go across
 this top link.

0:05:39.560000 --> 0:05:42.300000
 So I'm giving you sort of a preview
 of spanning tree that you'll learn

0:05:42.300000 --> 0:05:44.400000
 at the ICND 2 level.

0:05:44.400000 --> 0:05:46.520000
 But now we have a problem here.

0:05:46.520000 --> 0:05:48.280000
 I'm going to put this up here.

0:05:48.280000 --> 0:05:56.180000
 Blocked by spanning tree.

0:05:56.180000 --> 0:06:01.020000
 So here we have an issue, because switch
 1 doesn't know that the bottom

0:06:01.020000 --> 0:06:05.360000
 link is bad. From his perspective,
 this link is up up.

0:06:05.360000 --> 0:06:07.740000
 There's no issues with it.

0:06:07.740000 --> 0:06:11.420000
 So he's still taking all the traffic,
 and because spanning tree has told

0:06:11.420000 --> 0:06:14.360000
 him the bottom link is what you should
 be using, that's forwarding, forward

0:06:14.360000 --> 0:06:18.500000
 your traffic that way, he's still putting
 it on that trunk, as dying as

0:06:18.500000 --> 0:06:20.400000
 it gets to switch number 2.

0:06:20.400000 --> 0:06:23.720000
 He has no idea that
 this trunk is bad.

0:06:23.720000 --> 0:06:28.240000
 So what we could do instead is do
 what's called dynamic trunking.

0:06:28.240000 --> 0:06:32.700000
 With dynamic trunking, these two switches
 have to initially exchange some

0:06:32.700000 --> 0:06:37.460000
 special messages across this bottom
 link and the top link, if I want the

0:06:37.460000 --> 0:06:42.460000
 top link to be trunking as well, special
 Cisco proprietary messages that

0:06:42.460000 --> 0:06:44.540000
 say, I'd like to trunk with you.

0:06:44.540000 --> 0:06:49.180000
 Is that okay? Now if that message exchange
 works, then we can bring up

0:06:49.180000 --> 0:06:50.780000
 the trunk, but guess what?

0:06:50.780000 --> 0:06:55.060000
 As long as that trunk is up, those special
 messages are still exchanged.

0:06:55.060000 --> 0:06:56.000000
 Hey, you're still good?

0:06:56.000000 --> 0:06:57.060000
 We're still good for trunking?

0:06:57.060000 --> 0:06:58.680000
 Yeah, yeah, we're all right.

0:06:58.680000 --> 0:07:02.320000
 So in this particular
 case, that would fail.

0:07:02.320000 --> 0:07:08.420000
 If we use dynamic trunking here, the
 special messages that switch 1 was

0:07:08.420000 --> 0:07:10.080000
 sending to the top link saying,
 hey, I'd like to trunk with you.

0:07:10.080000 --> 0:07:14.140000
 Is that okay? All of a sudden, switch
 2 would not be getting those messages

0:07:14.140000 --> 0:07:16.540000
 anymore. Why is that?

0:07:16.540000 --> 0:07:20.280000
 Well, because they would be coming
 in, but they'd have to be stored in

0:07:20.280000 --> 0:07:21.240000
 the received buffer.

0:07:21.240000 --> 0:07:25.000000
 Anything that comes in on Fast Ethan at
 0-2 has to be stored in the received

0:07:25.000000 --> 0:07:28.680000
 buffer, but our received
 buffer is bad.

0:07:28.680000 --> 0:07:33.680000
 So switch 2 would say, we initially agreed
 on trunking and you're supposed

0:07:33.680000 --> 0:07:37.220000
 to be sending me these messages periodically
 and I'm not hearing from

0:07:37.220000 --> 0:07:40.220000
 you. It's not that switch
 1's not sending them.

0:07:40.220000 --> 0:07:43.620000
 Switch 1 is sending them, but when switch
 2 receives them, they're getting

0:07:43.620000 --> 0:07:48.640000
 all messed up. So from switch 2's perspective,
 he's saying something's

0:07:48.640000 --> 0:07:54.900000
 wrong here. And when that exchange of
 that messaging protocol fails, then

0:07:54.900000 --> 0:07:58.640000
 switch 2 says, okay, I'm no longer
 going to trunk with you.

0:07:58.640000 --> 0:08:02.920000
 Switch 2 would actually send a message
 back saying, trunking failed, no

0:08:02.920000 --> 0:08:08.380000
 longer trunking, and this would
 revert back to an access port.

0:08:08.380000 --> 0:08:10.420000
 That's what dynamic
 trunking can do.

0:08:10.420000 --> 0:08:14.720000
 It exchanges these special Cisco proprietary
 messages to bring up the

0:08:14.720000 --> 0:08:18.620000
 trunk, and then as the trunk is up,
 these messages have to periodically

0:08:18.620000 --> 0:08:22.020000
 still be exchanged as
 keep-alives as hellos.

0:08:22.020000 --> 0:08:26.660000
 And if something happens where that exchange
 stops, now the trunk reverts

0:08:26.660000 --> 0:08:29.080000
 back to access mode.

0:08:29.080000 --> 0:08:32.080000
 Now you might be wondering, well, wait
 a second, if it reverts back to

0:08:32.080000 --> 0:08:37.100000
 access mode, that means it was carrying
 all the VLANs that were allowed,

0:08:37.100000 --> 0:08:40.760000
 that were configured, and now
 it's carrying only one VLAN.

0:08:40.760000 --> 0:08:43.520000
 Which VLAN is it going to carry?

0:08:43.520000 --> 0:08:48.380000
 That all depends on what you've configured
 here in your switch port access

0:08:48.380000 --> 0:09:00.340000
 VLAN command. So if I had switch port
 access VLAN 4, while it's operating

0:09:00.340000 --> 0:09:04.740000
 as a trunk, this command would do nothing,
 because it's not an access

0:09:04.740000 --> 0:09:09.220000
 port. But if the trunk failed, and it
 had to revert back to being an access

0:09:09.220000 --> 0:09:13.840000
 port, now it would be an
 access port in VLAN 4.

0:09:13.840000 --> 0:09:16.720000
 So how do we get this dynamic
 trunking going on?

0:09:16.720000 --> 0:09:20.080000
 It's not the switch port mode trunk,
 because switch port mode trunk forces

0:09:20.080000 --> 0:09:21.440000
 it to be a trunk.

0:09:21.440000 --> 0:09:25.360000
 And that's what we're going
 to talk about right here.

0:09:25.360000 --> 0:09:30.520000
 So Cisco has a proprietary language
 that's going back and forth between

0:09:30.520000 --> 0:09:34.240000
 the switches is called the
 dynamic trunking protocol.

0:09:34.240000 --> 0:09:37.780000
 I wish I could capture it in a sniffer
 trace, but unfortunately the switch

0:09:37.780000 --> 0:09:41.700000
 is available to me in GNS3.

0:09:41.700000 --> 0:09:43.480000
 So I can't do that.

0:09:43.480000 --> 0:09:44.840000
 But you could Google it.

0:09:44.840000 --> 0:09:50.760000
 I would recommend Google Cisco DTP sniffer
 capture, and you could probably

0:09:50.760000 --> 0:09:53.240000
 find a picture of what
 that looks like.

0:09:53.240000 --> 0:09:56.660000
 But the dynamic trunking protocol is
 that special language that says,

0:09:56.660000 --> 0:09:58.060000
 okay, can you trunk with me?

0:09:58.060000 --> 0:10:02.440000
 Are we good? And then if the trunk comes
 up, they still exchange DTP back

0:10:02.440000 --> 0:10:06.100000
 and forth to maintain the
 trunk to keep it up.

0:10:06.100000 --> 0:10:09.400000
 Now clearly, Cisco proprietary.

0:10:09.400000 --> 0:10:14.900000
 So if I have a Cisco switch connected
 to a non-Cisco switch, you don't

0:10:14.900000 --> 0:10:19.500000
 have a choice. Then you'll have to do
 switch port mode trunk on the Cisco

0:10:19.500000 --> 0:10:21.380000
 switch and force it.

0:10:21.380000 --> 0:10:28.580000
 Another key thing, DTP only understood
 by Cisco switches, not understood

0:10:28.580000 --> 0:10:34.080000
 by routers. Remember in the last video,
 when I introduced the concept

0:10:34.080000 --> 0:10:39.100000
 of VLAN trunking, I still
 have the GNS3 up here.

0:10:39.100000 --> 0:10:44.820000
 The way I did it was I had also trunking
 going from the switch to the

0:10:44.820000 --> 0:10:50.020000
 router. This cannot be a dynamic trunk
 because the router does not understand

0:10:50.020000 --> 0:10:52.340000
 the dynamic trunking protocol.

0:10:52.340000 --> 0:10:56.520000
 So on this interface, on the switch,
 I would have to do switch port mode

0:10:56.520000 --> 0:10:59.720000
 trunk, even though I'm connecting
 to a Cisco router.

0:10:59.720000 --> 0:11:01.980000
 Because the Cisco router
 doesn't understand DTP.

0:11:01.980000 --> 0:11:07.080000
 But from one Cisco switch to another
 Cisco switch, I could use DTP.

0:11:07.080000 --> 0:11:09.660000
 Now it's optional, you
 don't have to use it.

0:11:09.660000 --> 0:11:13.440000
 But in this whiteboard right here, this
 is one reason why you might want

0:11:13.440000 --> 0:11:19.140000
 to. If you think there's a possibility
 where the interface might still

0:11:19.140000 --> 0:11:23.440000
 be up, but it might not actually
 be reachable on the other side.

0:11:23.440000 --> 0:11:27.280000
 Something is preventing communications
 by directional communication back

0:11:27.280000 --> 0:11:30.960000
 and forth, but the interface
 is still physically up.

0:11:30.960000 --> 0:11:35.600000
 That would be a good use case where
 dynamic trunking could detect that.

0:11:35.600000 --> 0:11:40.420000
 So when you're configuring trunking,
 you have three options.

0:11:40.420000 --> 0:11:45.820000
 So option number one is just
 switch port mode trunk.

0:11:45.820000 --> 0:11:50.580000
 And that's what they're showing you
 here as using the keyword of on.

0:11:50.580000 --> 0:11:53.160000
 There really is no keyword of on.

0:11:53.160000 --> 0:11:57.760000
 It's just switch port
 mode trunk is on.

0:11:57.760000 --> 0:11:59.300000
 So I'll just write that here.

0:11:59.300000 --> 0:12:05.080000
 Switch port mode trunk.

0:12:05.080000 --> 0:12:13.580000
 Okay, now auto and desirable, these
 here to use these, you have to go

0:12:13.580000 --> 0:12:15.520000
 into a different mode.

0:12:15.520000 --> 0:12:22.880000
 And to use auto or desirable, you use
 switch port mode dynamic because

0:12:22.880000 --> 0:12:25.560000
 we're doing dynamic trunking.

0:12:25.560000 --> 0:12:28.880000
 And then you get to choose
 desirable or auto.

0:12:28.880000 --> 0:12:35.300000
 Now, almost a guarantee that whether
 you take the ICND one, the ICND two,

0:12:35.300000 --> 0:12:38.600000
 you know, whatever you take, I can almost
 promise you that you're going

0:12:38.600000 --> 0:12:46.240000
 to get a question testing your understanding
 of, you know, versus dynamic

0:12:46.240000 --> 0:12:48.860000
 auto. So let me tell you.

0:12:48.860000 --> 0:12:53.220000
 So when you say switch port mode dynamic
 desirable, as soon as you hit

0:12:53.220000 --> 0:12:57.920000
 enter, if that interface is up and connected,
 it starts sending out DTP

0:12:57.920000 --> 0:13:00.160000
 messages saying, Hey, I'd
 like to trunk with you.

0:13:00.160000 --> 0:13:00.800000
 Can you do that?

0:13:00.800000 --> 0:13:02.780000
 Ha ha ha ha. You want
 trunk with me?

0:13:02.780000 --> 0:13:04.240000
 I would desire that.

0:13:04.240000 --> 0:13:05.440000
 That's desirable.

0:13:05.440000 --> 0:13:11.180000
 So if you do switch port mode dynamic
 auto, he's like sitting back with

0:13:11.180000 --> 0:13:15.800000
 his hands full and saying, Okay, you
 can talk to me, but I'm not going

0:13:15.800000 --> 0:13:18.320000
 to talk to you. In other words,
 you've got to initiate.

0:13:18.320000 --> 0:13:20.020000
 I'm just going to sit
 here and listen.

0:13:20.020000 --> 0:13:22.980000
 I'll talk to you if
 you talk to me.

0:13:22.980000 --> 0:13:25.760000
 That's auto. So auto is passive.

0:13:25.760000 --> 0:13:29.220000
 It does not initiate
 the conversation.

0:13:29.220000 --> 0:13:33.320000
 So if we think about it, and by the
 way, when you do switch port mode

0:13:33.320000 --> 0:13:43.560000
 trunk, as we saw in the last video,
 please forgive my bad handwriting

0:13:43.560000 --> 0:13:49.980000
 here. Switch port mode trunk.

0:13:49.980000 --> 0:14:07.320000
 DTP is sent. So even when you do switch
 port mode trunk, the side that's

0:14:07.320000 --> 0:14:11.240000
 configured as switch port mode trunk,
 he's not doing anything dynamically.

0:14:11.240000 --> 0:14:13.840000
 You've just told him
 you will be a trunk.

0:14:13.840000 --> 0:14:19.340000
 You have no choice, but he is sending
 out DTP as a courtesy so that the

0:14:19.340000 --> 0:14:22.260000
 other side could be desirable
 if it wants to.

0:14:22.260000 --> 0:14:26.700000
 So that being the case, we have to think
 about what combinations of keywords

0:14:26.700000 --> 0:14:31.060000
 will work to form a trunk,
 which ones won't.

0:14:31.060000 --> 0:14:35.480000
 Pretty much every combination of these
 keywords will work to bring up

0:14:35.480000 --> 0:14:46.780000
 a trunk other than if I have auto
 on one side and auto on the other.

0:14:46.780000 --> 0:14:51.280000
 If both sides are auto, neither side
 is initiating the conversation.

0:14:51.280000 --> 0:14:54.200000
 They're both waiting for the other
 side to talk and the other side is

0:14:54.200000 --> 0:14:55.520000
 not going to talk.

0:14:55.520000 --> 0:15:00.120000
 So in that particular case, this link
 will remain as an access port in

0:15:00.120000 --> 0:15:02.520000
 whatever VLAN is configured
 to be in.

0:15:02.520000 --> 0:15:03.960000
 It will not do trunking.

0:15:03.960000 --> 0:15:06.980000
 Somebody has to initiate
 the conversation.

0:15:06.980000 --> 0:15:11.340000
 So that could be a desirable or that
 could be switch port mode trunk,

0:15:11.340000 --> 0:15:12.860000
 but one side has to initiate.

0:15:12.860000 --> 0:15:16.820000
 In a lot of Cisco documents, they actually
 recommend that you set both

0:15:16.820000 --> 0:15:19.480000
 sides to desirable.

0:15:19.480000 --> 0:15:26.880000
 That's what they typically suggest
 is you do switch port mode dynamic

0:15:26.880000 --> 0:15:29.300000
 desirable on both sides.

0:15:29.300000 --> 0:15:32.180000
 I'm just showing you here, there's a
 lot of other combinations that would

0:15:32.180000 --> 0:15:36.340000
 work. I could have switch port mode
 trunk, mode auto, switch port mode

0:15:36.340000 --> 0:15:41.040000
 dynamic desirable, dynamic auto, dynamic
 desirable, dynamic desirable.

0:15:41.040000 --> 0:15:45.540000
 As long as someone is initiating the
 exchange, the other dynamic side

0:15:45.540000 --> 0:15:53.100000
 can pick it up and talk.

0:15:53.100000 --> 0:15:56.800000
 And we verify it, and switch
 port no negotiate.

0:15:56.800000 --> 0:16:02.560000
 Really, the only time I can think of
 where this might be something you

0:16:02.560000 --> 0:16:07.600000
 want to do is let's say that you have
 an interface on your switch connected

0:16:07.600000 --> 0:16:11.440000
 to a device that does not
 understand the device.

0:16:11.440000 --> 0:16:15.680000
 And DTP, and you just say to yourself,
 well, there's really no point in

0:16:15.680000 --> 0:16:17.460000
 putting DTP on that wire.

0:16:17.460000 --> 0:16:20.160000
 I mean, it takes up tiny
 little bit of bandwidth.

0:16:20.160000 --> 0:16:22.980000
 I mean, it doesn't go out that frequently,
 but if you say to yourself,

0:16:22.980000 --> 0:16:25.740000
 you know what? I don't even
 want it going out at all.

0:16:25.740000 --> 0:16:27.100000
 There's no point.

0:16:27.100000 --> 0:16:31.260000
 Well, you could say switch port mode
 trunk, force it to trunk, and then

0:16:31.260000 --> 0:16:35.000000
 on top of that, say switch
 port no negotiate.

0:16:35.000000 --> 0:16:37.020000
 That means don't send
 any DTP at all.

0:16:37.020000 --> 0:16:41.420000
 Just turn off DTP processing.

0:16:41.420000 --> 0:16:44.900000
 And verifying it is the exact same way
 that you verify it with the other

0:16:44.900000 --> 0:16:47.140000
 show commands that
 we've looked at.

0:16:47.140000 --> 0:16:53.640000
 So let's just do a quick lab on that
 so you can see what it looks like.

0:16:53.640000 --> 0:17:01.960000
 So for this, I am going
 to log into INE's racks.

0:17:01.960000 --> 0:17:07.460000
 And because I've used our racks so frequently,
 I know what the topology

0:17:07.460000 --> 0:17:11.500000
 looks like, but I'll just draw
 it here real quickly for you.

0:17:11.500000 --> 0:17:21.540000
 I know that switch one is connected
 to switch two via fast ethernet zero

0:17:21.540000 --> 0:17:23.940000
 slash ten on both sides.

0:17:23.940000 --> 0:17:26.740000
 So that's what I'll
 be configuring.

0:17:26.740000 --> 0:17:29.320000
 Now, one other thing you
 should be aware of.

0:17:29.320000 --> 0:17:32.520000
 You might be wondering, well, when it
 comes to mode, so software we talked

0:17:32.520000 --> 0:17:38.020000
 about switch port mode access, switch
 port mode trunk, and switch port

0:17:38.020000 --> 0:17:42.540000
 mode dynamic with either auto
 or desirable as the keywords.

0:17:42.540000 --> 0:17:45.600000
 You might be wondering,
 what's the default mode?

0:17:45.600000 --> 0:17:49.560000
 When I just wipe out the configuration,
 start from scratch, or I take

0:17:49.560000 --> 0:17:54.300000
 a brand new switch and I turn it on, which
 of those modes is it by default?

0:17:54.300000 --> 0:18:00.360000
 Pretty much all Cisco switches by default
 are switch port mode dynamic.

0:18:00.360000 --> 0:18:03.760000
 You might be saying, well, wait
 a second, you can't be done yet.

0:18:03.760000 --> 0:18:07.020000
 It's either dynamic auto
 or dynamic desirable.

0:18:07.020000 --> 0:18:08.240000
 Which one is it?

0:18:08.240000 --> 0:18:10.700000
 That depends on the
 model of switch.

0:18:10.700000 --> 0:18:15.140000
 Some switches are switch port
 mode dynamic auto by default.

0:18:15.140000 --> 0:18:16.420000
 Most of them are.

0:18:16.420000 --> 0:18:22.800000
 But some switches are switch port
 mode dynamic desirable by default.

0:18:22.800000 --> 0:18:26.420000
 And that can sometimes throw people
 for a loop because they say, hey,

0:18:26.420000 --> 0:18:29.960000
 I just connected these switches back
 to back with cables and these trunks

0:18:29.960000 --> 0:18:32.400000
 just came up. I didn't mean
 for that to happen.

0:18:32.400000 --> 0:18:33.640000
 It just happened.

0:18:33.640000 --> 0:18:37.680000
 Well, that's because at least one of them
 was dynamic desirable by default.

0:18:37.680000 --> 0:18:40.940000
 And as soon as you connected the cable,
 it started sending DTP without

0:18:40.940000 --> 0:18:42.380000
 you doing anything.

0:18:42.380000 --> 0:18:45.980000
 Let's see what these ones are.

0:18:45.980000 --> 0:18:51.240000
 I know these are catalyst
 3560 switches.

0:18:51.240000 --> 0:18:56.120000
 So one way you can tell is, first of all,
 let me take a look at the interface

0:18:56.120000 --> 0:18:58.560000
 and see if it has any existing
 configuration on it.

0:18:58.560000 --> 0:18:59.560000
 No, it doesn't. Okay.

0:18:59.560000 --> 0:19:02.480000
 So this interface doesn't
 have any configuration.

0:19:02.480000 --> 0:19:10.800000
 So I can type show interface fast ethernet
 zero slash 10 switch port.

0:19:10.800000 --> 0:19:14.180000
 And there we go.

0:19:14.180000 --> 0:19:16.060000
 Dynamic auto. It's dynamic auto.

0:19:16.060000 --> 0:19:22.640000
 So that's why it will not form
 a trunk until I tell it to.

0:19:22.640000 --> 0:19:27.460000
 Okay. So I'll go into interface
 fast ethernet zero slash 10.

0:19:27.460000 --> 0:19:32.140000
 And I'll say, let's just
 shut it down first.

0:19:32.140000 --> 0:19:38.780000
 I typically recommend that if you're
 changing the physical layer or data

0:19:38.780000 --> 0:19:42.960000
 link layer characteristics of an interface,
 it's a good idea to shut it

0:19:42.960000 --> 0:19:47.540000
 down first, make your layer one or
 layer two changes, and then do a no

0:19:47.540000 --> 0:19:49.080000
 shut down afterwards.

0:19:49.080000 --> 0:19:52.120000
 Sometimes when you try to change those
 types of things while the interface

0:19:52.120000 --> 0:19:55.500000
 is up, weird things can happen.

0:19:55.500000 --> 0:19:57.900000
 So let's just do switch port.

0:19:57.900000 --> 0:20:04.520000
 Switch port mode.

0:20:04.520000 --> 0:20:09.080000
 Dynamic. Desirable.

0:20:09.080000 --> 0:20:17.260000
 While we're at it, switch port trunk
 encapsulation dot one queue.

0:20:17.260000 --> 0:20:23.660000
 Switch port. No shut down.

0:20:23.660000 --> 0:20:28.740000
 Now, before I do no shut down, I don't
 know, because I haven't looked

0:20:28.740000 --> 0:20:32.440000
 yet, what the state is
 of this interface.

0:20:32.440000 --> 0:20:38.540000
 If this interface is ready to go, if
 it is not administratively disabled,

0:20:38.540000 --> 0:20:42.620000
 if it's ready to go, and if it is in
 the default auto state, the default

0:20:42.620000 --> 0:20:47.620000
 state of dynamic auto, the moment I do
 no shut on here, I just configured

0:20:47.620000 --> 0:20:50.420000
 him to be dynamic desirable.

0:20:50.420000 --> 0:20:55.300000
 So the moment I bring him up, he should
 start sending DTP, the dynamic

0:20:55.300000 --> 0:20:57.320000
 trunking protocol.

0:20:57.320000 --> 0:21:02.580000
 And if this other side comes up and
 he's auto, the trunk should come up.

0:21:02.580000 --> 0:21:05.380000
 I shouldn't have to do
 anything on switch two.

0:21:05.380000 --> 0:21:09.000000
 So let's just see
 what happens here.

0:21:09.000000 --> 0:21:12.620000
 Interface change state to down.

0:21:12.620000 --> 0:21:15.920000
 Okay, so that's telling me,
 remember what we said?

0:21:15.920000 --> 0:21:20.320000
 Remember what I said when I said
 show IP interface brief?

0:21:20.320000 --> 0:21:22.900000
 That says our troubleshooting
 step.

0:21:22.900000 --> 0:21:25.880000
 If I have an interface that I know
 is connected to something and it's

0:21:25.880000 --> 0:21:27.760000
 down down, what did I say?

0:21:27.760000 --> 0:21:31.040000
 I said, well, maybe there's
 no cable connected at all.

0:21:31.040000 --> 0:21:34.540000
 Maybe there is a cable, but the other
 end of that cable is not connected

0:21:34.540000 --> 0:21:39.040000
 to anything. Or the other end of that
 cable is connected to something,

0:21:39.040000 --> 0:21:41.840000
 but the other side is
 administratively down.

0:21:41.840000 --> 0:21:43.540000
 Let's take a look.

0:21:43.540000 --> 0:21:48.820000
 Show run interface fast
 ethernet zero slash ten.

0:21:48.820000 --> 0:21:57.680000
 See, it is shutdown.

0:21:57.680000 --> 0:22:01.600000
 Okay, change state
 to up, that's good.

0:22:01.600000 --> 0:22:05.540000
 And if this becomes a trunk, I should
 get some messaging about that, I

0:22:05.540000 --> 0:22:09.920000
 would think. Change state to up.

0:22:09.920000 --> 0:22:13.100000
 So this is the data link layer.

0:22:13.100000 --> 0:22:15.740000
 The line protocol indicates
 layer two.

0:22:15.740000 --> 0:22:18.400000
 This here indicates
 the physical layer.

0:22:18.400000 --> 0:22:22.720000
 So far I haven't gotten any messaging
 about it being a trunk.

0:22:22.720000 --> 0:22:27.380000
 What is the command I can type to see
 if I have any VLAN trunks on this

0:22:27.380000 --> 0:22:34.580000
 switch? That command was
 show interfaces trunk.

0:22:34.580000 --> 0:22:37.800000
 And it is. So I didn't get any syslog
 message, I didn't see any messages

0:22:37.800000 --> 0:22:39.040000
 about it, but here it is.

0:22:39.040000 --> 0:22:41.780000
 It says it's in auto mode.

0:22:41.780000 --> 0:22:44.720000
 N means it dynamically negotiated.


0:22:44.720000 --> 0:22:48.840000
 That's what the N is for
 it, negotiated 802.1q.

0:22:48.840000 --> 0:22:51.260000
 And here it says native
 VLAN is one.

0:22:51.260000 --> 0:22:52.980000
 So this says it's in dynamic auto.


0:22:52.980000 --> 0:22:57.060000
 Let's take a look at switch one, who
 I configured as dynamic desirable.

0:22:57.060000 --> 0:23:02.800000
 Show interfaces trunk.

0:23:02.800000 --> 0:23:05.420000
 See, his mode says desirable.

0:23:05.420000 --> 0:23:13.700000
 And that concludes this section on
 Cisco's dynamic trunking protocol.

