All language subtitles for Free-CCNA-Spanning-Tree-Protocol-Part-1-Day-20-CCNA-200-301-Complete-Course_en

af Afrikaans
ak Akan
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranî)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:04,849 --> 00:00:08,160 This is a free, complete course for the CCNA. 2 00:00:08,160 --> 00:00:12,089 If you like these videos, please subscribe\n 3 00:00:12,089 --> 00:00:17,300 Also, please like and leave a comment, and\n 4 00:00:20,399 --> 00:00:26,919 In this video we will move on to another important\n 5 00:00:26,920 --> 00:00:29,380 for network engineers understand. 6 00:00:29,379 --> 00:00:32,780 That is STP, Spanning Tree Protocol. 7 00:00:32,780 --> 00:00:40,260 The CCNA Exam Topics list mentions Rapid spanning\n 8 00:00:40,259 --> 00:00:46,939 However, to understand rapid STP, I think\n 9 00:00:47,119 --> 00:00:53,859 So, first we will talk about STP, which will\n 10 00:00:53,869 --> 00:00:57,799 and then in a future video I will teach you about rapid\nSTP. 11 00:00:57,799 --> 00:01:01,149 Let’s take a look at what we’ll cover\nin this video. 12 00:01:01,149 --> 00:01:06,900 First, I’ll talk about redundancy in networks,\n 13 00:01:06,900 --> 00:01:10,830 Then I will introduce STP, Spanning Tree Protocol. 14 00:01:10,829 --> 00:01:15,670 I will introduce its purpose, the problem\nit solves, etc. 15 00:01:15,670 --> 00:01:18,950 Also, remember to watch until the end of today’s\nquiz. 16 00:01:18,950 --> 00:01:24,000 I will once again feature a bonus question\n 17 00:01:27,959 --> 00:01:32,199 If you’re looking for a set of practice\n 18 00:01:32,200 --> 00:01:34,240 is without a doubt the best there is. 19 00:01:34,239 --> 00:01:40,869 I used ExSim for my CCNA and CCNP, so I feel\n 20 00:01:42,120 --> 00:01:48,310 If you want to grab a copy of Boson ExSim,\n 21 00:01:49,760 --> 00:01:54,310 First, just a few points about redundancy\nin networks. 22 00:01:54,310 --> 00:01:57,280 Redundancy is an essential part of network\ndesign. 23 00:01:57,280 --> 00:02:01,299 A network that is not redundant is simply\nnot acceptable. 24 00:02:01,299 --> 00:02:08,689 Modern networks are expected to run 24 hours\n 25 00:02:08,689 --> 00:02:12,870 Even a short downtime can be disastrous for\na business. 26 00:02:12,870 --> 00:02:18,539 Imagine if Amazon’s network went down for\n 27 00:02:18,539 --> 00:02:23,030 If one network component fails, you must ensure\n 28 00:02:24,669 --> 00:02:30,019 Finally, as much as possible, you must implement\n 29 00:02:32,139 --> 00:02:36,979 As network engineers, we are responsible for\n 30 00:02:36,979 --> 00:02:42,859 to make sure that that infrastructure is resilient\n 31 00:02:42,860 --> 00:02:46,080 First off, here is a poorly designed network. 32 00:02:46,080 --> 00:02:49,860 There are many points of failure here which\n 33 00:02:49,860 --> 00:02:54,940 For example if this connection is cut\n 34 00:02:54,939 --> 00:02:57,579 loses connectivity to the Internet. 35 00:02:57,580 --> 00:03:03,160 Or, if this connection is cut off due to a\n 36 00:03:03,159 --> 00:03:06,030 within the LAN, and out to the Internet. 37 00:03:06,030 --> 00:03:11,680 Okay, those are just two examples, let’s\n 38 00:03:11,680 --> 00:03:14,599 This network here is a much better design. 39 00:03:14,598 --> 00:03:20,039 If this PC wants to reach the Internet, it\n 40 00:03:20,039 --> 00:03:26,620 However, even if this router has a hardware\n 41 00:03:26,620 --> 00:03:31,430 reach the Internet via this or another alternate\npath. 42 00:03:31,430 --> 00:03:37,319 Perhaps traffic to this other PC in the LAN\n 43 00:03:39,129 --> 00:03:43,519 That’s not a problem, because this alternate\npath is available. 44 00:03:43,520 --> 00:03:48,599 So, I think you can see the benefit of designing\n 45 00:03:48,598 --> 00:03:52,829 However, you may be asking, what if this switch\nfails? 46 00:03:52,830 --> 00:03:58,489 Well, if that is the case, all hosts connected\n 47 00:03:58,489 --> 00:04:04,659 Unfortunately, Most PCs only have a single\n 48 00:04:04,659 --> 00:04:07,259 only be plugged into a single switch. 49 00:04:07,259 --> 00:04:12,239 However, important servers typically have\n 50 00:04:12,239 --> 00:04:16,590 multiple switches for redundancy. 51 00:04:16,589 --> 00:04:20,369 We will cover many protocols that are used\n 52 00:04:20,370 --> 00:04:23,759 course, and spanning tree is one of them. 53 00:04:23,759 --> 00:04:29,259 Spanning tree is a Layer 2 protocol by the\n 54 00:04:29,259 --> 00:04:33,270 so within the LAN here, not routing out to\n 55 00:04:34,269 --> 00:04:40,038 I just showed you the benefits of a redundant\n 56 00:04:40,038 --> 00:04:43,248 provides alternate paths if one connection\nfails. 57 00:04:43,249 --> 00:04:47,889 However, without spanning tree, there is a\n 58 00:04:52,740 --> 00:04:55,778 Let me introduce the concept of ‘broadcast\nstorms’. 59 00:04:55,778 --> 00:04:59,939 I’ll use a simplified network topology to\ndemonstrate the issue. 60 00:04:59,939 --> 00:05:08,709 PC1 is 10.0.0.1, PC2 is 10.0.0.2, and PC3\nis 10.0.0.3. 61 00:05:08,709 --> 00:05:13,188 You already know what a switch does with a\n 62 00:05:13,189 --> 00:05:18,430 Let’s say, for example, PC1 wants to send some traffic\nto PC2. 63 00:05:18,430 --> 00:05:21,370 To do that, it needs to know PC2’s MAC address. 64 00:05:21,370 --> 00:05:28,090 So, let’s say PC1 sends an ARP request frame,\n 65 00:05:28,089 --> 00:05:32,819 MAC address of all F's as its Layer2\naddress. 66 00:05:32,819 --> 00:05:37,149 When SW1 receives the frame, what will it\ndo? As I said 67 00:05:37,149 --> 00:05:41,359 you already know what a switch does with broadcast\n 68 00:05:41,360 --> 00:05:45,598 It will flood it out of all interfaces, except\n 69 00:05:45,598 --> 00:05:50,329 So, SW2 and SW3 both receive a copy of the\nframe. 70 00:05:50,329 --> 00:05:54,838 They then do the same thing, they flood it\n 71 00:05:56,338 --> 00:06:01,939 So, PC2 receives the ARP request and will\n 72 00:06:06,490 --> 00:06:11,569 Although PC2 received the ARP request and\n 73 00:06:13,309 --> 00:06:17,159 I’ve cleaned up the arrows so you can see\nthis easier. 74 00:06:17,158 --> 00:06:22,998 As I just said, PC2 received the ARP request\n 75 00:06:24,579 --> 00:06:29,579 The switches will continue flooding them . So,\n 76 00:06:29,579 --> 00:06:34,430 SW1 just received two broadcast frames, on\n 77 00:06:38,838 --> 00:06:44,598 SW2 and SW3 both just received broadcast frames,\n 78 00:06:45,769 --> 00:06:47,808 So, I think you get the point. 79 00:06:50,050 --> 00:06:55,098 Do you remember the TTL, or time to live,\n 80 00:06:55,098 --> 00:06:58,740 It is used to prevent infinite loops at Layer\n3. 81 00:06:58,740 --> 00:07:02,389 But the Ethernet header doesn’t have a TTL\nfield. 82 00:07:02,389 --> 00:07:06,429 These broadcast frames will loop around the\n 83 00:07:06,428 --> 00:07:11,359 If enough of these looped broadcasts accumulate\n 84 00:07:11,360 --> 00:07:14,559 for legitimate traffic to use the network. 85 00:07:14,559 --> 00:07:17,279 This is called a broadcast storm. 86 00:07:17,278 --> 00:07:22,939 Eventually your network will look like this,\n 87 00:07:22,939 --> 00:07:26,159 regular traffic can pass through your network. 88 00:07:26,158 --> 00:07:31,009 The red arrows represent the clock-wise loop\n 89 00:07:31,009 --> 00:07:34,050 arrows the counter-clockwise loop. 90 00:07:34,050 --> 00:07:38,449 However, network congestion isn’t the only\nproblem. 91 00:07:38,449 --> 00:07:43,139 Each time a frame arrives on a switchport,\n 92 00:07:43,139 --> 00:07:47,389 to ‘learn’ the MAC address and update\nits MAC address table. 93 00:07:47,389 --> 00:07:52,240 When the frames with the same source MAC address\n 94 00:07:52,240 --> 00:07:56,449 the switch is continuously updating the interface\n 95 00:07:56,449 --> 00:07:59,218 This is known as MAC Address Flapping. 96 00:07:59,218 --> 00:08:05,699 So, how can we design a network with redundant\n 97 00:08:05,699 --> 00:08:10,610 Well, Spanning Tree Protocol is one answer\nto this problem. 98 00:08:10,610 --> 00:08:16,999 So let’s take a look at Spanning Tree protocol\n 99 00:08:16,999 --> 00:08:22,620 is an industry standard protocol, IEEE 802.1D. 100 00:08:22,620 --> 00:08:27,449 This is the type of STP we will focus on in\n 101 00:08:30,490 --> 00:08:35,470 Because it is so important to prevent Layer\n 102 00:08:36,470 --> 00:08:40,610 So, you won’t only find STP on Cisco switches. 103 00:08:40,610 --> 00:08:47,519 STP prevents Layer 2 loops by placing redundant\n 104 00:08:49,600 --> 00:08:55,279 These interfaces act as backups that can enter\n 105 00:08:55,279 --> 00:08:59,620 meaning an interface that is currently forwarding,\nfails. 106 00:08:59,620 --> 00:09:02,139 Interfaces in a forwarding state behave normally. 107 00:09:02,139 --> 00:09:04,529 They send and receive all normal traffic. 108 00:09:04,529 --> 00:09:12,319 However, Interfaces in a blocking state only\n 109 00:09:12,320 --> 00:09:17,180 or Bridge Protocol Data Units), and some other\nspecific traffic. 110 00:09:17,179 --> 00:09:21,019 Before going more in depth , let me talk about\n 111 00:09:21,019 --> 00:09:26,370 I told you about Ethernet hubs in a previous\nvideo. 112 00:09:26,370 --> 00:09:31,129 Hubs were used before switches were invented,\n 113 00:09:31,129 --> 00:09:35,850 frames to the correct destination, they simply\n 114 00:09:35,850 --> 00:09:42,330 But actually, before switches, there was another\n 115 00:09:42,330 --> 00:09:47,259 You don’t need to know about bridges for\n 116 00:09:47,259 --> 00:09:50,950 they’re like a transitional stage between\n 117 00:09:50,950 --> 00:09:55,820 However, the reason I’m telling you about\n 118 00:09:57,750 --> 00:10:02,590 However, when we use the term ‘bridge’,\nwe really mean ‘switch’. 119 00:10:02,590 --> 00:10:05,000 Bridges are not used in modern networks. 120 00:10:05,000 --> 00:10:10,639 So, in this lecture, and really any time I\n 121 00:10:10,639 --> 00:10:13,870 ‘bridge’, but really it means switch. 122 00:10:13,870 --> 00:10:21,220 So, if we look at this topology again, perhaps\n 123 00:10:21,220 --> 00:10:26,029 while this one interface on SW3 is in a blocking\n 124 00:10:29,149 --> 00:10:34,809 So effectively its like that link doesn’t\n 125 00:10:34,809 --> 00:10:40,719 If PC1 sends that same ARP request broadcast\n 126 00:10:41,820 --> 00:10:47,400 However, if at some point another interface\n 127 00:10:47,399 --> 00:10:51,819 The switches will automatically adjust the\n 128 00:10:51,820 --> 00:10:54,390 flooded like this, again no loops. 129 00:10:54,389 --> 00:10:58,799 So, that is just a basic outline of the purpose\n 130 00:10:58,799 --> 00:11:04,029 Now let’s go a little deeper into how spanning tree protocol 131 00:11:04,029 --> 00:11:09,740 By selecting which ports are forwarding and\n 132 00:11:09,740 --> 00:11:13,480 path to and from each point in the network. 133 00:11:16,070 --> 00:11:20,750 There is a set process that STP uses to determine\n 134 00:11:22,580 --> 00:11:25,670 That process is what we will cover next. 135 00:11:25,669 --> 00:11:33,039 STP-enabled switches send Hello BPDUs out\n 136 00:11:33,039 --> 00:11:39,809 seconds, so the switch will send a Hello BPDU\n 137 00:11:39,809 --> 00:11:45,299 If a switch receives a Hello BPDU on an interface,\n 138 00:11:45,299 --> 00:11:52,939 switch, because routers, PCs, etc. do not use STP,\n 139 00:11:52,940 --> 00:11:59,680 So, back to our topology here, these switches\n 140 00:11:59,679 --> 00:12:06,069 this . They use these BPDUs to advertise themselves\n 141 00:12:07,370 --> 00:12:11,929 Now, what exactly are these BPDUs used for? 142 00:12:11,929 --> 00:12:18,569 First of all, switches use one field in the\n 143 00:12:21,399 --> 00:12:25,039 The switch with the lowest Bridge ID becomes\nthe root bridge. 144 00:12:25,039 --> 00:12:29,559 I’ll talk about the bridge ID in the next\nslide. 145 00:12:29,559 --> 00:12:34,089 ALL ports on the root bridge are put in a\n 146 00:12:34,090 --> 00:12:37,509 topology must have a path to reach the root\nbridge. 147 00:12:37,509 --> 00:12:43,549 So, as I mentioned previously STP puts ports in either a blocking 148 00:12:43,549 --> 00:12:47,979 state, to avoid Layer 2 loops in the network. 149 00:12:47,980 --> 00:12:53,129 However, as I just said, on the root bridge, all ports are\n 150 00:12:53,129 --> 00:12:55,889 a path to reach the root bridge. 151 00:12:55,889 --> 00:13:02,620 Traditionally, the bridge ID field of the\n 152 00:13:02,620 --> 00:13:07,549 There is a bridge priority field, which is\n 153 00:13:07,549 --> 00:13:12,689 address of the switch, which as you already\n 154 00:13:12,690 --> 00:13:18,950 The default bridge priority is 32768 on all\n 155 00:13:21,730 --> 00:13:27,000 As I said before, the switch with the lowest\n 156 00:13:27,000 --> 00:13:33,210 by default the switch with the lowest MAC\n 157 00:13:33,210 --> 00:13:37,750 So here’s that topology once again, and I’ve\n 158 00:13:40,450 --> 00:13:45,920 As you know MAC addresses are 12 hexadecimal\n 159 00:13:45,919 --> 00:13:51,429 I’ve also added port lights for the interfaces,\n 160 00:13:51,429 --> 00:13:57,899 The G0/2 interface on each switch is connected\n 161 00:13:57,899 --> 00:14:03,959 BPDUs, it knows it is safe to go into forwarding\n 162 00:14:03,960 --> 00:14:06,519 so these port lights are all green. 163 00:14:06,720 --> 00:14:13,420 Now, all three switches have the default priority\n 164 00:14:13,419 --> 00:14:16,969 be the root bridge we will have to compare\nthe MAC addresses. 165 00:14:16,970 --> 00:14:20,730 Remember, the LOWEST bridge ID wins. 166 00:14:20,730 --> 00:14:23,539 Which of these MAC addresses is the lowest? 167 00:14:23,539 --> 00:14:32,480 Well, hexadecimal A is equal to 10, B is equal\n 168 00:14:34,049 --> 00:14:38,528 Therefore, SW1 will become the root bridge\nof this network. 169 00:14:38,528 --> 00:14:43,309 All ports on the root bridge become designated\n 170 00:14:43,309 --> 00:14:46,859 So, that is the traditional bridge ID. 171 00:14:46,860 --> 00:14:51,669 However, the bridge ID was actually updated\nto look like this. 172 00:14:51,669 --> 00:14:57,240 In reality, the bridge priority has been updated\n 173 00:14:57,240 --> 00:15:02,740 which is 4 bits, and the ‘extended system\n 174 00:15:02,740 --> 00:15:08,060 12 bits, because as you know a VLAN number\nis 12 bits in length. 175 00:15:08,059 --> 00:15:10,899 Why include a VLAN ID in the bridge priority? 176 00:15:10,899 --> 00:15:18,299 Well, Cisco switches use a version of STP\n 177 00:15:19,470 --> 00:15:26,269 PVST runs a separate STP ‘instance’ in\n 178 00:15:27,950 --> 00:15:35,060 One interface could be forwarding in VLAN1,\n 179 00:15:35,059 --> 00:15:40,278 By adding the VLAN ID into the bridge priority,\n 180 00:15:41,909 --> 00:15:45,990 Here’s a deeper look at the bridge priority\nfield. 181 00:15:45,990 --> 00:15:50,110 You may have wondered why 32768 is the default\nbridge priority. 182 00:15:50,110 --> 00:15:56,180 Well, it’s because this total field is 16 bits\n 183 00:15:57,860 --> 00:16:01,950 Therefore, the default bridge priority WAS\n32768. 184 00:16:01,950 --> 00:16:08,011 However, with the addition of the extended-system\n 185 00:16:10,100 --> 00:16:18,519 So, the default VLAN ID is 1, therefore the\n 186 00:16:20,879 --> 00:16:26,320 In the default VLAN of 1, the default bridge\n 187 00:16:28,840 --> 00:16:34,519 Now, here’s a question, If you want to increase\n 188 00:16:34,519 --> 00:16:40,220 VLAN numbers, what is the minimum unit of\nincrease/decrease? 189 00:16:40,220 --> 00:16:43,810 Let me explain what I mean in the next slide. 190 00:16:43,809 --> 00:16:49,799 The bridge priority + extended system ID is\n 191 00:16:49,799 --> 00:16:55,709 extended system ID is set and cannot be changed because it is 192 00:16:55,710 --> 00:17:01,100 Therefore, you can only change the total bridge\n 193 00:17:01,100 --> 00:17:09,818 system ID) in units of 4096, the value of\n 194 00:17:10,909 --> 00:17:14,619 Currently, the bridge priority here is 32769. 195 00:17:14,618 --> 00:17:19,958 Let’s reduce it to make this switch the\nroot bridge. 196 00:17:19,959 --> 00:17:31,610 If I want to reduce it just a little, I can\n 197 00:17:34,220 --> 00:17:40,589 I could reduce it more, of course, but the\n 198 00:17:40,589 --> 00:17:44,999 only be changed in units of 4096. 199 00:17:44,999 --> 00:17:50,440 So, the valid values you can configure are listed\n 200 00:17:53,210 --> 00:18:00,528 The extended system ID will then be added\n 201 00:18:00,528 --> 00:18:02,509 So let’s look at this topology again. 202 00:18:02,509 --> 00:18:08,789 We’ll just be looking at the STP topology\n 203 00:18:12,839 --> 00:18:19,869 But if there are multiple VLANs, say VLAN1,\n 204 00:18:19,869 --> 00:18:28,398 would be 32770 for VLAN2, and 32771 for VLAN3, etc. 205 00:18:28,398 --> 00:18:33,719 We could also change the bridge priority on\n 206 00:18:33,720 --> 00:18:41,048 SW1 is the root bridge in VLAN1, SW2 could be the\n 207 00:18:44,299 --> 00:18:50,079 I’ll talk about how you can do that in the next video,\n 208 00:18:50,089 --> 00:18:55,329 So, here in VLAN1, SW1 is the root bridge. 209 00:18:55,329 --> 00:18:59,849 All interfaces on the root bridge are designated\n 210 00:19:02,710 --> 00:19:06,079 Designated port is one of the port roles in\nspanning tree. 211 00:19:06,079 --> 00:19:07,699 There are a couple other port roles. 212 00:19:07,700 --> 00:19:11,140 I will introduce those in a minute. 213 00:19:11,140 --> 00:19:13,710 Okay just a few more points about the root\nbridge. 214 00:19:13,710 --> 00:19:17,990 When a switch is powered on, it assumes it\nis the root bridge. 215 00:19:17,990 --> 00:19:23,999 It will only give up its position if it receives\n 216 00:19:23,999 --> 00:19:28,440 a BPDU from a switch with a lower bridge ID. 217 00:19:28,440 --> 00:19:33,980 Once the topology has converged and all switches\n 218 00:19:36,048 --> 00:19:40,519 The reason all switches send BPDUs at first\n 219 00:19:42,368 --> 00:19:47,990 Other switches in the network will forward BPDUs from the root 220 00:19:51,679 --> 00:19:56,990 Before moving on, let’s see if you understand\n 221 00:19:56,990 --> 00:20:02,120 In this network of 4 switches, which will\n 222 00:20:02,119 --> 00:20:08,739 Pause the video now to think about the answer. 223 00:20:08,819 --> 00:20:11,460 Okay, did you find the root bridge? 224 00:20:14,589 --> 00:20:23,038 Both SW1 and SW3 have the same priority, 12289,\n 225 00:20:23,038 --> 00:20:33,450 The first half, 014A 38 is the same, but the\n 226 00:20:34,980 --> 00:20:40,200 Let’s do another practice question. 227 00:20:41,200 --> 00:20:44,490 Which switch will become the root bridge in\nthis case? 228 00:20:44,490 --> 00:20:50,880 Pause the video to think about your answer. 229 00:20:53,480 --> 00:20:57,579 It has the lowest priority of the 4 switches,\n4097. 230 00:21:01,308 --> 00:21:08,069 So far we have covered the first step of spanning-tree’s\n 231 00:21:08,069 --> 00:21:13,058 Step 1: the switch with the lowest bridge\n 232 00:21:13,058 --> 00:21:17,538 All ports on the root bridge are designated\n 233 00:21:17,538 --> 00:21:22,269 It’s important that this is the first step\n 234 00:21:22,269 --> 00:21:25,980 of the steps depend on knowing which switch\nis the root bridge. 235 00:21:30,038 --> 00:21:34,819 All other switches will select ONE of its\n 236 00:21:34,819 --> 00:21:39,730 So, that means there is one root port on each\n 237 00:21:41,440 --> 00:21:46,399 The interface with the lowest root cost will\nbe the root port. 238 00:21:46,398 --> 00:21:49,449 Root ports are also in a forwarding state. 239 00:21:49,450 --> 00:21:53,999 Now let’s talk about what that ‘root cost’\nis. 240 00:21:53,999 --> 00:21:57,038 Each interface has an associated spanning\ntree ‘cost’. 241 00:21:57,038 --> 00:22:03,960 A regular Ethernet interface, with a speed\n 242 00:22:03,960 --> 00:22:09,989 Fastethernet, 100 megabits per second, has\na cost of 19. 243 00:22:09,989 --> 00:22:15,269 Gigabit ethernet has a cost of 4, and 10 gigabit\n 244 00:22:15,269 --> 00:22:18,509 Make sure you remember these path costs for\nthe exam. 245 00:22:18,509 --> 00:22:22,378 Of course, there will be flashcards in the\n 246 00:22:23,798 --> 00:22:29,869 So, these are gigabit ethernet ports,\n 247 00:22:29,869 --> 00:22:36,428 The root cost is the total cost of the outgoing\n 248 00:22:36,429 --> 00:22:43,019 SW1 is the root bridge, so it has a cost of\n0 on all interfaces. 249 00:22:43,019 --> 00:22:47,599 They are gigabit ethernet interfaces, but\n 250 00:22:47,599 --> 00:22:50,769 interface, just the sending, the outgoing interface. 251 00:22:50,769 --> 00:22:57,829 So, SW1 advertises its root cost of 0 in its\nBPDUs. 252 00:22:57,829 --> 00:23:04,349 SW2 will receive the BPDU and add the cost\n 253 00:23:04,349 --> 00:23:08,808 4, when it floods those BPDUs out of its interfaces. 254 00:23:11,079 --> 00:23:16,230 So, which port do you think SW2 will choose\nas its root port? 255 00:23:17,940 --> 00:23:24,249 It was advertised a cost of 0 on its G0/1\n 256 00:23:24,249 --> 00:23:29,759 is 4, therefore the total root cost via G0/1\nis 4. 257 00:23:29,759 --> 00:23:34,499 It was advertised a cost of 4 on G0/0, from\nSW3. 258 00:23:34,499 --> 00:23:39,690 However its interface also has a cost of 4,\n 259 00:23:39,690 --> 00:23:45,058 So, it will select G0/1 as the root port. 260 00:23:45,058 --> 00:23:48,798 SW3’s logic follows the same process. 261 00:23:48,798 --> 00:23:58,048 It has a total cost of 4 via G0/0, and a total\n 262 00:24:00,558 --> 00:24:06,069 In this case, the ports directly across from\n 263 00:24:08,220 --> 00:24:14,749 However, keep in mind that the port connected\n 264 00:24:14,749 --> 00:24:19,159 Because the root port is the switch’s path\n 265 00:24:20,378 --> 00:24:25,248 Okay, so I’ve updated our spanning-tree\nsummary here. 266 00:24:25,249 --> 00:24:29,110 First, one switch is elected as the root bridge. 267 00:24:29,109 --> 00:24:32,349 All ports on the root bridge are designated\nports. 268 00:24:32,349 --> 00:24:36,769 There is only one step in selecting the root\n 269 00:24:38,128 --> 00:24:43,949 Next, each remaining switch will select ONE\n 270 00:24:43,950 --> 00:24:47,019 is also in a forwarding state. 271 00:24:47,019 --> 00:24:52,660 Ports across from, ports connected to, the root port are always 272 00:24:52,669 --> 00:24:57,639 The first criteria for root port selection\n 273 00:24:57,638 --> 00:25:02,538 However, what if a switch has multiple ports\n 274 00:25:02,538 --> 00:25:08,118 In that case, the interface connected to the\n 275 00:25:11,849 --> 00:25:15,819 Okay, let’s practice that with a\nquiz, actually. 276 00:25:15,819 --> 00:25:18,999 First, which switch will become the root bridge? 277 00:25:18,999 --> 00:25:27,048 Pause the video to think about the answer. 278 00:25:27,048 --> 00:25:31,398 Okay, the answer is SW2, because it has the lowest\npriority. 279 00:25:31,398 --> 00:25:34,469 So, SW2’s ports are all designated. 280 00:25:34,470 --> 00:25:38,019 Now, which ports will become root ports? 281 00:25:38,019 --> 00:25:42,769 All interfaces are gigabit ethernet, so all\nhave a cost of 4. 282 00:25:42,769 --> 00:25:48,058 Remember, if there is a tie in root cost,\n 283 00:25:48,058 --> 00:25:50,668 to the neighbor with the lowest bridge ID. 284 00:25:50,669 --> 00:25:56,070 So, pause the video here to think about your\n 285 00:26:04,250 --> 00:26:13,130 Okay, on SW1 and SW4, the answer is obvious, SW1’s\n 286 00:26:16,528 --> 00:26:22,109 Via G0/0 it has a cost of 8, 4 plus 4. 287 00:26:22,109 --> 00:26:26,248 Via G0/1 it has the same, a cost of 8, 4 plus\n4. 288 00:26:26,249 --> 00:26:34,210 So, we have to use the tiebreaker, which neighbor\n 289 00:26:34,210 --> 00:26:39,829 It’s SW1, the priorities are the same, but\n 290 00:26:39,829 --> 00:26:47,960 So, G0/0 is selected as the root port, and\n 291 00:26:47,960 --> 00:26:51,120 So, this is the process so far. 292 00:26:51,119 --> 00:26:56,879 HOWEVER, there is ONE more tiebreaker that\n 293 00:26:56,880 --> 00:27:01,650 What if two switches have two connections\n 294 00:27:01,650 --> 00:27:04,809 neighbor bridge ID are the same? 295 00:27:04,808 --> 00:27:09,908 Then we get to the final tie-breaker, the\n 296 00:27:09,909 --> 00:27:14,409 neighbor switch with the lowest port ID will\n 297 00:27:14,409 --> 00:27:17,860 Okay, let me briefly explain port ID. 298 00:27:17,859 --> 00:27:23,868 So, here is the output of the command SHOW\n 299 00:27:23,868 --> 00:27:27,209 in a future video when we look at spanning\ntree configuration. 300 00:27:27,210 --> 00:27:33,028 I just want to show you this section, this\n 301 00:27:35,019 --> 00:27:38,778 Notice the column title is Prio dot number. 302 00:27:38,778 --> 00:27:46,179 So, each port has a default priority of 128,\n 303 00:27:46,179 --> 00:27:50,009 2 for G0/1, etc on this switch. 304 00:27:50,009 --> 00:27:56,298 So, the STP port ID equals the port priority\n 305 00:27:56,298 --> 00:28:00,970 Similar to the bridge ID, where the MAC address\n 306 00:28:00,970 --> 00:28:06,028 tie, in this case the port number is used\n 307 00:28:06,028 --> 00:28:10,898 I won’t explain the port ID in more depth\n 308 00:28:10,898 --> 00:28:14,918 about it or change it, so you can just look\nat the port number. 309 00:28:14,919 --> 00:28:22,090 For example, G0/0 is lower than G1/0, or G0/3\n 310 00:28:22,089 --> 00:28:26,128 So, one more quiz to practice that. 311 00:28:26,128 --> 00:28:30,259 Now there are two connections between SW1\nand SW3. 312 00:28:30,259 --> 00:28:34,200 Which port will SW3 select as the root port? 313 00:28:34,200 --> 00:28:41,899 Pause the video to think about your answer. 314 00:28:41,898 --> 00:28:48,339 The answer is G0/2, because it is connected\n 315 00:28:51,440 --> 00:28:56,351 The NEIGHBOR switch’s port ID is used to\n 316 00:28:57,351 --> 00:29:04,110 That’s why G0/2 was selected over G0/0,\n 317 00:29:05,419 --> 00:29:12,340 So, SW1’s G0/1 interface is a designated\n 318 00:29:13,419 --> 00:29:16,460 Okay, so this is our process so far. 319 00:29:18,528 --> 00:29:23,009 We still haven’t blocked any ports, and\n 320 00:29:24,460 --> 00:29:28,759 So, let’s return to our previous topology. 321 00:29:28,759 --> 00:29:33,659 All that’s left is this connection between\nSW2 and SW3. 322 00:29:33,659 --> 00:29:39,470 So far, all of our ports are in a forwarding\n 323 00:29:39,470 --> 00:29:41,390 are always in a forwarding state. 324 00:29:41,390 --> 00:29:45,590 So, to prevent loops do we block both of these\nports? 325 00:29:49,788 --> 00:29:55,950 Actually no, here’s an important rule to\n 326 00:29:55,950 --> 00:29:58,480 spanning tree designated port. 327 00:29:58,480 --> 00:30:04,899 Remember, unlike old Ethernet hubs, which\n 328 00:30:04,898 --> 00:30:08,058 each link is a separate collision domain. 329 00:30:08,058 --> 00:30:15,220 This collision domain between SW1 and SW2\n 330 00:30:15,220 --> 00:30:20,730 This connection between SW1 and SW3 has one,\nSW1’s G0/1. 331 00:30:20,730 --> 00:30:25,190 And the connections with the PCs are all designated\n 332 00:30:25,190 --> 00:30:28,009 PCs don’t participate in spanning tree. 333 00:30:28,009 --> 00:30:34,149 So, we need one designated port on the connection\n 334 00:30:34,148 --> 00:30:38,998 How do we determine which port will be designated,\n 335 00:30:38,999 --> 00:30:43,200 The switch with the lowest root cost will\n 336 00:30:43,200 --> 00:30:51,109 However, in this case both switches have the\n 337 00:30:51,108 --> 00:30:54,808 and 4 for SW3 via its G0/0 interface. 338 00:30:54,808 --> 00:30:59,069 So, for the tie-breaker we compare the bridge\nID. 339 00:30:59,069 --> 00:31:06,079 SW2 has the lower bridge ID, so its G0/0 interface\n 340 00:31:06,079 --> 00:31:11,569 Finally, the other switch will make its port\n 341 00:31:13,038 --> 00:31:19,970 So SW3’s G0/1 is non-designated, it blocks\n 342 00:31:19,970 --> 00:31:24,278 So, here is the process for selecting the\n 343 00:31:25,989 --> 00:31:30,479 One switch is selected as the root bridge,\n 344 00:31:30,479 --> 00:31:36,919 Then, each remaining switch selects ONE of\n 345 00:31:36,919 --> 00:31:42,049 The interface with the lowest root cost is\n 346 00:31:42,048 --> 00:31:46,210 connecting to a neighboring switch with the\n 347 00:31:46,210 --> 00:31:53,379 a tie also, the interface connected to the\n 348 00:31:53,378 --> 00:31:58,638 Then finally, each remaining collision domain\n 349 00:31:58,638 --> 00:32:02,998 port, and the other port will be non-designated. 350 00:32:02,999 --> 00:32:06,798 The interface on the switch with the lowest\n 351 00:32:06,798 --> 00:32:12,408 a tie the interface on the switch with the\n 352 00:32:12,409 --> 00:32:18,509 the other interface will be a non-designated\n 353 00:32:18,509 --> 00:32:22,608 There are still many important things left\n 354 00:32:22,608 --> 00:32:27,069 cover those in part 2, before moving on to\n 355 00:32:29,200 --> 00:32:33,259 We already did a few quiz questions throughout\n 356 00:32:33,259 --> 00:32:36,639 questions to make sure you know the whole\nprocess. 357 00:32:36,638 --> 00:32:42,439 If you get stuck, if you don't know the answer, go back to the 358 00:32:42,440 --> 00:32:45,538 try to figure out the answers yourself. 359 00:32:45,538 --> 00:32:50,858 I will also feature one question from Boson\n 360 00:32:52,868 --> 00:32:56,878 Because there are still some important points\n 361 00:32:56,878 --> 00:33:00,638 aren’t ready to answer the spanning tree\n 362 00:33:00,638 --> 00:33:06,058 So, I will show you one question from Boson\n 363 00:33:07,628 --> 00:33:11,488 Of course, if you have already studied spanning\n 364 00:33:12,759 --> 00:33:18,419 Okay, let’s do a couple more practice questions\nfirst. 365 00:33:20,269 --> 00:33:25,579 Identify the root bridge, and the role of\n 366 00:33:25,579 --> 00:33:31,288 so which interfaces are root ports, which\n 367 00:33:32,380 --> 00:33:39,920 Pause the video to think about your answer. 368 00:33:40,000 --> 00:33:42,579 Okay, I hope you found the answer. 369 00:33:42,589 --> 00:33:50,558 So, the root bridge is SW3, because the priority\n 370 00:33:50,558 --> 00:33:56,028 These are the root ports, SW2 selected its\n 371 00:33:56,028 --> 00:34:00,378 the lower-number interface on SW1, G0/0. 372 00:34:00,378 --> 00:34:02,730 And these are the remaining connections. 373 00:34:02,730 --> 00:34:09,530 In each case the interface on SW2 is non-designated,\n 374 00:34:09,530 --> 00:34:13,550 Always remember to check that there is one\n 375 00:34:19,159 --> 00:34:22,019 Do the same thing, but with this network topology. 376 00:34:22,019 --> 00:34:27,719 Look carefully, some of these interfaces are\n 377 00:34:31,340 --> 00:34:38,100 Pause the video to think about your answer. 378 00:34:40,030 --> 00:34:44,780 SW4 is the root bridge because it has the\nlowest priority. 379 00:34:46,349 --> 00:34:53,009 SW1 uses its G0/1 interface as the root port,\n 380 00:34:53,010 --> 00:34:55,550 with a much higher spanning tree cost. 381 00:34:55,550 --> 00:35:00,080 Finally, the remaining designated and non-designated\nports. 382 00:35:00,079 --> 00:35:08,440 SW1’s F1/0 and F2/0 are non-designated because\n 383 00:35:08,440 --> 00:35:14,980 is non-designated because SW4 IS the root\n 384 00:35:14,980 --> 00:35:20,769 Okay, that’s all for the quiz, let’s take\na look at Boson ExSim. 385 00:35:20,769 --> 00:35:26,460 Okay for today's Boson ExSim practice question\n 386 00:35:26,460 --> 00:35:30,280 optional feature of spanning tree which I\n 387 00:35:30,280 --> 00:35:34,760 So, I won't give the answer in this video,\n 388 00:35:34,760 --> 00:35:38,260 give you the answer in the next lecture video,\nday 21. 389 00:35:38,260 --> 00:35:42,380 Now, if you think you know the answer, if\n 390 00:35:42,380 --> 00:35:45,559 feel free to let me know your answer in the\ncomments. 391 00:35:45,559 --> 00:35:50,529 Or if you want to do some independent research\n 392 00:35:50,530 --> 00:35:54,970 tree portfast' and do some reading, and then\n 393 00:35:54,969 --> 00:35:57,439 know your answer in the comment section. 394 00:35:59,880 --> 00:36:04,539 You want to decrease the amount of time that\n 395 00:36:06,090 --> 00:36:12,289 Portfast is not configured on any of the switchports\n 396 00:36:12,289 --> 00:36:16,059 portfast default' command from global configuration\nmode. 397 00:36:16,059 --> 00:36:18,980 Which of the ports on Switch A will use portfast? 398 00:36:20,889 --> 00:36:25,750 So A says 'No ports, because portfast cannot\n 399 00:36:25,750 --> 00:36:34,070 B says 'All ports', C says 'All access ports',\n 400 00:36:34,070 --> 00:36:37,330 Okay so as I said, this time we won't check\nthe answer. 401 00:36:37,329 --> 00:36:41,059 Please wait for the next video to see the\n 402 00:36:41,059 --> 00:36:44,860 Of course, if you think you know the answer,\n 403 00:36:44,860 --> 00:36:48,840 If you want to get your own copy of ExSim,\n 404 00:36:48,840 --> 00:36:52,870 the real thing, please follow my link in the\nvideo description. 405 00:36:52,869 --> 00:36:58,400 These are by far the best practice exams out\nthere for the CCNA. 406 00:36:58,400 --> 00:37:01,559 There will be supplementary materials for\nthis video. 407 00:37:01,559 --> 00:37:05,309 There will be a review flashcard deck to use\n 408 00:37:05,309 --> 00:37:09,130 Download the deck from the link in the description. 409 00:37:09,130 --> 00:37:12,260 There will also be a packet tracer practice\nlab. 410 00:37:12,260 --> 00:37:16,580 Please be sure to watch the practice lab,\n 411 00:37:16,579 --> 00:37:22,840 process of figuring out a spanning tree topology,\n 412 00:37:22,840 --> 00:37:27,559 commands which I didn’t have the time to\nshow in this video. 413 00:37:27,559 --> 00:37:32,980 Before finishing today’s video I want to\n 414 00:37:32,980 --> 00:37:41,099 Thank you to Joyce, Marek, Samil, Velvijaykum,\n 415 00:37:41,099 --> 00:37:48,969 Boson Software, the creators of ExSim, Sidi,\n 416 00:37:51,579 --> 00:37:57,019 Sorry if I pronounced your name incorrectly,\n 417 00:37:57,019 --> 00:38:01,849 One of you is displaying as Channel failed\n 418 00:38:01,849 --> 00:38:04,809 and I’ll see if YouTube can fix it. 419 00:38:04,809 --> 00:38:10,409 This is the list of JCNP-level members at\n 420 00:38:10,409 --> 00:38:14,339 up recently and your name isn’t on here\n 421 00:38:19,219 --> 00:38:23,119 Please subscribe to the channel, like the\n 422 00:38:23,119 --> 00:38:26,469 with anyone else studying for the CCNA. 423 00:38:26,469 --> 00:38:29,349 If you want to leave a tip, check the links\nin the description. 424 00:38:29,349 --> 00:38:35,019 I'm also a Brave verified publisher and accept\n 35298

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.