WEBVTT 00:00:01.000 --> 00:00:05.080 Now we're going to dive into a discussion, a very short discussion, on 00:00:05.080 --> 00:00:10.560 dynamic routing overview. I don't want to waste too much time here because I'd 00:00:10.560 --> 00:00:14.320 really like to get into OSPF and cover everything we need to to get ourselves 00:00:14.320 --> 00:00:19.080 set up for our next session. But when it comes to routing, for example, we've seen 00:00:19.080 --> 00:00:22.559 that we have static routing already with the IP route command and we learned 00:00:22.559 --> 00:00:28.200 about that in CCNA. We cover it, not heavily, but we spent a lot of time on it 00:00:28.200 --> 00:00:33.200 there. And in dynamic routing, you've got your IGPs versus your EGPs. Your IGPs 00:00:33.200 --> 00:00:36.840 are dynamic routing protocols that you run within your autonomous system, 00:00:36.840 --> 00:00:40.639 whereas the EGPs you run between autonomous systems typically. And under 00:00:40.639 --> 00:00:44.279 IGPs, you get your distance vector like RIPv1, RIPv2. You got your link state, 00:00:44.279 --> 00:00:50.160 OSPF, ISIS. You get your advanced distance vector, EIGRP. And then under EGP, you've 00:00:50.160 --> 00:00:54.919 got BGP, your path vector routing protocol. So being able to, on the exam, 00:00:54.919 --> 00:00:59.160 understand this flow and understand the types of protocols and what they are by 00:00:59.160 --> 00:01:03.840 name, good thing to have. When it comes to the term autonomous system, what exactly 00:01:03.840 --> 00:01:07.360 does that mean? It means a collection of networks overseen by a single 00:01:07.360 --> 00:01:11.199 organization, essentially. So, for example, my company is an autonomous system, your 00:01:11.199 --> 00:01:14.800 company's autonomous system, Cisco's an autonomous system, Facebook's an 00:01:14.800 --> 00:01:18.879 autonomous system, etc., etc., etc. So everybody is an autonomous system. 00:01:18.879 --> 00:01:23.400 Regardless of whether you are officially autonomous system on the internet or not, 00:01:23.400 --> 00:01:26.440 think of it that way. So even your house could be considered an autonomous system, 00:01:26.440 --> 00:01:32.040 even though it's not like an official autonomous system with its own autonomous 00:01:32.040 --> 00:01:36.000 system number, it's still a collection of routers, one router under your control, 00:01:36.000 --> 00:01:39.000 when it's all said and done, typically. Maybe you've got two or three routers, 00:01:39.000 --> 00:01:44.519 depending on how your home's set up. But in the end, you think of it this way. 00:01:44.519 --> 00:01:47.800 An autonomous system is a collection of networks overseen by a single 00:01:47.800 --> 00:01:52.199 organization, and therefore I'm going to run an IGP inside my organization, 00:01:52.199 --> 00:01:59.080 like RIPv2, ISIS, EIGRP, OSPF. And then between myself and another organization, 00:01:59.080 --> 00:02:03.239 or between myself and my service provider, I'm going to run maybe something like BGP, 00:02:03.239 --> 00:02:09.559 which is an exterior gateway protocol. In addition, you run like BGP, for example, 00:02:09.559 --> 00:02:13.559 if you're connected up to an MPLS layer 3 VPN. But even nowadays, you might be using 00:02:13.559 --> 00:02:20.600 BGP inside of your data center. So BGP can be used for many, many different things. 00:02:23.080 --> 00:02:28.199 Not just connecting two different autonomous systems together. But for this course, 00:02:28.199 --> 00:02:35.000 for this exam, that's the extent of it when it comes to knowing what an EGP is for or BGP. 00:02:35.000 --> 00:02:38.279 For example, when we get to our BGP discussion, we'll be talking about eBGP. 00:02:38.279 --> 00:02:41.880 That's what the exam objective state. You're not going to be testing on IBGP or anything like that, 00:02:41.880 --> 00:02:47.080 just eBGP. So you connecting your autonomous system up to another autonomous system 00:02:47.639 --> 00:02:52.360 is what we cover in Encore. Here's a nice little chart I put together for you 00:02:53.320 --> 00:02:57.320 with the dynamic routing protocols lifted down the left-hand side. We've got RIBv2, EIGRP, 00:02:57.320 --> 00:03:02.039 OSPF, ISAS, BGP. And when you look at the types, you really only have two different types. You 00:03:02.039 --> 00:03:07.160 have distance vector and you have link state. That's really all you have. RIBv2 is a pure, 00:03:07.160 --> 00:03:13.000 pure, pure distance vector routing protocol. And then EIGRP is an advanced distance vector 00:03:13.000 --> 00:03:16.279 writing protocol. Essentially, it has its roots as a distance vector writing protocol, 00:03:16.279 --> 00:03:21.320 but there's a lot of advanced functionality with EIGRP that makes it a really great dynamic 00:03:21.320 --> 00:03:28.679 routing protocol to use inside of your autonomous system. OSPF, a link state routing protocol. ISAS, 00:03:28.679 --> 00:03:33.080 a link state routing protocol. And then when you look at BGP, it's a path vector routing protocol. 00:03:33.080 --> 00:03:39.240 So path vector, distance vector, right? And so it has its roots in distance vector, 00:03:39.240 --> 00:03:42.839 but it relies on things like attributes and paths and different things like that, 00:03:42.839 --> 00:03:46.119 ultimately making it a different type of distance vector routing protocol. But in the end, 00:03:46.119 --> 00:03:49.880 we really just have distance vector and we have a link state. And what it really boils down to, 00:03:49.880 --> 00:03:53.800 folks, is the difference between distance vector and link state really comes down to 00:03:53.800 --> 00:03:57.720 the information that is shared when it's in the grand scheme of things. So when you think about 00:03:57.720 --> 00:04:01.479 any type of vector-related routing protocol, so distance vector, advanced distance vector, 00:04:01.479 --> 00:04:07.240 path vector, think of it like having street signs. So every router is a street sign. So when you 00:04:07.240 --> 00:04:12.199 arrive at a router, there's a street sign pointing you in the direction and how far it is to get 00:04:12.199 --> 00:04:17.880 there. That's it. And then you move on and you keep going, meaning that routers only know 00:04:17.880 --> 00:04:24.040 essentially what they have learned from all their directly connected routers when you are a distance 00:04:24.040 --> 00:04:27.880 vector in nature. And you don't know anything beyond that, except something is out there 00:04:27.880 --> 00:04:33.559 somewhere. So if we leave this interface, we follow the sign, we'll eventually get there. 00:04:33.559 --> 00:04:38.519 It's like driving down the highway and you see a sign that says New York City, 97 miles. Okay, 00:04:38.519 --> 00:04:44.279 well, you know, if you just keep going, you'll get there in 97 miles. Now, maybe you'll have to 00:04:44.279 --> 00:04:47.880 ramp off, maybe you'll have to take a Y exit or something, but again, there'll be a sign at that 00:04:47.880 --> 00:04:51.160 point that tells you what to do, a sign that'll tell you what to do, a sign that'll tell you, 00:04:51.160 --> 00:04:54.440 that's what distance vector's like, path vector's like a distance vector, okay? 00:04:54.440 --> 00:04:59.640 Whereas link state, you learn from everybody in your environment. So you learn from everybody in 00:04:59.640 --> 00:05:04.519 your environment and you can build what's called a topological map. So something like OSPF and ISIS 00:05:04.600 --> 00:05:09.320 has a complete view of the environment. And so they can make their decision based on those 00:05:09.320 --> 00:05:12.760 complete views, whereas distance vector makes their decisions based on what? Based on what 00:05:12.760 --> 00:05:16.040 they've only learned from their directly connected neighbors, right? Now I'm saying 00:05:16.040 --> 00:05:20.440 one is better than the other, right? For example, EIGRP and OSPF are really great 00:05:20.440 --> 00:05:24.359 for inside of your autonomous systems. EIGRP is very flexible, it's very easy to implement. 00:05:25.880 --> 00:05:30.600 But OSPF is very scalable and it is much more difficult to implement and much more difficult 00:05:30.600 --> 00:05:34.359 to work with. But primarily what we see in enterprise environments are EIGRP and OSPF. 00:05:34.359 --> 00:05:38.760 So chat in folks, are you using EIGRP or are you using OSPF? 00:05:40.519 --> 00:05:44.359 Conrad says, I've heard distance vector being called routing by rumor. Yes, because as I said, 00:05:44.359 --> 00:05:48.440 you only learn from your directly connected neighbor. So your neighbor has learned information, 00:05:48.440 --> 00:05:51.239 they've made a decision based on that information, and then they share that 00:05:51.239 --> 00:05:55.399 information to another router. So I've learned based on rumor, that's all that means. I've 00:05:55.399 --> 00:06:00.040 learned based on rumor. I haven't learned from everybody, I've learned based on rumor, 00:06:00.040 --> 00:06:05.959 does that make sense, Conrad? So yeah, so I'm not going to know about everybody else, 00:06:05.959 --> 00:06:09.559 I'm not going to know the information directly from the source, I'm only learning it from the 00:06:09.559 --> 00:06:13.079 directly connected neighbor. So whatever they have learned, whatever they have decided, 00:06:13.079 --> 00:06:18.040 that's what they teach me. They teach me their decision. So it's like playing the old game of 00:06:18.040 --> 00:06:21.320 telephone as a kid, right? Somebody says something and then you got to repeat it, 00:06:21.320 --> 00:06:25.720 repeat it, repeat it, repeat it. If it gets messed up along the way, it could get pretty bad. 00:06:25.720 --> 00:06:29.399 Same idea with distance vector, routing by rumor. That's essentially what it boils down to. 00:06:31.079 --> 00:06:34.600 Right, so we have some people using EIGRP, we have some people using OSPF. 00:06:34.600 --> 00:06:40.679 So if you primarily use EIGRP and you've worked a lot with EIGRP, for the certification exam, 00:06:40.679 --> 00:06:44.279 it's going to be all about OSPF pretty much when it comes to configuration verification. So you'll 00:06:44.279 --> 00:06:49.399 have a pretty big learning curve ahead of you. But for those of you who have OSPF, then you have 00:06:50.279 --> 00:06:54.040 quite a bit of information under your belt that is going to help you with the certification exam. 00:06:54.040 --> 00:06:57.320 But regardless, I'm going to go from the beginning soup to dessert when it comes to 00:06:57.320 --> 00:07:01.880 OSPF configuration verification troubleshooting when we get to that discussion. So this chart 00:07:01.880 --> 00:07:05.079 may come in handy on the certification exam because if they ask you a simple question like 00:07:05.079 --> 00:07:09.000 which of the following protocols are distance vector, or maybe there's a drag and drop that 00:07:09.000 --> 00:07:13.160 says drag the following attributes to the following types of protocols, maybe you have to do that. 00:07:13.160 --> 00:07:17.720 Which ones are Cisco proprietary versus not? So EIGRP, Cisco proprietary, doesn't work on other 00:07:17.720 --> 00:07:22.920 Cisco equipment. Not technically true. And the reason why is because in 2011, Cisco made an RFC 00:07:22.920 --> 00:07:29.239 about EIGRP. And other vendors could implement EIGRP on their devices if they want to free of 00:07:29.239 --> 00:07:34.600 charge nowadays. But it's still Cisco proprietary, meaning Cisco controls it. And you must implement 00:07:34.600 --> 00:07:39.480 on your routers exactly as Cisco tells you in that RFC. We've talked about metric earlier today, 00:07:39.480 --> 00:07:44.359 memorizing that's not too bad for the certification exam, EGP versus IGP. And then of course, 00:07:44.359 --> 00:07:49.160 your administrative distances are really important to memorize for the exam. So earlier, somebody 00:07:49.160 --> 00:07:52.119 said, hey, should we memorize our administrative distance? Yeah. Memorize your administrative 00:07:52.119 --> 00:07:59.559 distance. Memorize your metrics. Memorize EGP versus IGP. Wow. That's not good. You see that 00:07:59.559 --> 00:08:06.200 flash? That was a camera issue. All right. Fingers crossed we get through class. 00:08:09.959 --> 00:08:14.519 Fingers crossed we get through class. All right. If not, we'll have to do it without 00:08:14.519 --> 00:08:21.640 camera. And we'll just do it with audio and slides. Now, I've also put this together for you. 00:08:21.640 --> 00:08:28.119 This is available in your exam crash that is in your campus environment. So you don't have to 00:08:30.040 --> 00:08:34.119 copy this page right now. You don't have to take a screenshot of it because I am in the way. 00:08:34.119 --> 00:08:39.479 But in your exam crash, you will find this page. But if you did want to take a screenshot, 00:08:39.479 --> 00:08:42.359 I'll just move out of the way right now. And for those of you watching a recorded video, 00:08:42.359 --> 00:08:47.080 you could pause it and take a screenshot if you want. But the goal here is for you to be able 00:08:47.080 --> 00:08:53.559 to compare and contrast. So the idea here, especially for this exam, is to be able to 00:08:53.559 --> 00:08:58.440 compare and contrast EIGRP and OSPF. This is something that is in the exam objectives. 00:08:59.239 --> 00:09:02.679 And it's quite possible you could get a drag and drop, a multiple choice question, anything like 00:09:02.679 --> 00:09:07.960 that. So you really have to take the time to make sure you know what's on here. That's why I put 00:09:07.960 --> 00:09:11.000 this together. And I'm not going to bore you. And I'm not going to walk you through this and hold 00:09:11.000 --> 00:09:16.200 your hand in regards to this. This is just like the fundamental behaviors and characteristics 00:09:16.200 --> 00:09:19.960 of OSPF and EIGRP. So when you look at something like summarization, 00:09:21.000 --> 00:09:27.159 you'll see that EIGRP supports autosummarization. But OSPF does not support autosummarization. 00:09:27.159 --> 00:09:32.280 So it may be something you need to know. It also shows that EIGRP, you can do summarization 00:09:32.280 --> 00:09:36.280 manually on any enabled interface you want. Whereas something like OSPF, you can only do 00:09:36.280 --> 00:09:40.520 summarization on ABRs and ASBRs. Know your administrative distances. They're listed there. 00:09:40.520 --> 00:09:45.400 Know that one's distance vector, one's link state. Know all of these different things. 00:09:46.119 --> 00:09:49.719 You are not going to be testing on configuration verification of EIGRP. You're not going to learn 00:09:49.719 --> 00:09:54.760 about EIGRP, which frustrates me to no end when it comes to the Encore course and certification exam. 00:09:56.280 --> 00:10:02.200 They are so focused on OSPF and they are now expecting you just to know some attributes 00:10:02.200 --> 00:10:06.359 of EIGRP. That's silly in my opinion. In my opinion, if you're going to go ahead and do 00:10:06.359 --> 00:10:11.239 EIGRP, you might as well teach everybody EIGRP from soup to dessert, just like you're doing for 00:10:11.239 --> 00:10:15.000 OSPF. But they're not doing that. They're not testing you on that. So what I've done here, 00:10:15.960 --> 00:10:19.640 if you know these attributes, you know these attributes. Anytime they ask you to compare and 00:10:19.640 --> 00:10:22.599 contrast EIGRP and OSPF in the exam, you're going to get the answer right. 00:10:24.039 --> 00:10:29.880 Are all of my slides up to date? They should be. Why are they not? Are they not? 00:10:31.000 --> 00:10:35.080 So when you talk about slides, I assume you're talking about, for example, these slides 00:10:35.880 --> 00:10:40.599 right here, the class slides. So I'm talking about here the exam crash. That's where you're 00:10:40.599 --> 00:10:49.880 going to find that one. So it's under the exam crash, download, and it should be near the beginning. 00:10:53.719 --> 00:10:57.559 No, did I take it out and put it back in the course? Oh my gosh, 00:10:57.559 --> 00:11:01.799 I think I took it out and put it in the course. All right. So, oops. 00:11:02.440 --> 00:11:08.599 What did I do there? Okay, yeah, I guess when I updated it and we updated it, we took it out of 00:11:08.599 --> 00:11:13.479 the exam crash. Okay, it's not in there anymore. All right, so cool. And if it's not in the slides, 00:11:13.479 --> 00:11:17.320 I assume you're saying it's not in the slides. So I'll get the slides updated to make sure 00:11:17.320 --> 00:11:22.119 they're in the slides. So let's check it out here. 00:11:22.119 --> 00:11:27.640 Okay, so it's not in the slides anymore. So I'll get the slides updated to make sure they're in the slides. 00:11:28.840 --> 00:11:30.440 So let's check it out here. 00:11:52.119 --> 00:12:00.840 Oh, there it is. It's right there. Yeah, so it is in there. 00:12:04.840 --> 00:12:09.159 All right, so what page was that? 344, if you want to know, folks, 344. 00:12:10.919 --> 00:12:13.080 All right, so yeah, I did move it out and I put in the slide deck. 00:12:17.080 --> 00:12:20.599 All right, if you're experiencing any buffering or latency, it's probably on your end. I 00:12:21.159 --> 00:12:24.679 I recommend you refresh your browser. That would be your best option. 00:12:24.679 --> 00:12:29.159 I'm not seeing any issues on my end and I'm not having any dropped packets or anything like that 00:12:29.159 --> 00:12:34.280 based on my counters and statistics. So everything looks good on my end. So maybe refresh your 00:12:34.280 --> 00:12:38.760 browser or anything like that. That might be what is causing your problem. Maybe your connection 00:12:38.760 --> 00:12:47.880 is just not good enough right now. All right. All right, so this is on you. Make sure you know 00:12:47.880 --> 00:12:52.280 this stuff, folks. All right. All right. So that is it for our dynamic routing protocol discussion 00:12:52.280 --> 00:12:56.679 or overview. Good information there just in case they ask you multiple choice question, 00:12:56.679 --> 00:12:59.320 compare, contrast, drag and drops, anything like that for the certification.