1 00:00:02,358 --> 00:00:05,275 (futuristic music) 2 00:00:09,005 --> 00:00:12,571 - So after all of this theory of OSPF we've been talking 3 00:00:12,571 --> 00:00:16,794 about, let's finally get around to configuring this thing. 4 00:00:16,794 --> 00:00:20,672 So let's talk about implementing OSPF. 5 00:00:20,672 --> 00:00:24,345 So the initial configuration of OSPF is pretty simple, 6 00:00:24,345 --> 00:00:27,422 few things I wanna call to your attention right here. 7 00:00:27,422 --> 00:00:30,042 So, you would start out by configuring 8 00:00:30,042 --> 00:00:34,004 at the global configuration level your command router, 9 00:00:34,004 --> 00:00:36,254 OSPF and then a process-id. 10 00:00:37,229 --> 00:00:39,626 Now I wanna make a distinct difference between 11 00:00:39,626 --> 00:00:43,501 a process-id and an autonomous system number. 12 00:00:43,501 --> 00:00:47,168 In EIGRP, at the global configuration level, 13 00:00:48,810 --> 00:00:50,560 come on, 14 00:00:52,009 --> 00:00:54,842 you typed router EIGRP, 15 00:01:00,814 --> 00:01:04,044 and then you had to put your autonomous system number 16 00:01:04,044 --> 00:01:04,961 right here. 17 00:01:06,486 --> 00:01:08,396 And whatever number you put there as your 18 00:01:08,396 --> 00:01:10,885 autonomous system number was very important 19 00:01:10,885 --> 00:01:14,186 because you had to match on all the routers. 20 00:01:14,186 --> 00:01:17,419 In EIGRP when a router sends out an EIGRP hello packet, 21 00:01:17,419 --> 00:01:19,861 it includes the autonomous system number 22 00:01:19,861 --> 00:01:22,319 as part of that hello packet 23 00:01:22,319 --> 00:01:24,478 and those things have to match. 24 00:01:24,478 --> 00:01:26,787 Well, in this particular case a process-id 25 00:01:26,787 --> 00:01:29,454 is not sent in any OSPF packets, 26 00:01:30,475 --> 00:01:33,619 it's simply a locally significant value. 27 00:01:33,619 --> 00:01:34,621 That's it. 28 00:01:34,621 --> 00:01:36,232 Now you might be wondering, Keith, what do you mean 29 00:01:36,232 --> 00:01:38,018 a locally significant value? 30 00:01:38,018 --> 00:01:40,473 When I use that term locally significant that means 31 00:01:40,473 --> 00:01:43,262 only this router, only this device, 32 00:01:43,262 --> 00:01:45,148 needs to be aware of that number, 33 00:01:45,148 --> 00:01:48,802 it's not shared with any other device. 34 00:01:48,802 --> 00:01:51,839 So, most of the time when people configure OSPF, 35 00:01:51,839 --> 00:01:55,020 they use process-id number one. 36 00:01:55,020 --> 00:01:56,978 You can use whatever you want. 37 00:01:56,978 --> 00:01:59,505 I mean, theoretically, on router one you could use 38 00:01:59,505 --> 00:02:02,147 process one, on router two you could use process two, 39 00:02:02,147 --> 00:02:04,166 on router 99 you could use process 99. 40 00:02:04,166 --> 00:02:08,513 It doesn't really matter, it does not have to match. 41 00:02:08,513 --> 00:02:10,245 The main thing to remember is, 42 00:02:10,245 --> 00:02:13,065 unless you have a real good reason for doing so, 43 00:02:13,065 --> 00:02:16,322 you should only have one process of OSPF 44 00:02:16,322 --> 00:02:19,239 running in your router and that's it. 45 00:02:19,239 --> 00:02:22,124 As an example, let me contrast that with EIGRP. 46 00:02:22,124 --> 00:02:26,730 Once again, with EIGRP, if I had a router right here, 47 00:02:26,730 --> 00:02:29,730 let's say this is router x, y and z. 48 00:02:35,404 --> 00:02:39,571 And let's say that y and z were part of company... 49 00:02:43,045 --> 00:02:44,128 Let's say yz, 50 00:02:46,726 --> 00:02:50,893 and then all of a sudden we acquire a new company. 51 00:02:52,404 --> 00:02:54,571 So this is an acquisition. 52 00:02:59,536 --> 00:03:03,703 And maybe we were already doing EIGRP in company yz, 53 00:03:08,076 --> 00:03:12,666 and previously we were using autonomous system number 200. 54 00:03:12,666 --> 00:03:15,088 So all the routers here were using 200. 55 00:03:15,088 --> 00:03:17,740 All of a sudden this new aquistion we have, well, 56 00:03:17,740 --> 00:03:20,528 they were also using EIGRP, but they were using 57 00:03:20,528 --> 00:03:22,861 autonomous system number 77. 58 00:03:24,575 --> 00:03:27,794 So, for the time being, router y actually has to have 59 00:03:27,794 --> 00:03:29,711 two instances of EIGRP. 60 00:03:31,332 --> 00:03:33,976 You have to type router EIGRP 200, 61 00:03:33,976 --> 00:03:36,262 and so that's how he can exchange routes with 62 00:03:36,262 --> 00:03:39,001 his own internal company and then also in router y, 63 00:03:39,001 --> 00:03:41,251 you'd have EIGRP 77. 64 00:03:42,397 --> 00:03:46,096 Totally different process that he can run with router x. 65 00:03:46,096 --> 00:03:48,698 Now those two processes will not share routes. 66 00:03:48,698 --> 00:03:51,218 They will be separate in router y. 67 00:03:51,218 --> 00:03:54,508 We would have to redistribute between the two processes 68 00:03:54,508 --> 00:03:57,369 tell one process sends his routes into the other, 69 00:03:57,369 --> 00:03:59,998 and the other process sends his routes back. 70 00:03:59,998 --> 00:04:02,775 That's something we'd have to do manually in router y, 71 00:04:02,775 --> 00:04:04,777 otherwise they will stay separate and unique, 72 00:04:04,777 --> 00:04:08,325 as if they were completely different routing protocols. 73 00:04:08,325 --> 00:04:11,059 So that's the only time when you would really need 74 00:04:11,059 --> 00:04:14,069 two instances of the same routing protocol, 75 00:04:14,069 --> 00:04:16,506 running in one router. 76 00:04:16,506 --> 00:04:18,894 Well that also holds true with OSPF. 77 00:04:18,894 --> 00:04:22,529 In OSPF you should only have to have a single process 78 00:04:22,529 --> 00:04:24,104 running in your router. 79 00:04:24,104 --> 00:04:26,282 Only if you're in a situation like this, 80 00:04:26,282 --> 00:04:29,136 would you possibly need more than one process, 81 00:04:29,136 --> 00:04:31,499 but at the CCNA level just think to yourself 82 00:04:31,499 --> 00:04:35,721 I'm only gonna type router OSPF some number and that's it, 83 00:04:35,721 --> 00:04:37,464 and I'm never gonna do that command again. 84 00:04:37,464 --> 00:04:40,271 I'm never gonna have to create another process. 85 00:04:40,271 --> 00:04:42,174 One process is enough. 86 00:04:42,174 --> 00:04:44,921 And then you use your network command. 87 00:04:44,921 --> 00:04:49,088 Now in EIGRP, you had the option of using a wildcard mask. 88 00:04:50,654 --> 00:04:53,399 In OSPF, it's not an option. 89 00:04:53,399 --> 00:04:55,902 In OSPF you have to include a wildcard mask 90 00:04:55,902 --> 00:04:59,704 after your prefix and then you also include the word 91 00:04:59,704 --> 00:05:02,204 area and then the area number. 92 00:05:03,247 --> 00:05:06,511 So as an example of that you might type network, 93 00:05:06,511 --> 00:05:10,594 I'm just gonna shorten it, 25.70.00, 94 00:05:13,637 --> 00:05:17,804 and then a wildcard mask that would be appropriate for that. 95 00:05:19,684 --> 00:05:22,196 And then I would tell my router okay any links 96 00:05:22,196 --> 00:05:26,083 that you have on yourself that begin with 25.70, 97 00:05:26,083 --> 00:05:29,416 those links are gonna be part of AREA 1. 98 00:05:32,034 --> 00:05:35,639 So that's an example of how you type the network command. 99 00:05:35,639 --> 00:05:38,734 Now the router will come up with a router-id by itself, 100 00:05:38,734 --> 00:05:41,072 but as you saw in the last video, 101 00:05:41,072 --> 00:05:43,111 where we talked about designated routers 102 00:05:43,111 --> 00:05:44,917 and backup designated routers, 103 00:05:44,917 --> 00:05:47,837 you might want to deterministically set the router-id 104 00:05:47,837 --> 00:05:52,038 so that you can influence which router will become the DR 105 00:05:52,038 --> 00:05:55,948 or the BDR, and remember, every segment that needs a DR 106 00:05:55,948 --> 00:05:57,466 is a unique segment. 107 00:05:57,466 --> 00:06:00,459 In other words, if I'm a router with two ethernet segments, 108 00:06:00,459 --> 00:06:02,845 on this segment, there's gonna be a DR, 109 00:06:02,845 --> 00:06:05,318 it might be me, might be somebody else, 110 00:06:05,318 --> 00:06:08,622 and on this segment right here, that's also ethernet, 111 00:06:08,622 --> 00:06:10,264 there's gonna be another DR. 112 00:06:10,264 --> 00:06:12,581 Might be me, might be somebody else, 113 00:06:12,581 --> 00:06:16,157 but every broadcast segment or non-broadcast multi-access 114 00:06:16,157 --> 00:06:18,574 segment needs a DR and a BDR. 115 00:06:24,082 --> 00:06:26,650 Along those same lines you could also influence 116 00:06:26,650 --> 00:06:29,631 the ip ospf priority on an interface. 117 00:06:29,631 --> 00:06:34,153 Remember the default priority of OSPF on an interface is.... 118 00:06:34,153 --> 00:06:36,830 One. The default is one. 119 00:06:36,830 --> 00:06:40,457 If you set the priority to zero, that actually means 120 00:06:40,457 --> 00:06:44,539 this router can never become a DR on that interface, 121 00:06:44,539 --> 00:06:47,706 it is disqualified from becoming a DR. 122 00:06:49,790 --> 00:06:51,910 Now like it says here, both the router-id 123 00:06:51,910 --> 00:06:54,189 and the priority, if you change them, 124 00:06:54,189 --> 00:06:57,402 you need to restart your OSPF process. 125 00:06:57,402 --> 00:07:01,232 It will not take those changes on the fly. 126 00:07:01,232 --> 00:07:03,868 And then here's some verification commands we can use 127 00:07:03,868 --> 00:07:05,981 to see what OSFP is doing. 128 00:07:05,981 --> 00:07:09,586 So let's actually do an example of this in the lab. 129 00:07:09,586 --> 00:07:12,321 So I'm gonna be using this typology right here, 130 00:07:12,321 --> 00:07:16,545 and the routers that you see with the light blue circles, 131 00:07:16,545 --> 00:07:20,231 router one, switch one, router two, switch three, 132 00:07:20,231 --> 00:07:23,063 and router four, they have already been pre-configured 133 00:07:23,063 --> 00:07:25,820 for OSPF so they're already up and running. 134 00:07:25,820 --> 00:07:28,316 And I'm just gonna configure OSFP from scratch 135 00:07:28,316 --> 00:07:30,899 on switch two and router three. 136 00:07:32,757 --> 00:07:34,633 Now before I do that, let's for example, 137 00:07:34,633 --> 00:07:36,503 let's go to router two and issue some 138 00:07:36,503 --> 00:07:39,557 verification commands to see what he looks like already. 139 00:07:39,557 --> 00:07:40,474 Router two. 140 00:07:42,836 --> 00:07:47,247 Okay, so what command would I type to see if this router 141 00:07:47,247 --> 00:07:51,414 has become fully adjacent with any other OSPF neighbors, 142 00:07:52,622 --> 00:07:54,730 or if he's learned of any OSPF neighbors 143 00:07:54,730 --> 00:07:57,756 in any other transitory state? 144 00:07:57,756 --> 00:08:01,173 Hopefully you said show ip ospf neighbor, 145 00:08:02,355 --> 00:08:06,188 and you can see he's got one neighbor 1.2.1.1, 146 00:08:08,405 --> 00:08:09,988 that is switch one. 147 00:08:11,071 --> 00:08:13,148 So remember, when switch one was coming up 148 00:08:13,148 --> 00:08:15,114 with his router-id, first this you said was 149 00:08:15,114 --> 00:08:16,724 do I have any loop backs? 150 00:08:16,724 --> 00:08:17,949 No, I don't. 151 00:08:17,949 --> 00:08:20,224 Okay, what interfaces do I have that are either 152 00:08:20,224 --> 00:08:22,677 up-up, up-down or down-down? 153 00:08:22,677 --> 00:08:24,697 These two right here. 154 00:08:24,697 --> 00:08:26,750 Of these two interfaces, which one has 155 00:08:26,750 --> 00:08:28,531 the highest ip address? 156 00:08:28,531 --> 00:08:30,597 That would be this, one two one 11. 157 00:08:30,597 --> 00:08:33,354 So switch one said I'm gonna create my OSPF router-id 158 00:08:33,354 --> 00:08:38,027 of 1.2.1.11 and that's what we can see right here. 159 00:08:38,027 --> 00:08:42,227 What do you think the router-id is gonna be of router one? 160 00:08:42,227 --> 00:08:43,986 It should be it's loop back, right? 161 00:08:43,986 --> 00:08:46,853 Because the very first this it's looked at is a loop back. 162 00:08:46,853 --> 00:08:50,406 So let's go to router one and take a look. 163 00:08:50,406 --> 00:08:52,515 Which is also gonna answer the question of 164 00:08:52,515 --> 00:08:55,027 when I'm on a local router, how can I tell 165 00:08:55,027 --> 00:08:56,710 what it's router-id is? 166 00:08:56,710 --> 00:09:00,130 You can just do the command show ip ospf. 167 00:09:00,130 --> 00:09:04,297 And right at the top it says here is my router-id. 168 00:09:07,424 --> 00:09:09,314 In this case, just like we thought, 169 00:09:09,314 --> 00:09:11,364 it's the loop back interface. 170 00:09:11,364 --> 00:09:14,620 So, show ip ospf shows you a lot of good stuff, 171 00:09:14,620 --> 00:09:16,660 as you can see right here. 172 00:09:16,660 --> 00:09:19,056 And once again, we can use our favorite command, 173 00:09:19,056 --> 00:09:22,852 show ip protocols, and that will give us some information 174 00:09:22,852 --> 00:09:26,954 about ospf, shows you what your locally sigificant 175 00:09:26,954 --> 00:09:31,173 process-id is, I just used the number one on all of mine. 176 00:09:31,173 --> 00:09:34,256 It shows you what neighbors you have, 177 00:09:36,052 --> 00:09:39,052 the administrative distance of ospf. 178 00:09:39,893 --> 00:09:43,202 Going back here once again, because router one, switch one 179 00:09:43,202 --> 00:09:46,154 and router two have already been pre-configured, 180 00:09:46,154 --> 00:09:48,925 router two should have learned about this loop back 181 00:09:48,925 --> 00:09:51,275 network one 11 one 11 one 11, 182 00:09:51,275 --> 00:09:54,772 and he should have learned about one one one zero, 183 00:09:54,772 --> 00:09:56,599 as ospf routes. 184 00:09:56,599 --> 00:09:59,524 So let's take a look in his OSFP routing table, 185 00:09:59,524 --> 00:10:01,941 of router two, show ip route. 186 00:10:05,796 --> 00:10:08,297 And there we can see, there's that loop back network 187 00:10:08,297 --> 00:10:10,464 that was learned via OSPF, 188 00:10:11,355 --> 00:10:15,371 and here's that other network that was learned via OSPF. 189 00:10:15,371 --> 00:10:18,547 And notice when a route is prefaced with just the letter O, 190 00:10:18,547 --> 00:10:22,464 that means that it is an OSPF intra-area route. 191 00:10:25,619 --> 00:10:27,165 What does that mean? 192 00:10:27,165 --> 00:10:30,289 That means that this route actually lives in the same area 193 00:10:30,289 --> 00:10:33,132 where this local router is. 194 00:10:33,132 --> 00:10:34,818 In other words, router two says 195 00:10:34,818 --> 00:10:37,779 okay the one 11 one 11 one 11 and the one one one, 196 00:10:37,779 --> 00:10:41,985 they both reside in area one, and I live in area one. 197 00:10:41,985 --> 00:10:44,568 So that is an intra-area route. 198 00:10:47,541 --> 00:10:51,600 Now let's go ahead and configure switch two for OSPF. 199 00:10:51,600 --> 00:10:53,929 And if you haven't already taken a screenshot of this, 200 00:10:53,929 --> 00:10:57,776 I would recommend that you do so, so you can follow along. 201 00:10:57,776 --> 00:11:00,362 So in switch two what I'm gonna do is I'm gonna have 202 00:11:00,362 --> 00:11:04,042 three network statements, I'm gonna configure OSPF 203 00:11:04,042 --> 00:11:07,403 then I'm gonna put the two two two network into area 1, 204 00:11:07,403 --> 00:11:10,790 I'm gonna put the two three two network into area 0, 205 00:11:10,790 --> 00:11:13,391 and I'm gonna put the three two three network 206 00:11:13,391 --> 00:11:16,634 also into area 0, so my configuration will consist 207 00:11:16,634 --> 00:11:18,694 of a total of four commands. 208 00:11:18,694 --> 00:11:23,209 Router OSPF one, followed by three network statements, 209 00:11:23,209 --> 00:11:26,792 and that will be all I need for switch two, 210 00:11:30,176 --> 00:11:32,209 router ospf and you can see here 211 00:11:32,209 --> 00:11:34,642 my process-id, locally significant value, 212 00:11:34,642 --> 00:11:37,584 you've got quite a range of values you can choose from, 213 00:11:37,584 --> 00:11:39,984 most people usually just start with one. 214 00:11:39,984 --> 00:11:44,428 Now I'm gonna say network 2.2.2.0, with the appropriate 215 00:11:44,428 --> 00:11:48,178 wildcard mask, and that's gonna be in area 1, 216 00:11:49,703 --> 00:11:53,203 network 2.3.2.0 that's gonna be in area 0, 217 00:11:56,679 --> 00:11:58,964 so right there, the fact that I have put 218 00:11:58,964 --> 00:12:03,419 one link in area 1 and one or more links in area 0, 219 00:12:03,419 --> 00:12:07,466 means this router is now an area border router. 220 00:12:07,466 --> 00:12:10,383 And network 3.2.3.0 also in area 0. 221 00:12:14,854 --> 00:12:17,129 Now how could I tell that this router, 222 00:12:17,129 --> 00:12:20,192 now remember it's a switch, but it's a multi-layer switch, 223 00:12:20,192 --> 00:12:22,667 I've enabled it for routing so I'm just calling it 224 00:12:22,667 --> 00:12:27,458 a router, how do I know this device is running OSPF? 225 00:12:27,458 --> 00:12:30,785 Well, once again show ip protocols and if OSPF 226 00:12:30,785 --> 00:12:34,952 shows up here, which it does, I know it's running OSPF. 227 00:12:37,337 --> 00:12:40,165 It also says right here it is an area border router, 228 00:12:40,165 --> 00:12:43,695 so he knows that he's an area border router. 229 00:12:43,695 --> 00:12:46,151 And this shows me the various networks, 230 00:12:46,151 --> 00:12:50,318 where I've activated OSPF with the network command. 231 00:12:51,457 --> 00:12:54,811 So now I'll just go ahead and put my light blue circle 232 00:12:54,811 --> 00:12:59,533 on switch two, since I've just finished OSPF for him. 233 00:12:59,533 --> 00:13:04,079 So at this point, if we go into let's say router four, 234 00:13:04,079 --> 00:13:08,246 router four should now have at least a couple of networks 235 00:13:10,137 --> 00:13:13,230 that are OSPF intra-area routes. 236 00:13:13,230 --> 00:13:16,665 He should have learned about the two three two network, 237 00:13:16,665 --> 00:13:20,077 and he should have learned about the three two three network 238 00:13:20,077 --> 00:13:21,340 as intra-area routes. 239 00:13:21,340 --> 00:13:26,208 So these two routes should show up simply as O's in R4. 240 00:13:26,208 --> 00:13:28,577 And then R4 should also have learned about 241 00:13:28,577 --> 00:13:31,900 all these routes over here in area 1, 242 00:13:31,900 --> 00:13:34,464 and in R4's routing table, all of these will show up 243 00:13:34,464 --> 00:13:37,210 as O I A in the routing table, 244 00:13:37,210 --> 00:13:40,699 O I A standing for inter-area routes. 245 00:13:40,699 --> 00:13:43,342 Routes that originate in some other area 246 00:13:43,342 --> 00:13:45,881 that router four is not connected to. 247 00:13:45,881 --> 00:13:47,858 Let's take a look at router four, 248 00:13:47,858 --> 00:13:50,191 show ip route. 249 00:13:53,073 --> 00:13:57,663 And there we have it, here are the intra-area routes, 250 00:13:57,663 --> 00:14:00,250 that are part of his own area, 251 00:14:00,250 --> 00:14:04,177 and OSPF as a metric uses cost, it uses cost, 252 00:14:04,177 --> 00:14:06,444 which is based on interface bandwidth, 253 00:14:06,444 --> 00:14:08,516 just like the spanning tree protocol. 254 00:14:08,516 --> 00:14:10,508 The metric of OSPF is cost, it just uses 255 00:14:10,508 --> 00:14:13,733 a completely different formula but the higher the bandwidth, 256 00:14:13,733 --> 00:14:15,316 the lower the cost. 257 00:14:16,662 --> 00:14:20,098 And here we see inter-area routes, 258 00:14:20,098 --> 00:14:22,224 learned from a different area. 259 00:14:22,224 --> 00:14:24,390 And those have a slightly higher cost, 260 00:14:24,390 --> 00:14:28,192 'cause they're a little bit further away. 261 00:14:28,192 --> 00:14:32,094 And at this point I think one other thing I wanna show you, 262 00:14:32,094 --> 00:14:34,770 you can actually look at the database that contains 263 00:14:34,770 --> 00:14:38,020 your OSPF lsa's, show ip ospf database. 264 00:14:40,335 --> 00:14:43,492 And it show's you your different lsa's, now, 265 00:14:43,492 --> 00:14:47,304 at the CCNA level, like I said, you don't have to know 266 00:14:47,304 --> 00:14:50,306 about the specific kinds of lsa's, you don't have to know 267 00:14:50,306 --> 00:14:52,875 what their names and type numbers are, 268 00:14:52,875 --> 00:14:54,796 you don't even really need to be able to 269 00:14:54,796 --> 00:14:56,997 interpret the output of this command. 270 00:14:56,997 --> 00:14:59,787 I just wanted to show you that, it is available to you, 271 00:14:59,787 --> 00:15:02,628 and once you get to the CCNP level and you start learning 272 00:15:02,628 --> 00:15:04,786 about the details of lsa's then you'll start 273 00:15:04,786 --> 00:15:07,022 going into gory detail about the output of 274 00:15:07,022 --> 00:15:09,659 show ip ospf database and some various keywords 275 00:15:09,659 --> 00:15:11,271 that you can add to it. 276 00:15:11,271 --> 00:15:13,273 But I just wanted you to walk away from this video 277 00:15:13,273 --> 00:15:15,441 knowing that you can go into the database 278 00:15:15,441 --> 00:15:17,970 and see various things. 279 00:15:17,970 --> 00:15:21,990 And, other than that we have gone through 280 00:15:21,990 --> 00:15:26,532 all of these show commands here, oh, show ip ospf interface, 281 00:15:26,532 --> 00:15:29,280 we haven't taken a look at that one yet, 282 00:15:29,280 --> 00:15:31,197 show ip ospf interface. 283 00:15:35,920 --> 00:15:38,435 And you can see, it'll show you every interface 284 00:15:38,435 --> 00:15:41,477 that has been activated for OSPF, 285 00:15:41,477 --> 00:15:43,493 because of a network command. 286 00:15:43,493 --> 00:15:45,258 It shows you the interface, 287 00:15:45,258 --> 00:15:47,775 it shows you what kind of network it is, 288 00:15:47,775 --> 00:15:50,309 remember we talked about that in a previous section, 289 00:15:50,309 --> 00:15:52,391 this is the broadcast interface, 290 00:15:52,391 --> 00:15:54,604 it shows you the OSPF cost, remember, 291 00:15:54,604 --> 00:15:56,642 cost is based on bandwidth. 292 00:15:56,642 --> 00:15:59,583 If I went into the interface and I changed the bandwidth, 293 00:15:59,583 --> 00:16:02,316 that would affect the ospf cost value. 294 00:16:02,316 --> 00:16:05,975 So OSPF's metric is much simpler than EIGRP, 295 00:16:05,975 --> 00:16:08,643 EIGRP used all sorts of factors to come up with 296 00:16:08,643 --> 00:16:11,162 a complex metric called distance, 297 00:16:11,162 --> 00:16:13,692 OSPF doesn't do that, OSPF just factors bandwidth 298 00:16:13,692 --> 00:16:17,727 and that's it, and it comes up with a cost value. 299 00:16:17,727 --> 00:16:21,300 It also shows you on a link who the designated router is, 300 00:16:21,300 --> 00:16:23,097 so you can see that. 301 00:16:23,097 --> 00:16:25,475 You can see this particular device, router four 302 00:16:25,475 --> 00:16:28,200 is the backup designated router, 303 00:16:28,200 --> 00:16:30,831 and you can see your interface priority. 304 00:16:30,831 --> 00:16:35,392 A lot of good information from the output of this command. 305 00:16:35,392 --> 00:16:38,048 And for troubleshooting OSPF, 306 00:16:38,048 --> 00:16:42,215 probably one of the best debugs is debug ip ospf adjacency. 307 00:16:44,433 --> 00:16:46,839 That is a great debug to find out, you know, 308 00:16:46,839 --> 00:16:48,790 why do I not have a neighbor? 309 00:16:48,790 --> 00:16:50,866 If I'm looking at a topology diagram and I say, 310 00:16:50,866 --> 00:16:53,658 well, router one and router two should be neighbors 311 00:16:53,658 --> 00:16:56,434 with each other but, when I do show ip ospf neighbor, 312 00:16:56,434 --> 00:16:58,871 they're not seeing each other. 313 00:16:58,871 --> 00:17:02,129 Great debug to turn on, debug ip ospf adjacency, 314 00:17:02,129 --> 00:17:03,898 will tell you what's going on 315 00:17:03,898 --> 00:17:06,347 and why they are not neighbors, 316 00:17:06,347 --> 00:17:09,460 debug ip packets I would recommend 317 00:17:09,460 --> 00:17:11,999 that you not use that debug. 318 00:17:11,999 --> 00:17:15,824 That debug can be very verbose, give you gobs of output 319 00:17:15,824 --> 00:17:18,177 in just a couple of seconds, 320 00:17:18,177 --> 00:17:20,210 probably not a good idea to turn that one on. 321 00:17:20,210 --> 00:17:23,210 (futuristic music)