1 00:00:00,000 --> 00:00:03,297 [AUDIO LOGO] 2 00:00:03,297 --> 00:00:07,070 3 00:00:07,070 --> 00:00:09,680 So in this video, we're going to start 4 00:00:09,680 --> 00:00:14,390 by just getting an overview of the different OSPF area types 5 00:00:14,390 --> 00:00:16,070 that we have available. 6 00:00:16,070 --> 00:00:20,630 So we'll be talking about the stub, the totally stubby area, 7 00:00:20,630 --> 00:00:25,160 the not so stubby area, and the totally stubby, not 8 00:00:25,160 --> 00:00:28,580 so stubby area, which we really just often refer 9 00:00:28,580 --> 00:00:31,910 to as the total NSSA just because it's 10 00:00:31,910 --> 00:00:32,930 a lot easier to say. 11 00:00:32,930 --> 00:00:34,100 It's a bit shorter. 12 00:00:34,100 --> 00:00:38,420 So let's jump in and take a look at these different area types. 13 00:00:38,420 --> 00:00:40,430 We'll bring up our topology map. 14 00:00:40,430 --> 00:00:44,300 And we'll talk about which LSA types are or are not 15 00:00:44,300 --> 00:00:49,220 allowed into which areas and how they get filtered and where. 16 00:00:49,220 --> 00:00:53,300 So let's go ahead and jump in and get started. 17 00:00:53,300 --> 00:00:58,760 So to begin, we will talk about the normal or the regular area. 18 00:00:58,760 --> 00:01:00,650 Now, there's not really a whole lot 19 00:01:00,650 --> 00:01:03,860 to say about these as it's sort of what we're 20 00:01:03,860 --> 00:01:06,770 working with normally in OSPF. 21 00:01:06,770 --> 00:01:11,930 This is an area type that allows all LSA types. 22 00:01:11,930 --> 00:01:16,340 Now, we say all, we mean all normal LSAs. 23 00:01:16,340 --> 00:01:19,130 So that would effectively be type 24 00:01:19,130 --> 00:01:24,920 1's, 2's, 3's, 4's, and 5's. 25 00:01:24,920 --> 00:01:28,430 Remember that 6's are used for multicast 26 00:01:28,430 --> 00:01:30,860 and not supported by Cisco. 27 00:01:30,860 --> 00:01:34,610 And a type 7 is actually a very special use. 28 00:01:34,610 --> 00:01:36,980 We'll see that here in just a couple of minutes. 29 00:01:36,980 --> 00:01:41,750 So a type 7 would not actually be in a normal area. 30 00:01:41,750 --> 00:01:43,610 Now, the next thing to take note of 31 00:01:43,610 --> 00:01:48,620 is the backbone area must be a normal area. 32 00:01:48,620 --> 00:01:51,290 Of course, we're referring to area zero up here. 33 00:01:51,290 --> 00:01:55,190 You cannot have the backbone be a non-normal area. 34 00:01:55,190 --> 00:01:59,090 It must support all of these LSA types. 35 00:01:59,090 --> 00:02:01,910 Also note that virtual links, which 36 00:02:01,910 --> 00:02:04,940 we'll be talking about later in this course, 37 00:02:04,940 --> 00:02:08,570 can only transit a normal area. 38 00:02:08,570 --> 00:02:12,440 They can't transmit a stub or a not so stubby area. 39 00:02:12,440 --> 00:02:15,080 It has to be a normal area. 40 00:02:15,080 --> 00:02:17,210 So other than these few attributes, 41 00:02:17,210 --> 00:02:20,360 there's not really a whole lot to say about the normal area. 42 00:02:20,360 --> 00:02:23,360 Again, this is what we have by default 43 00:02:23,360 --> 00:02:26,450 if we just create an area in OSPF. 44 00:02:26,450 --> 00:02:29,860 So now let's move on to the stub. 45 00:02:29,860 --> 00:02:32,530 So the main idea behind the stub area 46 00:02:32,530 --> 00:02:37,720 is that we want to filter out the type 5 external LSAs. 47 00:02:37,720 --> 00:02:40,990 And at the same time, since the type 4 48 00:02:40,990 --> 00:02:45,970 is used to support the type 5, we'll filter those out as well. 49 00:02:45,970 --> 00:02:48,760 The idea is a stub area-- 50 00:02:48,760 --> 00:02:50,500 a good example of this would be something 51 00:02:50,500 --> 00:02:52,630 like area 200 up here-- 52 00:02:52,630 --> 00:02:56,860 would not need external routes such as this one coming 53 00:02:56,860 --> 00:02:58,690 from EIGRP over here. 54 00:02:58,690 --> 00:03:03,760 We don't need it as long as we inject a default 55 00:03:03,760 --> 00:03:06,310 route into that area instead. 56 00:03:06,310 --> 00:03:09,730 So if we inject this default into area 200, 57 00:03:09,730 --> 00:03:13,600 there is no need for area 200 to get 58 00:03:13,600 --> 00:03:18,400 external routing information from other areas such as area 59 00:03:18,400 --> 00:03:19,210 100. 60 00:03:19,210 --> 00:03:22,420 We can just default right to the ABR. 61 00:03:22,420 --> 00:03:25,600 Now, a side effect of all of this, of course, 62 00:03:25,600 --> 00:03:30,700 is that if we cannot have type 5 LSAs, in other words, 63 00:03:30,700 --> 00:03:35,560 we cannot have external routes, then an ASBR, which, of course, 64 00:03:35,560 --> 00:03:39,580 by nature, is bringing external routes into OSPF, 65 00:03:39,580 --> 00:03:43,810 cannot exist in a stub area simply, 66 00:03:43,810 --> 00:03:47,410 because type 5 LSAs are not allowed. 67 00:03:47,410 --> 00:03:52,090 Also, since having external routes in the database 68 00:03:52,090 --> 00:03:54,160 would affect whether the database is 69 00:03:54,160 --> 00:03:59,140 the same between two devices, all of the routers in an area 70 00:03:59,140 --> 00:04:04,670 must be configured for it to be a stub area. 71 00:04:04,670 --> 00:04:07,070 Again, the simple reason for this, 72 00:04:07,070 --> 00:04:11,870 all the routers in an area must have identical databases. 73 00:04:11,870 --> 00:04:14,540 I can't have one router, thinking 74 00:04:14,540 --> 00:04:18,140 that external routes are OK, and another router saying, 75 00:04:18,140 --> 00:04:19,190 no, they're not. 76 00:04:19,190 --> 00:04:22,610 We have to agree on what LSA types are 77 00:04:22,610 --> 00:04:24,920 allowed in the database. 78 00:04:24,920 --> 00:04:28,910 So stub areas are good in situations where 79 00:04:28,910 --> 00:04:31,550 we don't need external routes. 80 00:04:31,550 --> 00:04:36,020 And with this default route coming into area 200, 81 00:04:36,020 --> 00:04:40,280 we have to ask ourselves, do we even need the other type 82 00:04:40,280 --> 00:04:41,630 3 LSAs? 83 00:04:41,630 --> 00:04:44,930 Do I even need router 8's loopback address, for example, 84 00:04:44,930 --> 00:04:47,330 if I can just follow the default? 85 00:04:47,330 --> 00:04:49,160 If the answer to that question is 86 00:04:49,160 --> 00:04:54,980 no, which would be the case here because router 6 is 87 00:04:54,980 --> 00:04:58,280 the only way out of area 200, well, then we 88 00:04:58,280 --> 00:05:02,460 can move on to a total stub. 89 00:05:02,460 --> 00:05:06,090 So any time we see the word "totally" in relation 90 00:05:06,090 --> 00:05:13,530 to OSPF areas, just think about blocking type 3 LSAs. 91 00:05:13,530 --> 00:05:16,650 If we look at the rest of these points, 92 00:05:16,650 --> 00:05:20,340 that we block type 5's, and we block type 4's. 93 00:05:20,340 --> 00:05:22,980 And there's a default route injected, 94 00:05:22,980 --> 00:05:25,380 and there can be no ASBR. 95 00:05:25,380 --> 00:05:30,510 And all of the routers have to be configured for stub area, 96 00:05:30,510 --> 00:05:32,970 all of these things are the same things 97 00:05:32,970 --> 00:05:35,790 we said about the stub area to begin with. 98 00:05:35,790 --> 00:05:40,980 So what the real difference here is the type 3 LSA. 99 00:05:40,980 --> 00:05:42,810 And what we're going to do is we're 100 00:05:42,810 --> 00:05:47,340 going to stop things like router 8's loopback that 101 00:05:47,340 --> 00:05:52,290 would normally come in to area 200 as a type 3. 102 00:05:52,290 --> 00:05:55,470 We're going to, in fact, filter that and not 103 00:05:55,470 --> 00:05:59,040 send it in at all since we're getting the default. 104 00:05:59,040 --> 00:06:03,690 So the difference between a stub area and a total stub 105 00:06:03,690 --> 00:06:07,080 is, simply, we don't send the type 3 LSAs 106 00:06:07,080 --> 00:06:08,940 into the total stub. 107 00:06:08,940 --> 00:06:12,990 This is further filtering that's happening on the ABR. 108 00:06:12,990 --> 00:06:16,470 Now, the default it injects will still be a type 3. 109 00:06:16,470 --> 00:06:19,830 So it's not the type 3's are not allowed in the area. 110 00:06:19,830 --> 00:06:23,130 It's just the ABR is filtering them out. 111 00:06:23,130 --> 00:06:27,060 Now, this isn't going to be perfect in every environment. 112 00:06:27,060 --> 00:06:30,780 If there's more than one exit from the stub, 113 00:06:30,780 --> 00:06:36,180 we may prefer one ABR over another ABR coming out 114 00:06:36,180 --> 00:06:37,380 of that area. 115 00:06:37,380 --> 00:06:40,110 In that case, we would want the type 116 00:06:40,110 --> 00:06:44,310 3's so that we can prefer specific prefixes through one 117 00:06:44,310 --> 00:06:46,110 ABR versus another. 118 00:06:46,110 --> 00:06:48,570 So in that case, you would want to just do 119 00:06:48,570 --> 00:06:51,540 a stub, not the total stub. 120 00:06:51,540 --> 00:06:57,060 But in the case of our area 200 here, it only has one way out. 121 00:06:57,060 --> 00:06:59,880 So there's no need to have anything other 122 00:06:59,880 --> 00:07:02,160 than that default. 123 00:07:02,160 --> 00:07:07,140 Now, one of the big limitations here of a stub area is that 124 00:07:07,140 --> 00:07:11,430 an ASBR cannot exist in this area type. 125 00:07:11,430 --> 00:07:14,760 So maybe we just had a few external routes 126 00:07:14,760 --> 00:07:16,440 we wanted to bring in. 127 00:07:16,440 --> 00:07:18,810 Well, we can't do that in a stub. 128 00:07:18,810 --> 00:07:23,130 And because of that, we have another area type, 129 00:07:23,130 --> 00:07:26,156 the Not So Stubby Area, or the NSSA. 130 00:07:26,156 --> 00:07:29,190 131 00:07:29,190 --> 00:07:33,570 So the idea behind the NSSA is that although we are still 132 00:07:33,570 --> 00:07:37,230 not allowing type 5's and type 4's, 133 00:07:37,230 --> 00:07:40,530 we can still bring in external routes. 134 00:07:40,530 --> 00:07:44,460 Now, one other fundamental difference here with a stub 135 00:07:44,460 --> 00:07:49,560 is that a default route is not injected automatically 136 00:07:49,560 --> 00:07:51,480 into the NSSA. 137 00:07:51,480 --> 00:07:53,550 And we'll see that more when we actually 138 00:07:53,550 --> 00:07:55,380 look at this in action. 139 00:07:55,380 --> 00:08:00,750 However, the biggest difference is that an ASBR actually 140 00:08:00,750 --> 00:08:04,080 can exist in this area. 141 00:08:04,080 --> 00:08:09,660 It's going to use LSA type 7 for those external prefixes. 142 00:08:09,660 --> 00:08:13,200 So a good example would be area 100 here. 143 00:08:13,200 --> 00:08:15,780 If we were going to try to make this a stub, 144 00:08:15,780 --> 00:08:21,030 we would lose the routes from router 9 coming in from EIGRP. 145 00:08:21,030 --> 00:08:23,160 Well, that's not what we would want to do. 146 00:08:23,160 --> 00:08:24,990 We do need those routes. 147 00:08:24,990 --> 00:08:26,970 So if we still want to bring those routes 148 00:08:26,970 --> 00:08:29,700 into this area, meaning, of course, 149 00:08:29,700 --> 00:08:33,390 we still want router 2 to be an ASBR, 150 00:08:33,390 --> 00:08:36,870 the only choice would be to make this NSSA. 151 00:08:36,870 --> 00:08:42,960 What happens is these updates come in as type 7's. 152 00:08:42,960 --> 00:08:48,840 That type 7 will then get translated into a type 5 153 00:08:48,840 --> 00:08:53,490 by one of the ABRs and sent into the rest of the network. 154 00:08:53,490 --> 00:08:59,040 So the type 7 only exists inside of the NSSA. 155 00:08:59,040 --> 00:09:02,280 Now, at the end of the day, this is still a stub. 156 00:09:02,280 --> 00:09:06,150 So keep in mind those type 5's and those type 4's are still 157 00:09:06,150 --> 00:09:07,350 not allowed. 158 00:09:07,350 --> 00:09:09,690 And, again, just like we said before, 159 00:09:09,690 --> 00:09:12,480 since that's affecting what's in the database, 160 00:09:12,480 --> 00:09:17,670 all the routers are going to have to be configured for NSSA 161 00:09:17,670 --> 00:09:20,620 just like they did for the stub. 162 00:09:20,620 --> 00:09:25,030 Now, the NSSA is actually probably our more complicated 163 00:09:25,030 --> 00:09:26,860 of the area types. 164 00:09:26,860 --> 00:09:29,020 So we're going to jump in and take a look at this. 165 00:09:29,020 --> 00:09:29,890 And we're actually going to spend 166 00:09:29,890 --> 00:09:31,630 a little bit more time on this one 167 00:09:31,630 --> 00:09:34,990 than we do on stub and total stub. 168 00:09:34,990 --> 00:09:37,870 NSSA does get a little more complicated. 169 00:09:37,870 --> 00:09:40,690 So we'll see that in an upcoming video. 170 00:09:40,690 --> 00:09:46,360 But just like we have for stub, there's a counterpart here. 171 00:09:46,360 --> 00:09:51,010 So as we had stub 2 totally stubby, 172 00:09:51,010 --> 00:09:56,890 we also have NSSA to the total NSSA. 173 00:09:56,890 --> 00:09:59,140 Let's take a look at that one. 174 00:09:59,140 --> 00:10:03,850 So just like with the total stub, the totally NSSA, 175 00:10:03,850 --> 00:10:07,690 or the total NSSA, as it's more commonly referred to, 176 00:10:07,690 --> 00:10:12,640 simply adds that additional filtering of the type 3. 177 00:10:12,640 --> 00:10:14,530 Again, all the rest of these points 178 00:10:14,530 --> 00:10:18,460 are going to be exactly the same as the NSSA. 179 00:10:18,460 --> 00:10:22,750 The only real difference is, once again, on the ABRs. 180 00:10:22,750 --> 00:10:26,800 Any type 3's that would be sent into this area 181 00:10:26,800 --> 00:10:29,610 are going to be filtered out. 182 00:10:29,610 --> 00:10:33,030 A couple of things to note about the use of total, 183 00:10:33,030 --> 00:10:36,480 be it for the stub or the NSSA. 184 00:10:36,480 --> 00:10:41,070 Technically, the total stub and the total NSSA 185 00:10:41,070 --> 00:10:43,320 are Cisco proprietary. 186 00:10:43,320 --> 00:10:48,990 However, since it's just the ABR doing additional filtering, 187 00:10:48,990 --> 00:10:52,860 the other routers in that area don't know anything 188 00:10:52,860 --> 00:10:54,990 about that total flag. 189 00:10:54,990 --> 00:10:57,090 They don't know anything about the fact 190 00:10:57,090 --> 00:11:00,000 that the ABR is doing extra filtering. 191 00:11:00,000 --> 00:11:04,110 So even though it is technically Cisco proprietary, that 192 00:11:04,110 --> 00:11:06,180 doesn't really affect compatibility 193 00:11:06,180 --> 00:11:09,120 with other vendor's routers because, 194 00:11:09,120 --> 00:11:11,370 again, they don't know it's happening. 195 00:11:11,370 --> 00:11:14,430 And, also, on that note, the total 196 00:11:14,430 --> 00:11:18,570 only has to be configured on the ABRs. 197 00:11:18,570 --> 00:11:20,760 And there's nothing that stops those 198 00:11:20,760 --> 00:11:24,660 from still forming neighborships with other devices that 199 00:11:24,660 --> 00:11:28,560 are just configured as either stub or NSSA. 200 00:11:28,560 --> 00:11:31,530 So in this video, we just took a look 201 00:11:31,530 --> 00:11:35,130 at the basics of the different OSPF area 202 00:11:35,130 --> 00:11:40,410 types, their attributes, which LSAs are sent between which 203 00:11:40,410 --> 00:11:44,400 areas, and a little bit more look at where that type 7 204 00:11:44,400 --> 00:11:47,460 LSA is used in the NSSA. 205 00:11:47,460 --> 00:11:51,240 In the next video, we're going to jump into the command line 206 00:11:51,240 --> 00:11:54,000 and get started looking at this, starting 207 00:11:54,000 --> 00:11:57,030 with the stub and the total stub. 208 00:11:57,030 --> 00:11:59,130 I hope this has been informative for you, 209 00:11:59,130 --> 00:12:02,120 and I'd like to thank you for viewing. 210 00:12:02,120 --> 00:12:05,000