Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:04,179 --> 00:00:07,679
This is a free, complete course for the CCNA.
2
00:00:07,679 --> 00:00:11,989
If you like these videos, please subscribe\n
3
00:00:11,990 --> 00:00:17,079
Also, please like and leave a comment, and\n
4
00:00:20,579 --> 00:00:24,300
In this video we will continue our study of\nspanning tree.
5
00:00:24,300 --> 00:00:29,069
In part 1 we focused on the basic purpose\n
6
00:00:30,809 --> 00:00:36,488
In this video we will look into more detail\n
7
00:00:36,488 --> 00:00:39,799
First let’s see what we’ll cover in this\nvideo.
8
00:00:39,799 --> 00:00:44,049
First of all we will take a look at spanning tree states and
9
00:00:44,049 --> 00:00:49,018
You already know the blocking and forwarding\n
10
00:00:49,018 --> 00:00:53,748
states between those two, and some timers\n
11
00:00:54,749 --> 00:01:00,800
I’ll show you the spanning tree BPDU (bridge protocol data unit,
12
00:01:04,140 --> 00:01:08,950
Then we’ll take a look at some optional\n
13
00:01:08,950 --> 00:01:13,140
tree ‘toolkit’, some additional features\n
14
00:01:13,140 --> 00:01:15,840
tree, we’ll cover some of them briefly.
15
00:01:15,840 --> 00:01:20,469
Finally, we’ll cover spanning tree configurations.
16
00:01:20,469 --> 00:01:25,141
Spanning tree runs by default so you don’t\n
17
00:01:25,141 --> 00:01:29,590
you should know how to change which switch\n
18
00:01:29,590 --> 00:01:32,370
make sure traffic follows the best path.
19
00:01:32,370 --> 00:01:35,980
Also, make sure to stick around to the end\nof today’s quiz.
20
00:01:35,980 --> 00:01:41,460
I will feature one practice question from\n
21
00:01:41,459 --> 00:01:44,719
of practice exams for the CCNA.
22
00:01:44,719 --> 00:01:49,099
Pretty much everyone who uses them agrees\n
23
00:01:49,099 --> 00:01:52,569
and are an essential part of preparing for\nthe CCNA.
24
00:01:52,569 --> 00:01:58,359
They definitely helped me pass all of my CCNA\n
25
00:01:58,359 --> 00:02:05,129
If you want to grab a copy of ExSim, please\n
26
00:02:05,129 --> 00:02:08,669
First let’s take a look at spanning\ntree port states.
27
00:02:08,669 --> 00:02:14,079
You are already familiar with two, BLOCKING\n
28
00:02:16,340 --> 00:02:19,640
BLOCKING and FORWARDING are the two ‘stable’\nstates.
29
00:02:19,639 --> 00:02:25,699
Root and Designated ports remain stable in a Forwarding state, and
30
00:02:28,069 --> 00:02:33,199
Note that they only remain stable as long\n
31
00:02:33,199 --> 00:02:38,750
If a new device is added, an interface is\n
32
00:02:38,750 --> 00:02:41,490
they may have to change states.
33
00:02:41,490 --> 00:02:46,379
But as I said, as long as the network is stable,\n
34
00:02:48,189 --> 00:02:51,990
Now, there are also two transitional states.
35
00:02:51,990 --> 00:02:55,890
Listening and Learning are transitional states\n
36
00:02:55,889 --> 00:03:00,369
is activated, or when a Blocking port must\n
37
00:03:00,370 --> 00:03:02,349
change in the network topology.
38
00:03:02,349 --> 00:03:08,289
Actually, there is one more state you might\n
39
00:03:08,289 --> 00:03:12,620
This simply refers to an interface that is\n
40
00:03:12,620 --> 00:03:16,520
We won’t really talk about the disabled\n
41
00:03:16,520 --> 00:03:19,820
any role in spanning tree, the interface is\nshut down.
42
00:03:19,819 --> 00:03:26,359
Okay, let’s take a look at these states,\n
43
00:03:26,360 --> 00:03:30,120
Non-designated ports are in a Blocking state.
44
00:03:30,129 --> 00:03:34,439
Interfaces in a Blocking state are effectively\n
45
00:03:34,439 --> 00:03:40,699
This is what makes spanning tree work, disabling\n
46
00:03:40,699 --> 00:03:45,030
Interfaces in a Blocking state do not send/receive\n
47
00:03:45,030 --> 00:03:50,479
Any regular traffic that arrives on an interface\n
48
00:03:50,479 --> 00:03:55,799
However, Interfaces in a Blocking state do\nreceive STP BPDUs.
49
00:03:55,800 --> 00:04:01,820
They need to receive and process BPDUs to\n
50
00:04:01,819 --> 00:04:05,590
to transition toward a forwarding state if\nthey need to.
51
00:04:05,590 --> 00:04:12,080
But, interfaces in a Blocking state do NOT\nforward STP BPDUs.
52
00:04:12,080 --> 00:04:17,348
Finally, interfaces in a Blocking state do\n
53
00:04:17,348 --> 00:04:21,569
If regular traffic arrives on the interface\n
54
00:04:25,329 --> 00:04:30,329
After the Blocking state, interfaces with\n
55
00:04:31,759 --> 00:04:38,250
Let me just repeat that only Designated or\n
56
00:04:39,908 --> 00:04:43,870
That’s because Listening is a transitional\n
57
00:04:43,870 --> 00:04:49,149
state, so there’s no need for a Non-designated\n
58
00:04:49,149 --> 00:04:52,679
The Listening state is 15 seconds long by\ndefault.
59
00:04:52,680 --> 00:04:56,228
This is determined by a timer called the ‘Forward\ndelay’ timer.
60
00:04:56,228 --> 00:05:00,438
You’ll soon see that this timer isn’t\n
61
00:05:00,439 --> 00:05:04,689
Anyway, remember that it is 15 seconds by\ndefault.
62
00:05:04,689 --> 00:05:10,740
An interface in the Listening state ONLY forwards/receives
63
00:05:10,740 --> 00:05:14,098
It does NOT send or receive regular traffic.
64
00:05:14,098 --> 00:05:18,519
If a regular unicast frame is received on\n
65
00:05:20,870 --> 00:05:25,439
An interface in the Listening state also does\n
66
00:05:25,439 --> 00:05:26,760
that arrives on the interface.
67
00:05:26,759 --> 00:05:31,490
I said the same thing about the Blocking state,\n
68
00:05:31,490 --> 00:05:36,340
As you know well already, when a frame arrives\n
69
00:05:36,339 --> 00:05:41,179
source MAC address field to ‘learn’ that\n
70
00:05:41,180 --> 00:05:45,620
table with the MAC address, interface, and\nVLAN information.
71
00:05:45,620 --> 00:05:50,800
However, if an interface is in the spanning\n
72
00:05:50,800 --> 00:05:57,619
The traffic is simply dropped, and the MAC\n
73
00:05:57,619 --> 00:06:02,979
After the Listening state, a Designated or\n
74
00:06:02,978 --> 00:06:06,180
The Learning state is 15 seconds long by default.
75
00:06:06,180 --> 00:06:10,689
This is determined by the Forward delay timer,\n
76
00:06:10,689 --> 00:06:15,689
and Learning states, meaning by default it\n
77
00:06:15,689 --> 00:06:19,309
both states and enter a forwarding state.
78
00:06:19,309 --> 00:06:24,629
Same as in the Listening state, an interface\n
79
00:06:27,009 --> 00:06:31,069
Also, it does NOT send or receive regular traffic.
80
00:06:31,069 --> 00:06:35,650
However, here is the difference between the\n
81
00:06:35,649 --> 00:06:40,088
An interface in the Learning state learns\n
82
00:06:41,439 --> 00:06:46,348
So, an interface in the learning state is\n
83
00:06:46,348 --> 00:06:49,498
some of its MAC address table beforehand.
84
00:06:49,499 --> 00:06:53,509
Finally, we have the forwarding state.
85
00:06:53,509 --> 00:06:57,939
Root and Designated ports are in a Forwarding\n
86
00:06:57,939 --> 00:07:01,110
A port in the Forwarding state operate as\nnormal.
87
00:07:03,478 --> 00:07:07,990
A port in the Forwarding state sends and receives\nBPDUs.
88
00:07:07,990 --> 00:07:10,978
It sends and receives normal traffic.
89
00:07:10,978 --> 00:07:15,110
Also it learns MAC addresses from the frames that\n
90
00:07:16,110 --> 00:07:20,119
So, it’s a switchport operating as normal.
91
00:07:20,119 --> 00:07:24,460
For review, here’s a summary of each spanning\ntree port state.
92
00:07:24,459 --> 00:07:29,468
For reference, I’ve also added the Disabled\n
93
00:07:29,468 --> 00:07:34,939
is the spanning tree state of a shutdown,\n
94
00:07:34,939 --> 00:07:39,160
Pause the video if you want to take a look\n
95
00:07:39,160 --> 00:07:43,310
You can also review using the flashcard deck,\n
96
00:07:46,468 --> 00:07:49,610
Now let’s talk about each of the timers\nused in Spanning Tree.
97
00:07:49,610 --> 00:07:54,960
I’ve already mentioned the Hello and Forward\n
98
00:07:57,028 --> 00:08:00,800
First up let’s look more in detail at the\nhello timer.
99
00:08:00,800 --> 00:08:05,990
It determines how often the root bridge sends\n
100
00:08:08,490 --> 00:08:13,900
Other switches in the network do not originate\n
101
00:08:15,278 --> 00:08:18,370
However, there is one thing I didn’t mention\nbefore.
102
00:08:18,370 --> 00:08:22,658
The switches will only forward BPDUs on their\nDESIGNATED PORTs.
103
00:08:26,189 --> 00:08:28,810
First off, I showed you this slide in day\n20’s video.
104
00:08:28,810 --> 00:08:33,899
Assuming these switches all come online at\n
105
00:08:33,899 --> 00:08:38,469
bridge, and each will send BPDUs out of all\ninterfaces.
106
00:08:38,469 --> 00:08:43,500
However, once the network has converged and\n
107
00:08:43,500 --> 00:08:46,480
roles, only the root bridge sends BPDUs.
108
00:08:46,480 --> 00:08:51,779
Then, the other switches will forward these\n
109
00:08:51,779 --> 00:08:58,429
information like the bridge root cost, sending\n
110
00:08:58,429 --> 00:09:05,049
Then, two seconds later, the root bridge will\n
111
00:09:05,049 --> 00:09:09,240
again forward these BPDUs on their designated\nports.
112
00:09:09,240 --> 00:09:14,419
Note that they do not forward the BPDUs out\n
113
00:09:19,480 --> 00:09:22,220
Next up, the forward delay timer.
114
00:09:22,220 --> 00:09:26,589
This is the length of the Listening and Learning\n
115
00:09:29,370 --> 00:09:34,490
Note that this is the length of each of the\n
116
00:09:34,490 --> 00:09:40,060
So, with the default Forward delay timer of\n
117
00:09:40,059 --> 00:09:44,609
for the switchport to move through both states\n
118
00:09:44,610 --> 00:09:50,450
Then the final timer, one I haven’t told\n
119
00:09:50,450 --> 00:09:55,440
This timer indicates how long an interface\n
120
00:09:57,360 --> 00:10:00,278
So, this will need some more explanation.
121
00:10:02,929 --> 00:10:08,399
Remember that each collision domain has one\n
122
00:10:10,220 --> 00:10:16,829
So, all root ports and non-designated ports\n
123
00:10:16,828 --> 00:10:24,039
The root bridge, SW3, sends BPDUs, and then\n
124
00:10:27,190 --> 00:10:33,029
To demonstrate the Max Age timer, let’s\n
125
00:10:33,028 --> 00:10:37,970
It just received a BPDU, so the max age timer\nis reset to 20.
126
00:10:42,028 --> 00:10:46,850
And then the root bridge sends BPDUs, because\n
127
00:10:46,850 --> 00:10:54,879
they are forwarded by the other switches,\n
128
00:10:57,669 --> 00:11:02,419
But what if a failure occurs on the connection\n
129
00:11:02,419 --> 00:11:08,759
The root bridge will send BPDUs, and other\n
130
00:11:08,759 --> 00:11:16,000
G0/0 interface is down so SW2 no longer receives\n
131
00:11:16,000 --> 00:11:20,169
So, the max age timer continues counting down.
132
00:11:22,559 --> 00:11:28,278
15… and if the failure doesn’t recover\n
133
00:11:28,278 --> 00:11:34,409
its G0/1 interface, SW2’s max age timer\n
134
00:11:37,159 --> 00:11:42,409
First of all, If another BPDU is received\n
135
00:11:42,409 --> 00:11:46,448
the time will reset to 20 seconds and no changes\nwill occur.
136
00:11:46,448 --> 00:11:53,159
However, If another BPDU is not received,\n
137
00:11:53,159 --> 00:11:59,750
switch will reevaluate its STP choices, including\n
138
00:12:02,328 --> 00:12:07,309
After these decisions, if a non-designated\n
139
00:12:07,309 --> 00:12:13,518
root port, it will transition from the blocking\n
140
00:12:13,519 --> 00:12:18,149
learning state (again for 15 seconds), and then finally\n
141
00:12:18,149 --> 00:12:24,259
So, it can take a total of 50 seconds for\n
142
00:12:27,159 --> 00:12:31,870
Well, tThese timers and transitional states\n
143
00:12:31,870 --> 00:12:36,049
created by an interface moving to forwarding\nstate too soon.
144
00:12:36,049 --> 00:12:40,609
I showed you in the previous lecture how dangerous\n
145
00:12:40,610 --> 00:12:44,860
That’s why spanning tree protocol is very\n
146
00:12:45,860 --> 00:12:51,259
However, a forwarding interface can move directly\n
147
00:12:51,259 --> 00:12:53,990
about creating a loop by blocking an interface.
148
00:12:53,990 --> 00:12:59,509
But, as I just said, a blocking interface\n
149
00:12:59,509 --> 00:13:03,389
It must go through the listening and learning\nstates.
150
00:13:03,389 --> 00:13:09,500
So let’s move on to check out the spanning\n
151
00:13:09,500 --> 00:13:13,669
First off, in the Ethernet header section,\n
152
00:13:13,669 --> 00:13:25,120
Cisco’s PVST+ uses the destination MAC address\n
153
00:13:25,120 --> 00:13:30,089
I recommend remembering this, it’s a little\n
154
00:13:31,620 --> 00:13:36,220
For remembering little facts like these, I\n
155
00:13:36,220 --> 00:13:38,629
deck I include with this video.
156
00:13:38,629 --> 00:13:44,120
I mentioned PVST in the previous lecture,\nbut what’s PVST+?
157
00:13:44,120 --> 00:13:52,539
Well, PVST is an older version which only\n
158
00:13:52,539 --> 00:13:56,120
PVST+ is a newer version which supports dot1q.
159
00:13:56,120 --> 00:14:03,269
I might use the term ‘PVST’ sometimes,\n
160
00:14:06,019 --> 00:14:11,480
By the way, since I mentioned the MAC address,\n
161
00:14:11,480 --> 00:14:21,360
PVST or PVST+, uses a destination MAC address\nof 0180.c200.0000.
162
00:14:21,360 --> 00:14:25,820
Again, you probably should remember that fact\nfor the exam.
163
00:14:25,820 --> 00:14:29,220
Now let’s move on to the spanning tree BPDU\nitself.
164
00:14:29,220 --> 00:14:33,990
I don’t think you need to memorize the BPDU for the CCNA, but I
165
00:14:33,990 --> 00:14:38,089
give you an introduction to what is included\nin the BPDU.
166
00:14:38,089 --> 00:14:44,210
The first three fields are the protocol identifier,\n
167
00:14:45,339 --> 00:14:50,900
The protocol version identifier is set to\n
168
00:14:50,899 --> 00:14:55,860
a different value here when we look at rapid\n
169
00:14:55,860 --> 00:15:04,209
Finally, the BPDU type is hexadecimal 00 for\n
170
00:15:04,208 --> 00:15:10,748
There are other types of BPDUs, but we don’t\n
171
00:15:10,749 --> 00:15:15,480
Next up are some flags, these are used to\n
172
00:15:15,480 --> 00:15:21,659
Again, I don’t think we need to go in depth\n
173
00:15:21,659 --> 00:15:27,600
Next up is the root identifier, which gives\n
174
00:15:27,600 --> 00:15:33,528
is the VLAN ID, 10 in this case, and the bridge\n
175
00:15:34,528 --> 00:15:39,259
I set the MAC address to all A’s in this\ncase.
176
00:15:41,100 --> 00:15:45,930
It’s 0 in this case, so you know that this\nis the root bridge.
177
00:15:45,929 --> 00:15:49,588
You can also know this is the root bridge\n
178
00:15:49,589 --> 00:15:55,660
The information in the bridge identifier field\n
179
00:15:55,659 --> 00:15:58,879
meaning this is the root bridge.
180
00:15:58,879 --> 00:16:03,769
After that is the port identifier, the interface\n
181
00:16:07,169 --> 00:16:14,649
8 0 in hexadecimal is equivalent to 128, which\n
182
00:16:15,669 --> 00:16:19,448
0 2 is the number of the port itself.
183
00:16:22,480 --> 00:16:27,759
Message age is something I haven’t mentioned\n
184
00:16:27,759 --> 00:16:32,209
and is increased by 1 each time it is forwarded\n
185
00:16:32,208 --> 00:16:38,619
It is subtracted from the max age when a switch\n
186
00:16:38,620 --> 00:16:44,009
is passed through 5 switches, when it reaches\n
187
00:16:44,009 --> 00:16:50,060
its max age timer to 15, meaning each time\n
188
00:16:50,059 --> 00:16:54,689
to 15 instead of 20, even though the max age\ntimer is 20.
189
00:16:54,690 --> 00:17:01,209
I don’t think that’s an important topic\n
190
00:17:01,208 --> 00:17:07,940
After that we have the three timers we talked\n
191
00:17:07,940 --> 00:17:12,240
By the way, the spanning tree timers on the\n
192
00:17:12,240 --> 00:17:19,019
for the rest of the switches in the network,\n
193
00:17:19,019 --> 00:17:23,000
Next let’s talk about some optional features\n
194
00:17:25,329 --> 00:17:28,869
These are features that can be enabled to\n
195
00:17:31,160 --> 00:17:33,810
The first one is called portfast.
196
00:17:33,809 --> 00:17:37,240
It solves one problem of spanning tree.
197
00:17:37,240 --> 00:17:42,720
Portfast can be enabled on interfaces which\n
198
00:17:42,720 --> 00:17:45,400
interface on each of these switches.
199
00:17:45,400 --> 00:17:48,280
These are designated ports, in a forwarding\nstate.
200
00:17:48,279 --> 00:17:54,149
However, when they are first turned on or\n
201
00:17:54,150 --> 00:17:58,930
the Listening and Learning states first before\n
202
00:18:00,500 --> 00:18:07,920
15 seconds for Listening and 15 seconds for\n
203
00:18:07,920 --> 00:18:12,160
I want you to open up Packet Tracer and try\na little experiment.
204
00:18:12,160 --> 00:18:16,620
For this experiment, make sure Show Link Lights\nis enabled.
205
00:18:16,619 --> 00:18:21,739
You can enable it by clicking on options,\n
206
00:18:22,789 --> 00:18:29,129
I want you to place a switch and a PC like\n
207
00:18:31,200 --> 00:18:35,059
At first you should see that the link light\n
208
00:18:35,059 --> 00:18:40,029
This is the same if you connect a real physical\n
209
00:18:42,619 --> 00:18:47,169
It’s because the port is not Forwarding\n
210
00:18:48,539 --> 00:18:54,309
However, 30 seconds later you should finally\n
211
00:18:54,309 --> 00:18:56,700
The port is finally forwarding.
212
00:18:56,700 --> 00:19:01,049
I told you why spanning tree goes through\n
213
00:19:01,049 --> 00:19:06,220
forwarding state, it’s because Layer 2 loops\n
214
00:19:06,220 --> 00:19:11,960
wants to be absolutely sure no loop will be\n
215
00:19:11,960 --> 00:19:17,440
However, only interfaces connected to another\n
216
00:19:17,440 --> 00:19:20,200
There is no risk of forming a loop with an\nend host.
217
00:19:20,200 --> 00:19:25,279
So, wouldn’t it be nice if these ports connected\n
218
00:19:25,279 --> 00:19:30,250
away, without having to wait 30 seconds to\n
219
00:19:30,250 --> 00:19:34,039
Well, that’s what portfast does.
220
00:19:34,039 --> 00:19:38,269
Portfast allows a port to move immediately\n
221
00:19:40,079 --> 00:19:44,929
If used, it must be enabled only on ports\n
222
00:19:44,930 --> 00:19:50,250
If enabled on a port connected to another\n
223
00:19:50,250 --> 00:19:54,990
The purpose of the listening and learning\n
224
00:19:54,990 --> 00:19:59,880
them is risky when connected to another switch.
225
00:19:59,880 --> 00:20:03,490
We haven’t looked at any other spanning\n
226
00:20:03,490 --> 00:20:07,319
operates by default even without configuration.
227
00:20:07,319 --> 00:20:13,679
We will look at general spanning tree configuration,\n
228
00:20:13,680 --> 00:20:19,549
Portfast is enabled at the interface level\n
229
00:20:19,549 --> 00:20:24,180
Then we get a warning about what I just told\n
230
00:20:26,950 --> 00:20:31,420
There is also a message saying that, even\n
231
00:20:31,420 --> 00:20:36,890
take effect if the interface is in a non-trunking\n
232
00:20:36,890 --> 00:20:41,690
That’s because trunk ports are typically\n
233
00:20:41,690 --> 00:20:47,430
You can still configure portfast on a trunk\n
234
00:20:47,430 --> 00:20:52,431
You can also enable portfast with the following\n
235
00:20:54,880 --> 00:20:59,990
This enables portfast on all access ports,\nbut not trunk ports.
236
00:20:59,990 --> 00:21:04,910
So, portfast is a great feature for getting\n
237
00:21:04,910 --> 00:21:08,350
quickly without having to wait 30 seconds.
238
00:21:08,349 --> 00:21:12,269
However, it can still be a risk.
239
00:21:12,269 --> 00:21:16,490
What if an employee plugs another switch into\n
240
00:21:16,490 --> 00:21:21,500
This employee doesn’t necessarily have malicious\n
241
00:21:23,650 --> 00:21:28,550
Because portfast is putting these interfaces\n
242
00:21:30,630 --> 00:21:35,250
Portfast can also cause loops if the network\n
243
00:21:35,250 --> 00:21:40,839
perhaps a host is moved to a different switchport\n
244
00:21:40,839 --> 00:21:46,279
Anyway, the point is that there is a risk\nto using portfast.
245
00:21:46,279 --> 00:21:51,660
However, there is an additional spanning tree\n
246
00:21:56,589 --> 00:22:02,339
If an interface with BPDU Guard enabled receives\n
247
00:22:02,339 --> 00:22:05,990
will be shut down to prevent a loop from forming.
248
00:22:05,990 --> 00:22:09,740
BPDU guard is very simple to configure.
249
00:22:09,740 --> 00:22:15,319
From interface configuration mode, use the\n
250
00:22:17,049 --> 00:22:20,839
Similar to portfast, there is also an option\n
251
00:22:22,849 --> 00:22:29,889
From global config mode, use the command SPANNING-TREE\n
252
00:22:29,890 --> 00:22:34,970
This enables BPDU Guard on all portfast-enabled\ninterfaces.
253
00:22:34,970 --> 00:22:40,009
Notice that the commands are a little different,\n
254
00:22:40,009 --> 00:22:44,799
spanning-tree bpduguard enable, no mention\nof portfast.
255
00:22:44,799 --> 00:22:49,609
However to enable it globally, you have to\n
256
00:22:52,740 --> 00:22:58,269
I took this screenshot in packet tracer, so\n
257
00:22:58,269 --> 00:23:04,740
than the previous one, but I connected a switch\n
258
00:23:04,740 --> 00:23:10,279
you can see what happens when a BPDU arrives\n
259
00:23:10,279 --> 00:23:14,399
The port is disabled, it is effectively shut\ndown.
260
00:23:14,400 --> 00:23:17,890
What if you want to enable the port again?
261
00:23:17,890 --> 00:23:23,880
To enable a port that was disabled by BPDU\n
262
00:23:25,539 --> 00:23:28,129
You can see that the interface comes up.
263
00:23:28,130 --> 00:23:33,330
However, if you didn’t actually solve the\n
264
00:23:33,329 --> 00:23:39,119
you can see here that the interface will immediately\n
265
00:23:39,119 --> 00:23:45,729
So, make sure you actually solve the problem\n
266
00:23:45,730 --> 00:23:52,589
In terms of spanning tree optional features,\n
267
00:23:53,589 --> 00:24:00,099
I also showed you BPDU guard because it is\n
268
00:24:00,099 --> 00:24:03,980
There are many other optional features that\n
269
00:24:03,980 --> 00:24:08,951
all of them for the CCNA, but let me just\n
270
00:24:08,951 --> 00:24:14,650
least know the name and basic purpose of,\n
271
00:24:14,650 --> 00:24:18,690
They are Root Guard and Loop Guard.
272
00:24:18,690 --> 00:24:25,170
If you enable root guard on an interface,\n
273
00:24:25,170 --> 00:24:30,990
bridge ID) on that interface, the switch will\n
274
00:24:30,990 --> 00:24:33,500
The interface will be disabled.
275
00:24:33,500 --> 00:24:38,470
This helps maintain the spanning tree topology\n
276
00:24:38,470 --> 00:24:44,480
either with bad intent, or perhaps without\n
277
00:24:44,480 --> 00:24:50,279
If you enable loop guard on an interface,\n
278
00:24:52,690 --> 00:24:55,299
The interface will be disabled.
279
00:24:55,299 --> 00:24:59,649
This prevents loops that can happen if an\n
280
00:24:59,650 --> 00:25:04,170
what is called a ‘unidirectional link’\n
281
00:25:04,170 --> 00:25:06,289
to forward it, or the opposite.
282
00:25:06,289 --> 00:25:10,579
So, those are two other optional spanning\ntree features.
283
00:25:10,579 --> 00:25:16,349
However, as I said, You probably don’t have\n
284
00:25:16,349 --> 00:25:21,750
such as UplinkFast, Backbone Fast, etc) for\nthe CCNA.
285
00:25:21,750 --> 00:25:25,720
But make sure you know Portfast and BPDU Guard.
286
00:25:25,720 --> 00:25:30,490
If you want to read more about the others\n
287
00:25:30,490 --> 00:25:37,380
Finally, let’s look at some basic spanning\n
288
00:25:37,380 --> 00:25:43,130
You can configure the spanning mode the switch\n
289
00:25:43,130 --> 00:25:45,840
and then you can see there are three options.
290
00:25:45,839 --> 00:25:50,949
MST, multiple spanning tree, is not a topic\n
291
00:25:50,950 --> 00:25:57,120
PVST is the classic spanning tree but with\n
292
00:25:59,039 --> 00:26:04,339
Rapid-PVST is an improved version I will tell\n
293
00:26:04,339 --> 00:26:11,250
Modern Cisco switches run rapid-PVST by default,\n
294
00:26:11,250 --> 00:26:15,369
However, if you want to try out the classic\n
295
00:26:15,369 --> 00:26:23,199
these demonstrations, you can enable it with\n
296
00:26:23,200 --> 00:26:29,400
You can also manually configure the root bridge\n
297
00:26:29,400 --> 00:26:34,660
With these MAC addresses and the default priority\n
298
00:26:34,660 --> 00:26:38,980
However, we could configure SW3 to be the\nroot bridge.
299
00:26:38,980 --> 00:26:42,880
We could also configure something called a\n
300
00:26:42,880 --> 00:26:47,260
next in line to become the root bridge if\n
301
00:26:47,259 --> 00:26:51,470
Let’s see how to configure that.
302
00:26:51,470 --> 00:26:56,210
This is how to configure the root bridge,\n
303
00:26:56,210 --> 00:27:03,410
SPANNING-TREE VLAN, followed by the vlan number,\n
304
00:27:03,410 --> 00:27:06,700
Now you can see that this bridge has become the\nroot.
305
00:27:06,700 --> 00:27:12,100
This command sets the STP priority to 24576.
306
00:27:12,099 --> 00:27:17,719
If another switch already has a priority lower\n
307
00:27:17,720 --> 00:27:21,539
to 4096 less than the other switch’s priority.
308
00:27:21,539 --> 00:27:27,329
So, it makes this switch have the lowest priority,\n
309
00:27:27,329 --> 00:27:30,990
If you then check the running-config, you\n
310
00:27:30,990 --> 00:27:37,220
applied in this case is SPANNING-TREE VLAN\n1 PRIORITY 24576.
311
00:27:37,220 --> 00:27:43,400
So, this commands tells the switch to apply\n
312
00:27:43,400 --> 00:27:51,590
with the priority 24576, or 4096 less than\n
313
00:27:51,589 --> 00:27:56,299
The command to set the secondary root bridge,\n
314
00:27:57,829 --> 00:28:03,669
SPANNING-TREE VLAN, vlan number, ROOT SECONDARY.
315
00:28:03,670 --> 00:28:06,990
Now the priority has been set to 28672.
316
00:28:06,990 --> 00:28:13,650
So, this command sets the spanning tree priority\n
317
00:28:13,650 --> 00:28:19,691
However, like the root primary command, the\n
318
00:28:21,230 --> 00:28:26,460
So, for both of these commands, you could\n
319
00:28:26,460 --> 00:28:31,319
as you see here to configure the root bridge,\n
320
00:28:31,319 --> 00:28:36,599
way to do it without remembering the different\n
321
00:28:36,599 --> 00:28:40,909
You may remember from the last lecture, that\n
322
00:28:40,910 --> 00:28:46,130
of 4096, so the root command is easier to\nuse.
323
00:28:49,910 --> 00:28:58,029
The interface between SW1 and SW2 is disabled\n
324
00:28:58,029 --> 00:29:03,450
This topology is running Cisco’s PVST+,\n
325
00:29:05,500 --> 00:29:10,099
Perhaps there is another VLAN, VLAN 2, in\n
326
00:29:12,359 --> 00:29:17,289
It will look like this, the default topology,\n
327
00:29:19,970 --> 00:29:26,250
In VLAN 2, the connection between SW1 and\n
328
00:29:26,250 --> 00:29:29,819
between SW2 and SW3 will be disabled.
329
00:29:29,819 --> 00:29:34,309
This allows for what’s called spanning tree\nload balancing.
330
00:29:34,309 --> 00:29:39,789
If you have multiple VLANs in your network,\n
331
00:29:39,789 --> 00:29:42,399
a waste of interface bandwidth.
332
00:29:42,400 --> 00:29:46,269
That connection will be doing nothing, just\n
333
00:29:47,710 --> 00:29:53,029
However, if you configure a different root\n
334
00:29:53,029 --> 00:29:55,859
will disable different interfaces.
335
00:29:55,859 --> 00:30:02,369
Okay, to check if you understood that explanation,\n
336
00:30:02,369 --> 00:30:07,569
This is quiz question 7, because in day 20’s\n
337
00:30:08,569 --> 00:30:13,599
Two VLANs are active in this network, 10 and\n20.
338
00:30:13,599 --> 00:30:17,949
By default, SW3 is the root bridge for both\nVLANs.
339
00:30:17,950 --> 00:30:24,400
Configure SW1 as the primary root for VLAN10\n
340
00:30:24,400 --> 00:30:31,460
Configure SW2 as the primary root for VLAN20\n
341
00:30:31,460 --> 00:30:36,390
Which two commands should you issue on SW1,\n
342
00:30:37,390 --> 00:30:42,560
So, use the commands I just showed you, the\n
343
00:30:44,980 --> 00:30:49,839
You don’t have access to the CLI so just\n
344
00:30:59,220 --> 00:31:05,920
We want to make SW1 the primary root bridge\n
345
00:31:05,921 --> 00:31:09,259
essentially it acts like a backup root bridge\nfor VLAN20.
346
00:31:09,259 --> 00:31:14,379
So, these are the commands to issue on SW1.
347
00:31:14,380 --> 00:31:16,990
On SW2 we want to do the opposite.
348
00:31:16,990 --> 00:31:22,480
It should be the root bridge for VLAN20, and\n
349
00:31:22,480 --> 00:31:28,069
so it will have the second lowest priority\n
350
00:31:29,619 --> 00:31:34,859
These are the commands to issue on SW2, basically\n
351
00:31:34,859 --> 00:31:37,459
So, did you get the correct answers?
352
00:31:39,529 --> 00:31:43,490
Please watch the next video which will be\n
353
00:31:43,490 --> 00:31:48,059
learn in this video, you can practice with\n
354
00:31:48,059 --> 00:31:52,389
own labs in packet tracer to practice.
355
00:31:52,390 --> 00:31:58,070
So, with those settings, perhaps the VLAN10 topology\n
356
00:31:58,069 --> 00:32:01,490
And then perhaps the VLAN20 topology looks like this.
357
00:32:01,490 --> 00:32:07,870
So, different connections are used in different\n
358
00:32:07,869 --> 00:32:13,429
interfaces, this is called load balancing.
359
00:32:13,430 --> 00:32:17,840
Before moving on to the rest of the quiz questions\n
360
00:32:17,839 --> 00:32:22,750
show you how to configure some spanning-tree\nport settings.
361
00:32:22,750 --> 00:32:26,589
There are two main settings you can configure\n
362
00:32:26,589 --> 00:32:31,319
The cost, and the port priority, and as you\n
363
00:32:31,319 --> 00:32:35,480
on a per-VLAN basis like the bridge priority.
364
00:32:38,150 --> 00:32:42,870
It’s the root cost, remember the chart I\nshowed you in day 20.
365
00:32:42,869 --> 00:32:47,799
FastEthernet costs 19, gigabit ethernet costs\n4, etc.
366
00:32:47,799 --> 00:32:52,869
It’s used primarily to determine the root\n
367
00:32:52,869 --> 00:32:56,739
selecting designated and non-designated ports.
368
00:32:56,740 --> 00:33:00,049
How about the priority, do you remember what\nit is used for?
369
00:33:00,049 --> 00:33:05,970
Well, it is the first half of the port ID,\n
370
00:33:07,839 --> 00:33:10,389
Why would you want to change either of these\nvalues?
371
00:33:10,390 --> 00:33:17,140
Well, to change the result of the root port\n
372
00:33:17,140 --> 00:33:20,890
I won’t give a detailed example here, but\n
373
00:33:20,890 --> 00:33:24,400
video, so make sure to watch that.
374
00:33:24,400 --> 00:33:29,970
First I configured the cost of this interface,\n
375
00:33:30,970 --> 00:33:38,370
Then I set the port-priority, which is configured\n
376
00:33:38,369 --> 00:33:42,359
Those are the only spanning tree interface\n
377
00:33:42,359 --> 00:33:46,309
Again, stay tuned for the lab video to try\nthem out.
378
00:33:49,210 --> 00:33:52,480
We covered the different spanning tree states\nand timers used.
379
00:33:52,480 --> 00:33:58,410
We took a brief look at the structure of a\n
380
00:33:58,410 --> 00:34:04,940
the spanning-tree optional features, focusing\n
381
00:34:04,940 --> 00:34:10,210
Finally we did some basic spanning tree configurations,\n
382
00:34:10,210 --> 00:34:14,610
different root bridges in different VLANs\n
383
00:34:14,610 --> 00:34:19,860
interfaces, and then some basic spanning tree\n
384
00:34:19,860 --> 00:34:25,120
Okay, for today’s quiz we’ll do 3 more\n
385
00:34:27,739 --> 00:34:33,080
After that, one special practice question\n
386
00:34:33,081 --> 00:34:39,070
far the best practice exams for the CCNA there\n
387
00:34:39,070 --> 00:34:43,769
If you want to get a copy of Boson ExSim,\n
388
00:34:43,769 --> 00:34:48,489
Now let’s go to question 8 of the quiz.
389
00:34:48,489 --> 00:34:54,159
So, continuing from quiz question 7 we did\n
390
00:34:54,159 --> 00:34:59,170
You connect a PC to a switch, however for\n
391
00:35:00,719 --> 00:35:05,649
Which two options could fix this issue and\n
392
00:35:07,110 --> 00:35:09,480
Each answer is a complete solution.
393
00:35:09,480 --> 00:35:14,179
A, enable portfast on the switch port you\nconnect the PC to.
394
00:35:14,179 --> 00:35:17,960
B, reduce the STP hello timer.
395
00:35:17,960 --> 00:35:21,760
C, reduce the STP forward delay timer.
396
00:35:21,760 --> 00:35:26,050
Or D, reduce the STP max age timer.
397
00:35:26,050 --> 00:35:32,890
Pause the video to think about your answer,\n
398
00:35:32,889 --> 00:35:39,980
The answers are A and C. A, portfast, allows\n
399
00:35:39,980 --> 00:35:44,969
spanning tree states and enter the forwarding\n
400
00:35:47,750 --> 00:35:52,650
As for C, the forward delay timer determines\n
401
00:35:53,889 --> 00:35:58,150
If you shorten this timer, the switch will\n
402
00:35:58,150 --> 00:36:02,581
However, it is recommended that you leave\n
403
00:36:02,581 --> 00:36:05,440
default settings were chosen for a reason.
404
00:36:09,309 --> 00:36:17,139
A packet capture indicates that a switch port\n
405
00:36:17,139 --> 00:36:20,659
What is the STP port priority of this port?
406
00:36:30,260 --> 00:36:37,070
Pause the video to think about your answer.
407
00:36:40,670 --> 00:36:47,889
The first half of the port ID, hexadecimal\n
408
00:36:47,889 --> 00:36:53,920
Hexadecimal 8 0 is equivalent to 128 in decimal,\n
409
00:36:57,969 --> 00:37:02,309
You want to make sure that a Layer 2 loop\n
410
00:37:04,679 --> 00:37:07,639
Which spanning tree optional feature achieves\nthis?
411
00:37:16,949 --> 00:37:22,639
Pause the video to think about your anwer.
412
00:37:25,900 --> 00:37:31,690
BPDU guard will shutdown an interface if a\n
413
00:37:34,030 --> 00:37:37,900
It should be enabled on portfast-enabled switch\n
414
00:37:37,900 --> 00:37:43,869
Okay, that’s all for the quiz, let’s take\n
415
00:37:45,800 --> 00:37:51,880
Okay, for today's Boson ExSim practice question\n
416
00:37:51,880 --> 00:37:56,860
as in Day 20's video because at the end of\n
417
00:37:56,860 --> 00:38:00,470
enough to answer the questions from Boson\n
418
00:38:00,469 --> 00:38:03,219
Well, now we can answer at least some of them.
419
00:38:03,219 --> 00:38:06,279
So, let's read the question one more time.
420
00:38:06,280 --> 00:38:10,220
You want to decrease the amount of time that\n
421
00:38:12,139 --> 00:38:15,750
PortFast is not configured on any of the switch\n
422
00:38:15,750 --> 00:38:21,110
You issue the SPANNING-TREE PORTFAST DEFAULT\n
423
00:38:21,110 --> 00:38:24,180
Which of the ports on SwitchA will use PortFast?
424
00:38:25,699 --> 00:38:29,719
A, no ports because PortFast cannot be enabled\nglobally.
425
00:38:34,679 --> 00:38:37,619
Okay, you should know the answer to this question.
426
00:38:37,619 --> 00:38:44,319
Please pause the video here to think about\nyour answer.
427
00:38:46,170 --> 00:38:51,110
So, you should know, we just talked about\n
428
00:38:51,110 --> 00:38:53,930
Or at least I think it is, let's check.
429
00:38:53,929 --> 00:38:58,940
To check your answer click down here, 'show\nanswer'.
430
00:39:00,110 --> 00:39:05,019
Okay, so not only does it tell you it's correct,\n
431
00:39:05,019 --> 00:39:07,360
explanation of why it's correct.
432
00:39:07,360 --> 00:39:11,500
Why D is correct, and why A, B, and C are\nincorrect.
433
00:39:11,500 --> 00:39:15,980
That's one of the great things about Boson\n
434
00:39:15,980 --> 00:39:21,260
Personally I think a practice exam that just\n
435
00:39:21,260 --> 00:39:25,800
you why it's correct or why it's incorrect,\nisn't very useful.
436
00:39:25,800 --> 00:39:30,289
So let's read just at least this first part\n
437
00:39:30,289 --> 00:39:33,570
All access ports on SwitchA will use PortFast.
438
00:39:33,570 --> 00:39:38,370
PortFast enables faster connectivity for hosts\n
439
00:39:38,369 --> 00:39:43,000
If PortFast is not enabled, a switch port\n
440
00:39:43,000 --> 00:39:46,710
learning states before it enters the forwarding\nstate.
441
00:39:46,710 --> 00:39:51,880
This process can take as long as 30 seconds\n
442
00:39:51,880 --> 00:39:57,390
In addition, port initialization can take\n
443
00:39:58,869 --> 00:40:04,750
I haven't talked about this yet in the course,\n
444
00:40:07,019 --> 00:40:10,840
PortFast transitions the port into the STP\n
445
00:40:10,840 --> 00:40:13,220
STP listening and learning states.
446
00:40:13,219 --> 00:40:15,899
Okay, and there's more explanation down here.
447
00:40:15,900 --> 00:40:21,039
Plus references, here to the official cert\n
448
00:40:22,039 --> 00:40:24,969
And some Cisco documentation you can read\nfor free online.
449
00:40:24,969 --> 00:40:30,549
Okay, so if you want to get a copy of Boson\n
450
00:40:30,550 --> 00:40:38,740
I used them myself for my CCNA and CCNP, please\n
451
00:40:38,739 --> 00:40:42,099
There will be supplementary materials for\nthis video.
452
00:40:42,099 --> 00:40:46,630
There will be a review flashcard deck to use\n
453
00:40:46,630 --> 00:40:50,260
Download the deck from the link in the description.
454
00:40:50,260 --> 00:40:53,420
There will also be a packet tracer practice\nlab.
455
00:40:53,420 --> 00:40:57,389
Please be sure to watch the practice lab and\n
456
00:40:57,389 --> 00:41:02,400
practice with the configurations you learned\nin this video.
457
00:41:02,400 --> 00:41:07,519
Before finishing today’s video I want to\n
458
00:41:07,519 --> 00:41:15,449
Thank you to Vikram, Joyce, Marek, Samil,\n
459
00:41:15,449 --> 00:41:22,389
Miguel, Yousif, Kone, Boson Software, the\n
460
00:41:22,389 --> 00:41:26,829
Charlsetta, Lito, Yonatan, Mike, Aleksandr,\nand Vance.
461
00:41:26,829 --> 00:41:33,110
Sorry if I pronounced your name incorrectly,\n
462
00:41:33,110 --> 00:41:38,079
One of you is still displaying as Channel\n
463
00:41:38,079 --> 00:41:41,360
me know and I’ll see if YouTube can fix\nit.
464
00:41:41,360 --> 00:41:47,360
This is the list of JCNP-level members at\n
465
00:41:47,360 --> 00:41:52,920
2020, so if you signed up recently and your name\n
466
00:41:58,110 --> 00:42:02,170
Please subscribe to the channel, like the\n
467
00:42:02,170 --> 00:42:05,369
with anyone else studying for the CCNA.
468
00:42:05,369 --> 00:42:08,250
If you want to leave a tip, check the links\nin the description.
469
00:42:08,250 --> 00:42:13,869
I'm also a Brave verified publisher and accept\n
38797
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.