1 00:00:00,000 --> 00:00:00,942 2 00:00:00,942 --> 00:00:04,239 [AUDIO LOGO] 3 00:00:04,239 --> 00:00:08,020 4 00:00:08,020 --> 00:00:12,220 Now that we have our one-way redistribution done into IS-IS, 5 00:00:12,220 --> 00:00:14,890 let's move on to OSPF. 6 00:00:14,890 --> 00:00:18,250 So in this video, we're going to redistribute 7 00:00:18,250 --> 00:00:25,360 both EIGRP and IS-IS, as well as connected into OSPF. 8 00:00:25,360 --> 00:00:28,390 So let's bring up our topology design 9 00:00:28,390 --> 00:00:29,740 where we're going to do this. 10 00:00:29,740 --> 00:00:31,660 And then we'll jump into the command line 11 00:00:31,660 --> 00:00:35,050 and do some redistribution into OSPF. 12 00:00:35,050 --> 00:00:40,570 And of course, look at some of the caveats as we go. 13 00:00:40,570 --> 00:00:42,510 So what we're going to configure now 14 00:00:42,510 --> 00:00:48,540 is we will configure router 1 to redistribute EIGRP into OSPF. 15 00:00:48,540 --> 00:00:51,600 We'll do the same thing on router 2. 16 00:00:51,600 --> 00:00:56,340 Then we'll configure router 1 to redistribute IS-IS into OSPF 17 00:00:56,340 --> 00:00:59,350 and do the same thing on router 3. 18 00:00:59,350 --> 00:01:01,980 And of course, we'll be looking at these routes 19 00:01:01,980 --> 00:01:05,349 on various different routers through our topology. 20 00:01:05,349 --> 00:01:07,410 So let's jump into the command line 21 00:01:07,410 --> 00:01:11,040 and get started with our redistribution. 22 00:01:11,040 --> 00:01:14,910 So for this demonstration, let's start off on router 5 23 00:01:14,910 --> 00:01:19,080 with simply a show ip route ospf. 24 00:01:19,080 --> 00:01:20,730 And all we want to really look at 25 00:01:20,730 --> 00:01:25,920 is we just currently have internal OSPF routes. 26 00:01:25,920 --> 00:01:28,990 That's all we have on router 5 right now. 27 00:01:28,990 --> 00:01:32,700 So let's jump up to router 1 and configure our redistribution 28 00:01:32,700 --> 00:01:36,390 from EIGRP into OSPF. 29 00:01:36,390 --> 00:01:39,210 So we'll simply go in and configuration mode, 30 00:01:39,210 --> 00:01:44,040 into router OSPF 1, into our address family. 31 00:01:44,040 --> 00:01:48,700 And let's do a redistribute eigrp 100. 32 00:01:48,700 --> 00:01:50,410 And if we hit question mark after this, 33 00:01:50,410 --> 00:01:52,450 we'll see we have some different choices here. 34 00:01:52,450 --> 00:01:56,490 We can match on certain criteria or set the LSA type 35 00:01:56,490 --> 00:02:00,270 for redistributed routes, do things like redistribute only 36 00:02:00,270 --> 00:02:01,920 into NSSA. 37 00:02:01,920 --> 00:02:03,960 Of course, we can run our redistribution 38 00:02:03,960 --> 00:02:07,110 through a route policy that we could use for filtering 39 00:02:07,110 --> 00:02:08,639 or route manipulation. 40 00:02:08,639 --> 00:02:12,330 But what we want to do right now is just tag these routes. 41 00:02:12,330 --> 00:02:16,280 And what we're going to do is we're going to tag them as 90. 42 00:02:16,280 --> 00:02:19,310 Now, realistically, you can use any tag you want. 43 00:02:19,310 --> 00:02:21,920 In a relatively simple environment, 44 00:02:21,920 --> 00:02:24,710 I usually use the tag that's based 45 00:02:24,710 --> 00:02:27,710 on that routing protocol's admin distance 46 00:02:27,710 --> 00:02:29,820 just because it's easy to remember. 47 00:02:29,820 --> 00:02:33,740 And then later, we can easily see that this came from EIGRP. 48 00:02:33,740 --> 00:02:35,660 Of course, if you want to use any other tags, 49 00:02:35,660 --> 00:02:37,160 that's perfectly fine. 50 00:02:37,160 --> 00:02:39,380 And in a more complex environment 51 00:02:39,380 --> 00:02:44,450 where say, for example, we had more than one EIGRP AS, 52 00:02:44,450 --> 00:02:46,520 well, we would have to use different tags, 53 00:02:46,520 --> 00:02:48,020 or else, we wouldn't be able to tell 54 00:02:48,020 --> 00:02:49,290 the difference between them. 55 00:02:49,290 --> 00:02:52,160 But in a simple environment, I just find this as an easy way 56 00:02:52,160 --> 00:02:53,360 to do tags. 57 00:02:53,360 --> 00:02:55,700 So we'll go ahead and configure that. 58 00:02:55,700 --> 00:02:57,590 Commit those changes. 59 00:02:57,590 --> 00:02:59,780 And we'll exit configuration. 60 00:02:59,780 --> 00:03:01,790 As far as doing some verification, 61 00:03:01,790 --> 00:03:05,690 we can start with a show ip ospf database. 62 00:03:05,690 --> 00:03:08,310 We'll filter by external routes. 63 00:03:08,310 --> 00:03:11,750 And we'll say self to indicate self-originating. 64 00:03:11,750 --> 00:03:14,420 These are the external routes that we are 65 00:03:14,420 --> 00:03:17,090 putting into the OSPF database. 66 00:03:17,090 --> 00:03:19,470 We can see here that we're bringing in say, 67 00:03:19,470 --> 00:03:22,370 for example, router 9's loopback. 68 00:03:22,370 --> 00:03:27,070 Here, we have the link between router 1 and router 9. 69 00:03:27,070 --> 00:03:31,050 Here, we have the link between router 2 and router 9. 70 00:03:31,050 --> 00:03:35,580 And then we have some additional loopback interfaces on router 9 71 00:03:35,580 --> 00:03:38,460 that we're also bringing into OSPF. 72 00:03:38,460 --> 00:03:42,210 So we can, of course, see these if we go back over to router 5. 73 00:03:42,210 --> 00:03:44,980 Let's do our show ip route ospf again. 74 00:03:44,980 --> 00:03:47,700 But this time, let's filter it and say 75 00:03:47,700 --> 00:03:53,460 to include anything that's OSPF and external. 76 00:03:53,460 --> 00:03:56,070 What we see here is all of those prefixes 77 00:03:56,070 --> 00:03:58,030 that we just saw on the database-- 78 00:03:58,030 --> 00:04:03,630 now being brought in as external type 2's into OSPF. 79 00:04:03,630 --> 00:04:06,760 This is, of course, exactly what we're looking for. 80 00:04:06,760 --> 00:04:09,700 If we were to pick on one of these prefixes, 81 00:04:09,700 --> 00:04:14,220 so let's just say, for example, the 100.9.9.0, 82 00:04:14,220 --> 00:04:17,279 we can also see that route tag being applied here-- 83 00:04:17,279 --> 00:04:19,470 the route tag of 90. 84 00:04:19,470 --> 00:04:22,600 We can, of course, see this in the database as well. 85 00:04:22,600 --> 00:04:25,320 And we see here where the external route tag is set 86 00:04:25,320 --> 00:04:27,880 to 90 in the database as well. 87 00:04:27,880 --> 00:04:30,360 Now, let's go ahead and configure the redistribution 88 00:04:30,360 --> 00:04:32,890 on router 2 as well. 89 00:04:32,890 --> 00:04:35,550 Now, we're going to partially copy and paste this, 90 00:04:35,550 --> 00:04:38,550 but we're going to stop here at the tag. 91 00:04:38,550 --> 00:04:42,330 And the reason is we're going to go a little further this time. 92 00:04:42,330 --> 00:04:48,090 And we're going to set the metric type to be type 1. 93 00:04:48,090 --> 00:04:52,140 We saw just a moment ago that the default is to bring routes 94 00:04:52,140 --> 00:04:55,710 into OSPF as external type 2. 95 00:04:55,710 --> 00:04:57,480 Well, let's go ahead and change that, 96 00:04:57,480 --> 00:05:01,020 bring them in as external type 1 on router 2 97 00:05:01,020 --> 00:05:03,040 just to do it a little different. 98 00:05:03,040 --> 00:05:06,930 We'll commit our changes and exit configuration. 99 00:05:06,930 --> 00:05:10,890 Let's go ahead and look at those self-generated external LSAs 100 00:05:10,890 --> 00:05:12,280 again. 101 00:05:12,280 --> 00:05:16,080 We see that once again, we are generating all of those LSAs. 102 00:05:16,080 --> 00:05:19,230 They are, however, a type 1 this time, 103 00:05:19,230 --> 00:05:21,900 and they are still being tagged. 104 00:05:21,900 --> 00:05:23,550 We see it as all the same entries 105 00:05:23,550 --> 00:05:26,070 here as we scroll through the database. 106 00:05:26,070 --> 00:05:28,320 So now, what should have happened if we jump back over 107 00:05:28,320 --> 00:05:34,740 router 5, is router 5 should now be preferring all the E1's. 108 00:05:34,740 --> 00:05:39,240 Because remember in OSPF, external type 1's get chosen 109 00:05:39,240 --> 00:05:41,640 over external type 2's. 110 00:05:41,640 --> 00:05:44,340 So we can see that it's now choosing all the external type 111 00:05:44,340 --> 00:05:47,430 1's, which are coming from router 2. 112 00:05:47,430 --> 00:05:51,000 So now that we have EIGRP routes in OSPF, 113 00:05:51,000 --> 00:05:53,530 let's bring in the IS-IS routes as well. 114 00:05:53,530 --> 00:05:56,890 So let's go over to router 1. 115 00:05:56,890 --> 00:06:01,480 Of course, we go back into OSPF address-family. 116 00:06:01,480 --> 00:06:06,550 And we'll say to redistribute IS-IS process 1. 117 00:06:06,550 --> 00:06:09,550 And we'll go ahead and tag those as 115, 118 00:06:09,550 --> 00:06:13,970 which, of course, is IS-IS's administrative distance. 119 00:06:13,970 --> 00:06:16,000 We'll commit those changes. 120 00:06:16,000 --> 00:06:17,440 Exit configuration. 121 00:06:17,440 --> 00:06:20,380 And we're going to configure the exact same thing on router 3. 122 00:06:20,380 --> 00:06:23,660 So we'll just copy and paste that configuration. 123 00:06:23,660 --> 00:06:26,540 So here on router 3, we'll just paste that in. 124 00:06:26,540 --> 00:06:30,440 And now, let's go check router 5 again. 125 00:06:30,440 --> 00:06:31,930 So once again, we'll look for all 126 00:06:31,930 --> 00:06:34,490 of the OSPF external routes. 127 00:06:34,490 --> 00:06:38,350 And notice that we have considerably more routes now. 128 00:06:38,350 --> 00:06:42,320 We have all the routes coming from the IS-IS domain, 129 00:06:42,320 --> 00:06:47,440 including, for example, this 88.88.88.0, 130 00:06:47,440 --> 00:06:50,900 which we know is coming from router 8. 131 00:06:50,900 --> 00:06:55,520 So now that we have mutual redistribution on two routers, 132 00:06:55,520 --> 00:06:58,310 we know that both routing domains should 133 00:06:58,310 --> 00:07:00,180 have routes for each other. 134 00:07:00,180 --> 00:07:03,740 Now, we can hop over to router 7 or router 8, 135 00:07:03,740 --> 00:07:06,140 look at their routing tables, and make sure 136 00:07:06,140 --> 00:07:07,790 that they have the OSPF routes. 137 00:07:07,790 --> 00:07:10,880 But we did do that in the previous video 138 00:07:10,880 --> 00:07:13,790 when we redistributed into IS-IS. 139 00:07:13,790 --> 00:07:15,890 So that should still be OK. 140 00:07:15,890 --> 00:07:20,150 Now would be a good time to test connectivity. 141 00:07:20,150 --> 00:07:24,580 Let's go ahead and trace to that 88.88.88.88, 142 00:07:24,580 --> 00:07:28,600 and we will source that from our loopback 0 interface. 143 00:07:28,600 --> 00:07:32,810 144 00:07:32,810 --> 00:07:35,990 As you can see, this is a routing loop. 145 00:07:35,990 --> 00:07:38,590 146 00:07:38,590 --> 00:07:41,380 Our traffic is going to router 2, 147 00:07:41,380 --> 00:07:44,260 then to router 1, then to router 7, 148 00:07:44,260 --> 00:07:48,340 then to router 3, then back to router 1, back to router 7, 149 00:07:48,340 --> 00:07:50,390 back to router, and so on. 150 00:07:50,390 --> 00:07:53,890 So this is entering a routing loop. 151 00:07:53,890 --> 00:07:58,330 And this is exactly what we said can happen if you don't control 152 00:07:58,330 --> 00:08:03,220 routing loops when you do mutual redistribution on two routers. 153 00:08:03,220 --> 00:08:05,680 But let's take a look at our routing tables 154 00:08:05,680 --> 00:08:08,440 and figure out why this is happening. 155 00:08:08,440 --> 00:08:10,540 The biggest giveaway is just going 156 00:08:10,540 --> 00:08:13,330 to be to go look at router 7. 157 00:08:13,330 --> 00:08:15,490 Let's just start with that show ip route. 158 00:08:15,490 --> 00:08:18,040 Just verify that we do still have all of those routes 159 00:08:18,040 --> 00:08:19,600 that we're supposed to have. 160 00:08:19,600 --> 00:08:21,740 We can see that we do. 161 00:08:21,740 --> 00:08:24,880 However, we do have a rather large problem. 162 00:08:24,880 --> 00:08:27,460 If we look at that 88 route. 163 00:08:27,460 --> 00:08:30,490 Now, what's interesting is this is showing it 164 00:08:30,490 --> 00:08:32,650 that it's load-sharing. 165 00:08:32,650 --> 00:08:36,820 But the fact of the matter is, it really is not load-sharing. 166 00:08:36,820 --> 00:08:40,240 It's sending the traffic back to router 3. 167 00:08:40,240 --> 00:08:42,760 We saw that in our trace. 168 00:08:42,760 --> 00:08:45,430 So just so we fully understand the problem, 169 00:08:45,430 --> 00:08:47,870 let me bring up the diagram again. 170 00:08:47,870 --> 00:08:50,260 So let's remember what's happening here. 171 00:08:50,260 --> 00:08:55,120 Router 8 is sending this update to router 7. 172 00:08:55,120 --> 00:09:03,220 Router 7 is sending it to router 1 and router 3 through IS-IS. 173 00:09:03,220 --> 00:09:09,100 Now remember, IS-IS has an admin distance of 115. 174 00:09:09,100 --> 00:09:11,500 So then, one of the routers. 175 00:09:11,500 --> 00:09:14,740 And in this case, just based on the evidence, 176 00:09:14,740 --> 00:09:18,640 we can say that it's router 1. 177 00:09:18,640 --> 00:09:23,380 1 is taking that route and redistributing it into OSPF. 178 00:09:23,380 --> 00:09:29,620 Then what happens is OSPF sends this down to router 3. 179 00:09:29,620 --> 00:09:37,750 Router 3 now has an admin distance of 110 versus 115. 180 00:09:37,750 --> 00:09:42,310 And what it's essentially doing is replacing the IS-IS route 181 00:09:42,310 --> 00:09:46,600 in its routing table with the OSPF route. 182 00:09:46,600 --> 00:09:51,650 Once that's done, this part is not happening anymore. 183 00:09:51,650 --> 00:09:54,770 So now, since router is configured, of course, 184 00:09:54,770 --> 00:09:59,950 to redistribute OSPF back into IS-IS, it's doing just that 185 00:09:59,950 --> 00:10:04,270 and sending this update right back to router 7. 186 00:10:04,270 --> 00:10:09,280 Router 7 now has two IS-IS routes, 187 00:10:09,280 --> 00:10:12,910 which, again, theoretically, it should be load-sharing. 188 00:10:12,910 --> 00:10:15,580 But we could tell by the trace, it's not. 189 00:10:15,580 --> 00:10:19,150 It's sending the traffic right back to router 3. 190 00:10:19,150 --> 00:10:21,430 And this is why we have the loop. 191 00:10:21,430 --> 00:10:24,560 We'll be solving this in an upcoming video. 192 00:10:24,560 --> 00:10:26,290 We're not going to tackle this right now. 193 00:10:26,290 --> 00:10:27,920 But that's the problem. 194 00:10:27,920 --> 00:10:31,400 And that's why we have this loop. 195 00:10:31,400 --> 00:10:34,880 In this video, we looked at how to redistribute routes 196 00:10:34,880 --> 00:10:36,980 into OSPF. 197 00:10:36,980 --> 00:10:39,020 A couple of things to note about that-- 198 00:10:39,020 --> 00:10:44,120 first, all the routes come in by default as an external type 2, 199 00:10:44,120 --> 00:10:47,390 which, of course, we can change on the redistribution, 200 00:10:47,390 --> 00:10:49,610 like we did on router 2. 201 00:10:49,610 --> 00:10:52,550 Also, we didn't exactly point this out 202 00:10:52,550 --> 00:10:54,740 as we went because we had discussed it 203 00:10:54,740 --> 00:10:57,330 earlier in our previous videos. 204 00:10:57,330 --> 00:10:59,460 However, if you didn't notice it, 205 00:10:59,460 --> 00:11:01,370 you can go back and look that all 206 00:11:01,370 --> 00:11:05,480 of those routes we redistributed came in with that default seed 207 00:11:05,480 --> 00:11:09,410 metric of 20 because we didn't change that. 208 00:11:09,410 --> 00:11:13,460 Also, we got our first look here at a routing loop 209 00:11:13,460 --> 00:11:15,830 being caused by redistribution. 210 00:11:15,830 --> 00:11:18,500 And of course, we'll be solving that later. 211 00:11:18,500 --> 00:11:20,270 Before we do, though, we're going 212 00:11:20,270 --> 00:11:22,850 to configure redistribution into RIP. 213 00:11:22,850 --> 00:11:25,170 And that's exactly what we're going to do next. 214 00:11:25,170 --> 00:11:26,250 Until then. 215 00:11:26,250 --> 00:11:28,280 I hope this has been informative for you, 216 00:11:28,280 --> 00:11:31,210 and I'd like to thank you for viewing. 217 00:11:31,210 --> 00:11:35,000