All language subtitles for Free-CCNA-Dynamic-Routing-Day-24-CCNA-200-301-Complete-Course_en

af Afrikaans
sq Albanian
am Amharic
ar Arabic Download
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
ca Catalan
ceb Cebuano
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
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:01,030 --> 00:00:06,979 Welcome to Jeremy’s IT Lab. This is a free,\n 2 00:00:06,979 --> 00:00:12,070 these videos, please subscribe to follow along\n 3 00:00:12,070 --> 00:00:17,030 a comment, and share the video to help spread\n 4 00:00:18,800 --> 00:00:23,929 In this video we will return to Layer 3, after\n 5 00:00:23,929 --> 00:00:32,028 VLANs, DTP, VTP, Spanning Tree, and EtherChannel. This\n 6 00:00:32,029 --> 00:00:37,210 routing. ‘Dynamic routing’ is in contrast\n 7 00:00:37,210 --> 00:00:43,829 in Day 11 of this course. Static routing involves\n 8 00:00:43,829 --> 00:00:49,838 with the ‘IP ROUTE’ command. Dynamic routing,\n 9 00:00:49,838 --> 00:00:54,488 dynamic routing protocol on the router, and\n 10 00:00:54,488 --> 00:01:01,479 the best routes to destination networks. It’s\n 11 00:01:01,479 --> 00:01:06,399 If you add a new LAN, routers will automatically\n 12 00:01:06,400 --> 00:01:12,380 new destination network. If one path to a\n 13 00:01:12,379 --> 00:01:18,560 will automatically start using the next-best\n 14 00:01:18,560 --> 00:01:26,079 to cover a large portion of the exam topics\n 15 00:01:26,079 --> 00:01:32,048 of the CCNA exam, and we’re going to cover\n 16 00:01:32,049 --> 00:01:37,200 later. We’ve already covered some of the\n 17 00:01:37,200 --> 00:01:44,890 parts of 3.1, 3.2, and 3.3. My plan is to\n 18 00:01:44,890 --> 00:01:49,799 give a general overview of dynamic routing\n 19 00:01:49,799 --> 00:01:55,560 of two routing protocols, RIP and EIGRP, in\n 20 00:01:55,560 --> 00:02:00,539 days to cover OSPF, which is actually the\n 21 00:02:00,539 --> 00:02:06,989 the exam topics list, in 3.4. However, even\n 22 00:02:06,989 --> 00:02:11,150 still need a basic understanding of other\n 23 00:02:11,150 --> 00:02:14,900 able to compare and contrast them to OSPF. 24 00:02:14,900 --> 00:02:20,908 Here’s what we’ll cover in today’s video.\n 25 00:02:20,908 --> 00:02:25,489 routing protocols, to demonstrate how they\n 26 00:02:25,489 --> 00:02:30,989 over static routes. There are a few types\n 27 00:02:30,989 --> 00:02:37,580 them down. We will then take a brief look\n 28 00:02:37,580 --> 00:02:42,519 ‘metric’ is how it measure how ‘far’\n 29 00:02:42,519 --> 00:02:47,330 spanning tree protocol, and it’s used to\n 30 00:02:47,330 --> 00:02:52,269 Finally, we’ll talk about something called\n 31 00:02:52,269 --> 00:02:57,719 part of determining the best route to a destination.\n 32 00:02:57,719 --> 00:03:03,789 for a bonus question from Boson ExSim for\n 33 00:03:03,789 --> 00:03:09,469 and the ones I used when I studied for my\n 34 00:03:09,469 --> 00:03:13,090 follow the link in the description. 35 00:03:13,090 --> 00:03:17,158 Here is the network topology I’ll use for\n 36 00:03:17,158 --> 00:03:27,919 routers, R1, R2, R3, and R4, and there is\n 37 00:03:27,919 --> 00:03:33,208 be focusing mostly on R1’s perspective for\n 38 00:03:33,209 --> 00:03:38,158 or dynamic routing protocol, R1’s routing\n 39 00:03:38,158 --> 00:03:44,449 local routes which were automatically added\n 40 00:03:44,449 --> 00:03:49,269 Let me take a minute to clarify a few points\n 41 00:03:49,270 --> 00:03:59,719 here, 10.0.12.0/30 and 10.0.13.0/30, are examples\n 42 00:03:59,718 --> 00:04:07,609 a route to a network or subnet. In other words,\n 43 00:04:07,610 --> 00:04:14,420 For example, if we configure a static route\n 44 00:04:14,419 --> 00:04:21,639 also. It’s not a route to a single host,\n 45 00:04:21,639 --> 00:04:31,000 10.0.12.1/32 and 10.0.13.1/32, are examples\n 46 00:04:31,009 --> 00:04:38,149 a specific host, a single address, specified\n 47 00:04:38,149 --> 00:04:44,679 automatically added, and are host routes to the\n 48 00:04:44,680 --> 00:04:51,430 and G1/0 interfaces. To configure a static\n 49 00:04:51,430 --> 00:05:00,649 the host’s address, then 255.255.255.255,\n 50 00:05:00,649 --> 00:05:06,899 aside, so you understand those two terms.\n 51 00:05:06,899 --> 00:05:10,918 Instead of configuring static routes on each\n 52 00:05:10,918 --> 00:05:19,589 routing protocol on them. Then, R4 will ‘advertise’\n 53 00:05:19,589 --> 00:05:26,638 R2, saying ‘you can reach this network via\n 54 00:05:26,639 --> 00:05:34,099 It will then advertise the same thing to R1,\n 55 00:05:34,100 --> 00:05:40,820 via R2. R1 will add this route to its route\n 56 00:05:40,829 --> 00:05:48,990 you can see that R2 also advertised the 10.0.24.0/30\n 57 00:05:48,990 --> 00:05:55,240 added it to its route table. R1 will then\n 58 00:05:55,240 --> 00:06:04,389 can reach 192.168.4.0/24 via R1. It will also\n 59 00:06:04,389 --> 00:06:11,180 learned from R2, as well as the 10.0.12.0/30\n 60 00:06:11,180 --> 00:06:15,389 focusing on the one network for now. 61 00:06:15,389 --> 00:06:20,949 How about if there is an error and R4’s\n 62 00:06:20,949 --> 00:06:26,490 will automatically adapt and remove the route\n 63 00:06:26,490 --> 00:06:33,168 has removed the route. This will prevent R1\n 64 00:06:33,168 --> 00:06:38,098 What if the same situation happened when using\n 65 00:06:38,098 --> 00:06:43,978 on R1. It can send traffic to R4’s network\n 66 00:06:43,978 --> 00:06:49,620 failure on the link occurs? Because there\n 67 00:06:49,620 --> 00:06:55,569 is unaware that it can no longer reach the\n 68 00:06:55,569 --> 00:07:00,790 destined for that network, it will continue\n 69 00:07:00,790 --> 00:07:06,080 no longer reach the network. Okay, so that’s\n 70 00:07:06,079 --> 00:07:11,978 remove invalid routes. However, we really\n 71 00:07:11,978 --> 00:07:16,139 so instead of totally removing the destination\n 72 00:07:18,160 --> 00:07:25,830 So, I’ve added another connection between\n 73 00:07:25,829 --> 00:07:33,389 internal network. via R2, and via R3. Let’s\n 74 00:07:33,389 --> 00:07:40,069 has the route via R2 in its route table, as\n 75 00:07:40,069 --> 00:07:45,240 will happen if I disable R4’s G0/0 interface\n 76 00:07:45,240 --> 00:07:52,180 So, I did that, and now let’s check R1’s\n 77 00:07:52,180 --> 00:08:00,259 R2 was now automatically replaced with the\n 78 00:08:00,259 --> 00:08:07,360 lost the preferred route to 192.168.4.0, but\n 79 00:08:07,360 --> 00:08:13,560 may be wondering, why the route via R2 was\n 80 00:08:13,560 --> 00:08:18,939 because this connection here is a fastethernet\n 81 00:08:18,939 --> 00:08:22,939 already familiar with the spanning-tree concept\n 82 00:08:22,939 --> 00:08:28,370 the best path to the root bridge. Well, dynamic\n 83 00:08:28,370 --> 00:08:35,700 determine the best path to a destination.\n 84 00:08:35,700 --> 00:08:42,280 from both R2 and R3, however it determined\n 85 00:08:43,870 --> 00:08:49,200 Okay, so that’s a very quick introduction\n 86 00:08:49,200 --> 00:08:55,720 purpose. Here are a few key points. Routers\n 87 00:08:55,720 --> 00:08:59,860 information about their connected routes as\n 88 00:08:59,860 --> 00:09:06,580 devices. They form ‘adjacencies’ , also\n 89 00:09:06,580 --> 00:09:12,509 with adjacent routers to exchange this information.\n 90 00:09:12,509 --> 00:09:18,779 adjacencies with R2 and R3, its directly\n 91 00:09:18,779 --> 00:09:23,329 a destination are learned, the router determines\n 92 00:09:23,330 --> 00:09:28,400 routing table. It uses the ‘metric’ of\n 93 00:09:28,399 --> 00:09:33,850 the lower metric is superior. Just like in\n 94 00:09:33,850 --> 00:09:40,450 when determining the root port on a switch.\n 95 00:09:40,450 --> 00:09:45,530 Now lets talk about the different types of\n 96 00:09:45,529 --> 00:09:52,449 protocols can be divided into two main categories,\n 97 00:09:52,450 --> 00:09:59,230 and EGP, which stands for Exterior Gateway\n 98 00:09:59,230 --> 00:10:04,840 to share routes within a single autonomous\n 99 00:10:04,840 --> 00:10:12,379 for example a company. EGPs are used to share\n 100 00:10:12,379 --> 00:10:19,000 Maybe this diagram will make it easier to\n 101 00:10:19,000 --> 00:10:26,639 ISP B are each their own autonomous system,\n 102 00:10:26,639 --> 00:10:31,399 to exchange routing information. However,\n 103 00:10:31,399 --> 00:10:39,079 an EGP is used. The basic purpose of IGPs\n 104 00:10:39,080 --> 00:10:44,600 about routes to destinations. However they\n 105 00:10:44,600 --> 00:10:50,620 course, we will focus mostly on OSPF, which\n 106 00:10:50,620 --> 00:10:55,629 other IGPs and the one EGP that is in use\n 107 00:10:58,509 --> 00:11:03,179 Now let’s break down these categories further.\n 108 00:11:03,179 --> 00:11:10,759 Interior Gateway Protocols, IGPs, and Exterior\n 109 00:11:10,759 --> 00:11:15,960 further break these categories down by the\n 110 00:11:15,960 --> 00:11:22,629 used by each protocol to share route information\n 111 00:11:22,629 --> 00:11:28,279 There is only one type of EGP algorithm, Path\n 112 00:11:28,279 --> 00:11:34,990 EGP algorithm, but there is only one EGP that\n 113 00:11:34,990 --> 00:11:40,649 Border Gateway Protocol. Because it’s not\n 114 00:11:40,649 --> 00:11:45,519 about BGP. I will mention a few important\n 115 00:11:45,519 --> 00:11:51,100 need to know BGP for the CCNA. Just make sure\n 116 00:11:51,100 --> 00:11:56,860 share route information between autonomous\n 117 00:11:56,860 --> 00:12:02,200 that is used in modern networks. So, you also\n 118 00:12:02,200 --> 00:12:08,759 ‘Path Vector’ algorithm functions. Now,\n 119 00:12:08,759 --> 00:12:13,610 and link state. I’ll repeat, when I say\n 120 00:12:13,610 --> 00:12:19,629 protocol uses to share route information and\n 121 00:12:19,629 --> 00:12:24,610 All routing protocols have the same goal.\n 122 00:12:24,610 --> 00:12:30,289 and select the best route to each destination.\n 123 00:12:30,289 --> 00:12:37,349 for each routing protocol. There are two distance\n 124 00:12:37,350 --> 00:12:43,820 Protocol, and EIGRP, Enhanced Interior Gateway\n 125 00:12:43,820 --> 00:12:48,390 protocols in depth, although I will give you\n 126 00:12:48,389 --> 00:12:56,600 compare and contrast them with OSPF. So, RIP\n 127 00:12:56,600 --> 00:13:04,190 There are also two link state protocols. OSPF,\n 128 00:13:04,190 --> 00:13:11,190 System to Intermediate System. Like BGP, I\n 129 00:13:11,190 --> 00:13:16,790 to learn more about IS-IS, consider looking\n 130 00:13:16,789 --> 00:13:24,120 the CCNA. OSPF, however, I will spend plenty\n 131 00:13:24,120 --> 00:13:28,669 For now, what I want you to remember is, first\n 132 00:13:28,669 --> 00:13:35,670 protocols. Then remember which protocols use\n 133 00:13:35,671 --> 00:13:42,540 a distance vector algorithm, OSPF and IS-IS\n 134 00:13:42,539 --> 00:13:48,759 path vector algorithm. The flashcards I provide\n 135 00:13:48,759 --> 00:13:53,559 want to outline the characteristics of distance\n 136 00:13:53,559 --> 00:13:58,639 I’ll start with distance vector routing\n 137 00:13:58,639 --> 00:14:04,799 protocols we will learn about are RIP and\n 138 00:14:04,799 --> 00:14:11,459 before link state protocols, in the early\n 139 00:14:11,460 --> 00:14:20,330 are RIP and Cisco’s proprietary protocol\n 140 00:14:20,330 --> 00:14:24,040 Distance vector protocols operate by sending\n 141 00:14:24,039 --> 00:14:29,370 connected neighbors. their known destination\n 142 00:14:29,370 --> 00:14:34,539 known destination networks. This method of\n 143 00:14:34,539 --> 00:14:39,789 ‘routing by rumor’. Why the name? It’s\n 144 00:14:39,789 --> 00:14:45,509 network beyond its neighbors. It only knows\n 145 00:14:45,509 --> 00:14:49,179 This is different than link state routing\n 146 00:14:49,179 --> 00:14:54,289 more complete picture of the network. When\n 147 00:14:54,289 --> 00:14:58,721 hand, all the router knows is the routes its\n 148 00:14:58,721 --> 00:15:04,440 to reach those destinations. The reason for\n 149 00:15:04,440 --> 00:15:08,720 the routers only learn the ‘distance’,\n 150 00:15:08,720 --> 00:15:14,720 which is the direction to send the traffic, the\n 151 00:15:14,720 --> 00:15:18,950 distance vector protocols work by sharing\n 152 00:15:20,320 --> 00:15:27,920 So, the example I showed you before of R4\n 153 00:15:27,919 --> 00:15:34,049 example of distance vector logic. R4 tells\n 154 00:15:34,049 --> 00:15:41,379 can reach 192.168.4.0/24 via me. My metric\n 155 00:15:41,379 --> 00:15:45,769 metric numbers yet, each routing protocol\n 156 00:15:45,769 --> 00:15:52,049 cover those soon. Anyway, R2 doesn’t know\n 157 00:15:52,049 --> 00:16:01,500 via R4, and that R4’s metric is 1. Similarly,\n 158 00:16:01,500 --> 00:16:07,221 the metric as 2. Once again, R1 doesn’t\n 159 00:16:07,221 --> 00:16:13,899 it knows is that it can reach 192.168.4.0/24\n 160 00:16:13,899 --> 00:16:20,879 is 2. And of course, R1 advertises the network\n 161 00:16:20,879 --> 00:16:26,529 network. Once again, RIP and EIGRP are the\n 162 00:16:26,529 --> 00:16:31,409 are used, and we will talk more about them\nin day 25’s video. 163 00:16:31,409 --> 00:16:36,769 Next I’ll briefly introduce link state routing\n 164 00:16:36,769 --> 00:16:42,100 protocol, every router creates a ‘connectivity\n 165 00:16:42,100 --> 00:16:48,670 same on each router. To allow this, each router\n 166 00:16:48,669 --> 00:16:53,569 its connected networks, to its neighbors.\n 167 00:16:53,570 --> 00:16:58,760 routers, until all routers in the network\n 168 00:16:58,759 --> 00:17:03,450 each router independently uses this map to\n 169 00:17:03,450 --> 00:17:07,539 I think you can see how this is different\n 170 00:17:07,539 --> 00:17:13,220 vector protocols. In link state protocols,\n 171 00:17:13,220 --> 00:17:19,120 so that it can calculate the best routes.\n 172 00:17:19,119 --> 00:17:24,350 CPU power and memory, on the router, because\n 173 00:17:24,351 --> 00:17:28,640 state protocols tend to be faster in reacting\n 174 00:17:28,640 --> 00:17:36,250 protocols. The two link state protocols in\n 175 00:17:36,250 --> 00:17:43,160 mention some things about IS-IS, but as for\n 176 00:17:43,160 --> 00:17:47,300 Now let’s talk about those metrics that\n 177 00:17:47,299 --> 00:17:52,859 table contains the best route to each destination\n 178 00:17:52,859 --> 00:17:58,039 a dynamic routing protocol learns two different\n 179 00:17:58,039 --> 00:18:03,889 determine which is ‘best’? As I briefly\n 180 00:18:03,890 --> 00:18:09,480 of the routes to determine which is best.\n 181 00:18:09,480 --> 00:18:15,150 like the root cost in spanning tree. A lower\n 182 00:18:15,150 --> 00:18:21,340 with the lowest root cost will become the\n 183 00:18:21,339 --> 00:18:25,530 the route with the lowest metric is considered\n 184 00:18:25,530 --> 00:18:32,919 table. Each routing protocol uses a different\n 185 00:18:32,920 --> 00:18:40,571 Here in this slide I showed you before, although\n 186 00:18:40,570 --> 00:18:48,230 via R2 and one via R3, only the route via\n 187 00:18:48,230 --> 00:18:53,360 connection here has a higher metric cost than\n 188 00:18:53,359 --> 00:18:59,149 this route is less favorable. Now, you might\n 189 00:18:59,150 --> 00:19:04,009 ethernet connection? Both routes would have\n 190 00:19:04,009 --> 00:19:07,029 to the route table? Let’s see what happens. 191 00:19:07,029 --> 00:19:12,131 I changed the connection between R3 and R4\n 192 00:19:12,131 --> 00:19:19,800 others. Let’s check out R1’s route table.\n 193 00:19:19,799 --> 00:19:28,879 via 10.0.13.2, which is R3, and via 10.0.12.2,\n 194 00:19:28,880 --> 00:19:34,860 more) routes via the same routing protocol\n 195 00:19:34,859 --> 00:19:40,630 both will be added to the routing table. Traffic\n 196 00:19:40,631 --> 00:19:46,570 that they must be exactly the same destination,\n 197 00:19:46,569 --> 00:19:52,109 Here’s a larger view. In this case both\n 198 00:19:52,109 --> 00:19:58,509 protocol OSPF, as indicated by the code O\n 199 00:19:58,509 --> 00:20:06,609 same destination, 192.168.4.0/24, and they\n 200 00:20:06,609 --> 00:20:12,389 itself is also displayed in this output. Where\n 201 00:20:12,390 --> 00:20:17,821 square brackets is the metric value of the\n 202 00:20:17,820 --> 00:20:24,309 both were added, and traffic will be load-balanced\n 203 00:20:24,309 --> 00:20:31,139 MultiPath, or ECMP, load-balancing. Make sure\n 204 00:20:31,140 --> 00:20:37,250 up often in these videos about dynamic routing\n 205 00:20:37,250 --> 00:20:42,150 side of the square brackets, this is another\n 206 00:20:42,150 --> 00:20:48,950 or AD, which I will talk about a few slides\n 207 00:20:48,950 --> 00:20:55,100 Don’t memorize that now, as I said I’ll\n 208 00:20:55,099 --> 00:21:01,069 Since I just showed you ECMP, equal cost multipath\n 209 00:21:01,069 --> 00:21:05,849 I just want to let you know that you can do\n 210 00:21:05,849 --> 00:21:13,589 OSPF on R1, and then configured two static\n 211 00:21:13,589 --> 00:21:19,490 via R3. Then, both are added to the routing\n 212 00:21:19,490 --> 00:21:25,279 both routes. Notice that both routes have\n 213 00:21:25,279 --> 00:21:31,819 use the concept of ‘metric’ so you’ll\n 214 00:21:31,819 --> 00:21:37,650 distance, AD, value of static routes is 1.\n 215 00:21:37,651 --> 00:21:42,390 a few slides. For now, let’s return back\nto the topic of metric. 216 00:21:42,390 --> 00:21:47,590 As I already mentioned, each routing protocol\n 217 00:21:47,589 --> 00:21:53,559 of these in more detail in later videos, but\n 218 00:21:53,559 --> 00:21:59,539 RIP uses by far the simplest metric, hop count.\n 219 00:21:59,539 --> 00:22:05,960 counts as one ‘hop’, and the total metric\n 220 00:22:05,960 --> 00:22:11,620 One big downside is that links of all speeds\n 221 00:22:11,619 --> 00:22:17,359 megabit per second ethernet link is one hop,\n 222 00:22:17,359 --> 00:22:24,889 So, this is a very primitive way of calculating\n 223 00:22:24,890 --> 00:22:29,830 the most complicated metric of the IGPs, which\n 224 00:22:29,829 --> 00:22:36,369 by default, however with configuration other\n 225 00:22:36,369 --> 00:22:40,699 to note is that only the bandwidth of the\n 226 00:22:40,700 --> 00:22:46,670 the metric, but the total delay values of\n 227 00:22:46,670 --> 00:22:51,440 value is a little misleading, since by default\n 228 00:22:51,440 --> 00:22:56,009 on its bandwidth. Anyway, I’ll talk more\n 229 00:22:56,009 --> 00:23:03,759 more depth on EIGRP. Next up is OSPF, its\n 230 00:23:03,759 --> 00:23:07,990 link is calculated based on the bandwidth,\n 231 00:23:07,990 --> 00:23:13,220 route make up the metric of the route. This\n 232 00:23:13,220 --> 00:23:18,940 but also clearly better than RIP’s which\n 233 00:23:18,940 --> 00:23:25,160 IS-IS also uses a metric called ‘cost’.\n 234 00:23:25,160 --> 00:23:32,540 calculated based on bandwidth. All links have\n 235 00:23:32,539 --> 00:23:38,649 it functions the same as RIP, being a simple\n 236 00:23:38,650 --> 00:23:42,990 talk about much, but these other three I will\n 237 00:23:42,990 --> 00:23:49,779 now just remember the basics. RIP uses hop\n 238 00:23:49,779 --> 00:23:56,420 and delay, and OSPF uses a cost based on bandwidth.\n 239 00:23:56,420 --> 00:24:01,860 same, to let the router select the best route\n 240 00:24:01,859 --> 00:24:05,449 To briefly demonstrate how the difference\n 241 00:24:05,450 --> 00:24:11,610 selects, let’s look at this diagram again\n 242 00:24:11,609 --> 00:24:20,099 to 192.168.4.0/24 to select for its route\n 243 00:24:20,099 --> 00:24:28,159 Via R2, the hop count is 2. One hop to R2,\n 244 00:24:28,160 --> 00:24:35,029 2. One hop to R3, one hop to R4, even though\n 245 00:24:35,029 --> 00:24:41,069 fastethernet connection. So, both routes will\n 246 00:24:41,069 --> 00:24:46,980 load balance traffic using both routes, even\n 247 00:24:46,980 --> 00:24:53,390 is used instead of RIP, which path will be\n 248 00:24:53,390 --> 00:24:59,160 take into account bandwidth. So, the slower\n 249 00:24:59,160 --> 00:25:05,200 a higher metric value, making it less favorable.\n 250 00:25:05,200 --> 00:25:11,660 route table, and R1 will send all traffic\n 251 00:25:11,660 --> 00:25:18,740 R2. RIP views both routes as equal, but OSPF\n 252 00:25:18,740 --> 00:25:23,549 metrics is the same, to let the router select\n 253 00:25:23,549 --> 00:25:28,480 routing protocols might make better decisions\nthan others. 254 00:25:28,480 --> 00:25:33,289 Now let’s talk about administrative distance,\n 255 00:25:33,289 --> 00:25:38,889 cases a company will only use a single IGP\n 256 00:25:38,890 --> 00:25:45,810 EIGRP if they only use Cisco equipment. However,\n 257 00:25:45,809 --> 00:25:50,039 example, if two companies connect their networks\n 258 00:25:50,039 --> 00:25:55,230 protocols might be in use. You might connect\n 259 00:25:55,230 --> 00:26:01,450 EIGRP. Metric, which I just showed you, is\n 260 00:26:01,450 --> 00:26:07,350 routing protocol. If a router learns two routes\n 261 00:26:07,349 --> 00:26:12,919 metric to choose which route is better. However,\n 262 00:26:12,920 --> 00:26:20,800 metrics, so they cannot be compared. For example,\n 263 00:26:20,799 --> 00:26:28,759 a metric of 30, while an EIGRP route to the\n 264 00:26:28,759 --> 00:26:33,308 Which route is better? Which route should\n 265 00:26:33,308 --> 00:26:38,549 really answer those questions by looking at\n 266 00:26:38,549 --> 00:26:44,879 different metrics. So, the administrative\n 267 00:26:44,880 --> 00:26:50,400 routing protocol is preferred. A lower AD\n 268 00:26:50,400 --> 00:26:55,650 protocol is considered more ‘trustworthy’,\n 269 00:26:55,650 --> 00:27:00,269 As you saw before, RIP’s hop count-based\n 270 00:27:00,269 --> 00:27:05,549 a high AD, because it’s not as trustworthy.\n 271 00:27:05,549 --> 00:27:12,419 they have the same hop count, although really\n 272 00:27:12,420 --> 00:27:17,200 Ready for some memorization? These are the\n 273 00:27:17,200 --> 00:27:22,990 of routes. I HIGHLY recommend you use the\n 274 00:27:22,990 --> 00:27:29,000 if you don’t get a question on the exam\n 275 00:27:29,000 --> 00:27:35,269 are learned, one from OSPF and one from EIGRP.\n 276 00:27:35,269 --> 00:27:41,940 To answer that question, you would need to\n 277 00:27:41,940 --> 00:27:47,049 route is preferred and will be entered in\n 278 00:27:47,049 --> 00:27:52,069 is preferred, and will be selected over a\n 279 00:27:52,069 --> 00:27:58,389 values used on Cisco devices, other vendors\n 280 00:27:58,390 --> 00:28:04,860 preferred routes are those to directly connected\n 281 00:28:04,859 --> 00:28:12,259 are the next best, they have an AD of 1. Next\n 282 00:28:12,259 --> 00:28:20,059 with an AD of 20. There is another kind of\n 283 00:28:20,059 --> 00:28:27,700 later. EIGRP routes have an AD of 90. Next\n 284 00:28:27,700 --> 00:28:38,759 an AD of 100. OSPF has an AD of 110. IS-IS\n 285 00:28:38,759 --> 00:28:46,690 So, of the IGPs I showed you, which are RIP,\n 286 00:28:46,690 --> 00:28:55,019 preferred, it has the lowest AD. However,\n 287 00:28:55,019 --> 00:29:00,259 These are beyond the scope of the CCNA, but\n 288 00:29:00,259 --> 00:29:08,279 the EIGRP network, that are then advertised\n 289 00:29:08,289 --> 00:29:15,928 AD of 200. Then one more. Routes with an AD\n 290 00:29:15,929 --> 00:29:22,190 Cisco. If the administrative distance is 255,\n 291 00:29:22,190 --> 00:29:27,570 that route and does not install the route\n 292 00:29:27,569 --> 00:29:32,019 these. If you’re not using the flashcards,\n 293 00:29:32,019 --> 00:29:37,730 this. Without flashcards it might be difficult\n 294 00:29:39,579 --> 00:29:45,329 Here’s a quick quiz question to demonstrate\n 295 00:29:45,329 --> 00:29:53,970 network 10.1.1.0/24 are learned. A route with\n 296 00:29:53,970 --> 00:30:00,750 with a metric of 5. A route with a next hop\n 297 00:30:00,750 --> 00:30:09,819 of 3. And a route with a next hop of 192.168.3.1,\n 298 00:30:09,819 --> 00:30:16,109 route to 10.1.1.0/24 will be added to the\n 299 00:30:16,109 --> 00:30:26,089 the answer. Okay, so the answer is the OSPF\n 300 00:30:26,089 --> 00:30:31,339 is used to compare routes learned from the\n 301 00:30:31,339 --> 00:30:37,419 metrics, AD is used to select the best route.\n 302 00:30:37,420 --> 00:30:42,610 over the RIP routes, because it has a lower\nAD. 303 00:30:42,609 --> 00:30:47,199 Looking back at the route table I showed you\n 304 00:30:47,200 --> 00:30:52,480 static routes. The connected and local routes\n 305 00:30:55,589 --> 00:31:02,039 And another look at this route table with\n 306 00:31:02,039 --> 00:31:06,339 Remember that the number on the left inside\n 307 00:31:09,869 --> 00:31:15,259 One final point before moving on to the quiz.\n 308 00:31:15,259 --> 00:31:20,250 and I will demonstrate this when we cover\n 309 00:31:20,250 --> 00:31:25,450 want OSPF routes to be preferred over EIGRP\n 310 00:31:25,450 --> 00:31:31,980 that. You can also change the AD of a static\n 311 00:31:31,980 --> 00:31:38,490 to configure a static route. IP ROUTE, followed\n 312 00:31:38,490 --> 00:31:44,460 the next hop address. However, I used the\n 313 00:31:44,460 --> 00:31:49,370 Here it says ‘distance metric’ for this\n 314 00:31:49,369 --> 00:31:53,599 but don’t confuse this for the metric we\n 315 00:31:54,599 --> 00:32:01,469 So, I configured the route with an AD of 100.\n 316 00:32:01,470 --> 00:32:07,589 can see that the AD is now 100, instead of\n 317 00:32:07,589 --> 00:32:10,509 why would you want to do this? 318 00:32:10,509 --> 00:32:15,109 By changing the AD of a static route, you\n 319 00:32:15,109 --> 00:32:20,079 by a dynamic routing protocol to the same\n 320 00:32:20,079 --> 00:32:24,799 the static route’s AD is higher than the\n 321 00:32:24,799 --> 00:32:30,079 route will still be preferred. This kind of\n 322 00:32:30,079 --> 00:32:35,019 route’. The route will be inactive, meaning\n 323 00:32:35,019 --> 00:32:40,299 the route learned by the dynamic routing protocol\n 324 00:32:40,299 --> 00:32:45,139 router stops advertising it for some reason,\n 325 00:32:45,140 --> 00:32:49,911 with a neighbor to be lost. You can see here\n 326 00:32:49,911 --> 00:32:55,200 exam topics list. Make sure to watch the lab\n 327 00:32:55,200 --> 00:32:57,798 to get practice configuring everything we\ncover. 328 00:32:57,798 --> 00:33:03,970 Okay, so let’s quickly review what we covered\n 329 00:33:03,970 --> 00:33:08,870 to dynamic routing protocols. They allow routers\n 330 00:33:08,869 --> 00:33:15,009 destinations without having to manually configure\n 331 00:33:15,009 --> 00:33:19,160 in large networks it’s not practical to\n 332 00:33:19,160 --> 00:33:24,610 configure thousands of different routes, which\n 333 00:33:24,609 --> 00:33:30,080 types of dynamic routing protocols. First,\n 334 00:33:30,080 --> 00:33:36,629 gateway protocols, used for routing within\n 335 00:33:36,630 --> 00:33:43,090 gateway protocols, used for routing between\n 336 00:33:43,089 --> 00:33:48,859 The only EGP in use these days is BGP. We\n 337 00:33:48,859 --> 00:33:55,490 kind of algorithm they use. There is one type\n 338 00:33:55,490 --> 00:34:02,599 there are two different kinds of IGP algorithms.\n 339 00:34:02,599 --> 00:34:09,929 link state, used by OSPF and IS-IS. Then we\n 340 00:34:09,929 --> 00:34:15,250 uses a different metric, which is a value\n 341 00:34:15,250 --> 00:34:21,000 within the same routing protocol. However,\n 342 00:34:21,000 --> 00:34:26,590 With administrative distance. Use the flashcards\n 343 00:34:26,590 --> 00:34:31,730 routing protocol, I’m sure you’ll need\n 344 00:34:31,730 --> 00:34:36,320 in this video, so I want to say that you shouldn’t\n 345 00:34:36,320 --> 00:34:42,720 completely yet. In the next video I will cover\n 346 00:34:42,719 --> 00:34:48,359 videos after that will cover OSPF. In those\n 347 00:34:48,360 --> 00:34:52,240 topics again, such as administrative distance\nand metric. 348 00:34:52,239 --> 00:34:58,000 Okay let’s move on to today’s quiz. At\n 349 00:34:58,000 --> 00:35:03,659 question from Boson ExSim, the best practice\n 350 00:35:03,659 --> 00:35:09,259 for the CCNA exam and you want to make sure\n 351 00:35:09,260 --> 00:35:13,619 my opinion, the single best thing you can\n 352 00:35:13,619 --> 00:35:17,000 Follow the link in the description to get\nBoson ExSIm. 353 00:35:17,000 --> 00:35:25,130 Here’s quiz question 1. R1 learns four routes\n 354 00:35:25,130 --> 00:35:33,559 protocols: RIP, EIGRP, OSPF, and IS-IS. Which\n 355 00:35:33,559 --> 00:35:42,989 A, the RIP route only. B, the EIGRP route\n 356 00:35:42,989 --> 00:35:51,659 route only. E, the RIP and EIGRP routes, because\n 357 00:35:51,659 --> 00:35:57,949 and IS-IS, because both are link state protocols.\n 358 00:35:57,949 --> 00:36:05,799 table. Pause the video to think about your\nanswer. 359 00:36:05,800 --> 00:36:14,000 The answer is B, only the EIGRP route will be added to the routing 360 00:36:14,010 --> 00:36:19,480 destination to add to the routing table, and\n 361 00:36:19,480 --> 00:36:24,809 the AD is used to determine which will be\n 362 00:36:24,809 --> 00:36:30,889 lowest AD of the four protocols, so only the\n 363 00:36:34,809 --> 00:36:40,420 Which type of routing protocol is also known\n 364 00:36:40,420 --> 00:36:53,220 B, path vector. C, distance vector. Or D,\n 365 00:36:53,219 --> 00:36:57,919 The answer is C, distance\n 366 00:36:57,920 --> 00:37:03,470 RIP and EIGRP operate by telling neighboring\n 367 00:37:03,469 --> 00:37:08,849 metrics to reach those networks, this is known\n 368 00:37:08,849 --> 00:37:14,710 because, when using a link state protocol\n 369 00:37:14,710 --> 00:37:18,909 a complete map of the network to calculate\n 370 00:37:18,909 --> 00:37:24,139 minimal information a router receives from\n 371 00:37:24,139 --> 00:37:30,170 B, path vector, is a type of EGP, exterior\n 372 00:37:30,170 --> 00:37:37,150 current CCNA, and operates differently than\n 373 00:37:37,150 --> 00:37:42,670 or IGP, is a category which includes both\n 374 00:37:42,670 --> 00:37:46,970 so it is incorrect. Let’s go to question\n3. 375 00:37:46,969 --> 00:37:59,059 R1 learns two routes to 172.16.0.0/16 via\n 376 00:37:59,059 --> 00:38:05,860 Both routes are 5 hops away. Which route/routes\n 377 00:38:05,860 --> 00:38:16,130 both routes. B, only the route via 10.0.0.1.\n 378 00:38:16,130 --> 00:38:26,780 route will be added because RIP’s AD value\n 379 00:38:26,780 --> 00:38:31,610 The answer is A, both routes\n 380 00:38:31,610 --> 00:38:39,360 are to the same destination, 172.16.0.0/16.\n 381 00:38:39,360 --> 00:38:44,900 RIP. And they have the same metric, 5. So,\n 382 00:38:44,900 --> 00:38:51,400 added to the routing table and R1 will load-balance\n 383 00:38:51,400 --> 00:38:59,809 D, if R1 also learned a route to 172.16.0.0/16\n 384 00:38:59,809 --> 00:39:05,639 this would be true, because RIP’s AD value\n 385 00:39:05,639 --> 00:39:12,059 However, there was no mention of another routing\n 386 00:39:12,059 --> 00:39:16,409 take a look at a bonus question from Boson\nExSim for CCNA. 387 00:39:16,409 --> 00:39:21,799 Okay, for today's Boson ExSim practice question\n 388 00:39:21,800 --> 00:39:26,900 it's a good question about route selection.\n 389 00:39:26,900 --> 00:39:31,840 IP ROUTE command on RouterA and receive the\n 390 00:39:31,840 --> 00:39:42,530 four routes, S R D O. S is a static route,\n 391 00:39:42,530 --> 00:39:49,430 That's right, its D, not E. And O is OSPF.\n 392 00:39:49,429 --> 00:39:54,589 All of them begin '10.20.0.0', but they have\n 393 00:39:54,590 --> 00:40:02,090 as different destinations. The static route\n 394 00:40:02,090 --> 00:40:09,079 same destination. So that's why, even though\n 395 00:40:09,079 --> 00:40:14,239 most preferred, all of the routes appear in\n 396 00:40:14,239 --> 00:40:21,429 So, RouterA receives a packet that is destined\n 397 00:40:21,429 --> 00:40:28,000 will RouterA use to send the packet? Select\n 398 00:40:28,000 --> 00:40:33,110 it has the highest administrative distance.\n 399 00:40:33,110 --> 00:40:38,309 with the longest prefix match. C, the static\n 400 00:40:38,309 --> 00:40:45,079 over dynamic routes. Or D, the EIGRP route\n 401 00:40:45,079 --> 00:40:55,889 Okay, pause the video here to think about\n 402 00:40:55,889 --> 00:41:03,608 So, in today's video I just talked about metric\n 403 00:41:03,608 --> 00:41:09,319 routes from multiple routing protocols to\n 404 00:41:09,320 --> 00:41:15,480 distance to select the route. But if you get\n 405 00:41:15,480 --> 00:41:20,679 you use the metric. However, these routes\n 406 00:41:20,679 --> 00:41:26,429 different destinations, as I just said, because\n 407 00:41:26,429 --> 00:41:32,779 AD and metric numbers are irrelevant. So,\n 408 00:41:32,780 --> 00:41:38,630 11's video about static routes? How does the\n 409 00:41:38,630 --> 00:41:43,869 destination matches multiple entries in the\n 410 00:41:43,869 --> 00:41:48,170 all of these entries, so it could use any\n 411 00:41:48,170 --> 00:41:54,720 most specific match. And 'most specific' means\n 412 00:41:54,719 --> 00:42:05,119 should use this OSPF route and send the packet\n 413 00:42:05,119 --> 00:42:10,670 So, I think B, 'the OSPF route because it\n 414 00:42:10,670 --> 00:42:17,610 is the correct answer. Let's check. And it\n 415 00:42:17,610 --> 00:42:21,450 explanation, here is Boson's explanation.\n 416 00:42:21,449 --> 00:42:27,039 is the great thing about Boson ExSim, is it\n 417 00:42:27,039 --> 00:42:33,900 why B is correct, but also why A, C, and D\n 418 00:42:33,900 --> 00:42:38,420 to some Cisco documentation, which is freely\n 419 00:42:38,420 --> 00:42:44,019 in Cisco routers'. Okay, so that was today's\n 420 00:42:44,019 --> 00:42:48,269 to get a copy of ExSim, please follow the\n 421 00:42:48,269 --> 00:42:53,349 exams I used when I studied for my CCNA and\n 422 00:42:53,349 --> 00:42:57,620 me pass all of my exams on the first try.\n 423 00:42:57,619 --> 00:43:03,599 ExSim, please follow the link in the video\ndescription. 424 00:43:03,599 --> 00:43:08,170 There are supplementary materials for this\n 425 00:43:08,170 --> 00:43:12,809 the software ‘Anki’. There will also be\n 426 00:43:12,809 --> 00:43:18,559 some hands-on practice. That will be in the\n 427 00:43:18,559 --> 00:43:22,400 the link in the description, and I’ll send\n 428 00:43:25,849 --> 00:43:30,650 Before finishing today’s video I want to\n 429 00:43:30,659 --> 00:43:37,299 you to John, funnydart, Joshua, Scott, Aleksa,\n 430 00:43:37,300 --> 00:43:43,940 Samil, Velvijaykum, C Mohd, Johan, Mark, Miguel,\n 431 00:43:43,949 --> 00:43:50,368 of ExSim, Sidi, Magrathea, Devin, Charlsetta,\n 432 00:43:50,369 --> 00:43:56,271 Sorry if I pronounced your name incorrectly,\n 433 00:43:56,271 --> 00:44:00,950 of you is still displaying as Channel failed\n 434 00:44:00,949 --> 00:44:06,089 and I’ll see if YouTube can fix it. This\n 435 00:44:06,090 --> 00:44:11,720 of recording by the way, June 13th 2020, if\n 436 00:44:11,719 --> 00:44:16,609 on here don’t worry, you’ll be in future\nvideos. 437 00:44:16,610 --> 00:44:21,490 Thank you for watching. Please subscribe to\n 438 00:44:21,489 --> 00:44:26,459 and share the video with anyone else studying\n 439 00:44:26,460 --> 00:44:32,179 check the links in the description. I'm also\n 440 00:44:32,179 --> 00:44:37,139 or Basic Attention Token, tips via the Brave\n 35950

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