WEBVTT 1 00:00.000 --> 00:01.920 So this is the topology where once again, 2 00:01.920 --> 00:06.120 I'm gonna be using for IPv4 routing with OSPF version three. 3 00:06.120 --> 00:09.090 Now one of the things that we wanna be aware of right on the gate is that if we 4 00:09.090 --> 00:10.600 're using OSPF V3, 5 00:10.600 --> 00:12.920 which is traditionally for IPv6, 6 00:12.920 --> 00:14.760 if we're gonna use it with IPv4, 7 00:14.760 --> 00:18.520 we need to make sure that we've enabled IPv6 on our interfaces, 8 00:18.520 --> 00:21.320 because even though we're doing routing for IPv4 traffic, 9 00:21.320 --> 00:26.840 behind the scenes, OSPF V3 is actually using multicast addresses for IPv6 10 00:26.840 --> 00:29.800 to communicate messages back and forth between peers. 11 00:29.800 --> 00:34.080 So first and foremost, make sure we have enabled IPv6 on our interfaces. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:29.800 --> 00:34.080 So first and foremost, make sure we have enabled IPv6 on our interfaces. 12 00:34.080 --> 00:38.640 And again, that's even if we're not intending to do routing for IPv6, 13 00:38.640 --> 00:43.510 we need enabled IPv6 interfaces if we wanna support OSPF V3 for the address 14 00:43.510 --> 00:44.440 family of IPv4. 15 00:44.440 --> 00:47.720 That also included having IPv6 unicast routing enabled. 16 00:47.720 --> 00:49.640 So on each of these eight routers, 17 00:49.640 --> 00:52.160 each of the interfaces already has an IPv6 address, 18 00:52.160 --> 00:56.200 and IPv6 unicast routing is enabled on all eight routers. 19 00:56.200 --> 01:00.480 So to configure OSPF V3 for IPv4, we'll go into configuration mode, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 00:56.200 --> 01:00.480 So to configure OSPF V3 for IPv4, we'll go into configuration mode, 20 01:00.480 --> 01:04.400 then further we'll go into router configuration for OSPF V3. 21 01:04.400 --> 01:07.160 By typing router, OSPF V3, 22 01:07.160 --> 01:09.360 and then the process ID number that we wanna use. 23 01:09.360 --> 01:12.840 So in the lab, I'm gonna simply use process ID1 across the board. 24 01:12.840 --> 01:16.080 And then inside the OSPF V3 routing process configuration, 25 01:16.080 --> 01:18.600 we have our address families, I'll put AF for short. 26 01:18.600 --> 01:22.560 So for using IPv6, we'd have an address family for IPv6. 27 01:22.560 --> 01:26.760 And if we're using IPv4, we have a separate address family for IPv4. 28 01:26.760 --> 01:30.950 So in this set of videos here, we're gonna focus on the address family for IPv4 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 01:26.760 --> 01:30.950 So in this set of videos here, we're gonna focus on the address family for IPv4 29 01:30.950 --> 01:31.760 only. 30 01:31.760 --> 01:35.640 So I'm gonna go ahead and remove the IPv6 component as we're focusing just on 31 01:35.640 --> 01:36.480 IPv4. 32 01:36.480 --> 01:40.190 And then here under the address family, we could go ahead and specify passive 33 01:40.190 --> 01:40.920 interfaces. 34 01:40.920 --> 01:44.120 If we wanna do redistribution, we could do redistribution here under the 35 01:44.120 --> 01:45.760 address family for IPv4. 36 01:45.760 --> 01:48.600 For example, if R1 had some static IPv4 routes, 37 01:48.600 --> 01:52.360 and we wanted to redistrue those into OSPF, we would do that within the address 38 01:52.360 --> 01:53.040 family. 39 01:53.040 --> 01:56.580 And if we did that redistribution from a static route into the routing process 40 01:56.580 --> 01:58.440 for OSPF V3 here on R1, 41 01:58.440 --> 02:03.320 they would make R1 an ASBR and a ton of system boundary router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:58.440 --> 02:03.320 they would make R1 an ASBR and a ton of system boundary router. 42 02:03.320 --> 02:08.440 And R3 and R4, because they're connected to the backbone area and also to non 43 02:08.440 --> 02:09.560 backbone areas. 44 02:09.560 --> 02:13.720 Router 3 and router 4 would both be ABRs, area border routers. 45 02:13.720 --> 02:15.320 So let me go ahead and clean this up a little bit. 46 02:15.320 --> 02:17.200 And let's talk about a few other key points. 47 02:17.200 --> 02:19.600 And in previous skills, we've taken a look at the LSA types. 48 02:19.600 --> 02:23.800 And so we have the common LSA types we'd normally find with IPv4. 49 02:23.800 --> 02:30.320 So LSA type 1, that's the router LSA generated by each router, LSA type 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 02:23.800 --> 02:30.320 So LSA type 1, that's the router LSA generated by each router, LSA type 2. 50 02:30.320 --> 02:34.240 LSA type 2 is the network LSA generated by the designated router on a segment. 51 02:34.240 --> 02:37.360 If there's two or more speakers or routers on that segment, 52 02:37.360 --> 02:40.640 three is the interarea prefix LSA. 53 02:40.640 --> 02:44.000 Or in the traditional flavor of OSPF, it was referred to as the summary. 54 02:44.000 --> 02:45.680 And those are generated by the ABRs. 55 02:45.680 --> 02:48.990 So for example, these networks, the 13 network and 12 network and the 24 56 02:48.990 --> 02:50.400 network and 34 network. 57 02:50.400 --> 02:52.800 And those are advertised down into area 1. 58 02:52.800 --> 02:56.400 We aren't sending the actual original LSAs for those, but what we're doing is, 59 02:56.400 --> 03:01.240 I should say R3 is doing as the ABR, it's sending an LSA type 3 for each of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 02:56.400 --> 03:01.240 I should say R3 is doing as the ABR, it's sending an LSA type 3 for each of 60 03:01.240 --> 03:01.760 those. 61 03:01.760 --> 03:05.360 And it's the LSA 3s that get propagated down into the other normal areas. 62 03:05.360 --> 03:09.360 Then we have LSA types 4 and 5 dealing with external routes being redistributed 63 03:09.360 --> 03:10.240 into OSPF. 64 03:10.240 --> 03:13.200 So the actual LSA type 5 is the route itself. 65 03:13.200 --> 03:16.240 For example, we had static routes, we brought them into OSPF. 66 03:16.240 --> 03:17.520 Those would be LSA type 5s. 67 03:17.520 --> 03:20.800 And then the area border routers, also going to advertise an LSA type 4, 68 03:20.800 --> 03:24.640 indicating how to reach the ASBR who did the redistribution. 69 03:24.640 --> 03:28.160 So that identifies the ASBR and the external route. 70 03:28.160 --> 03:32.080 Now normally, with just IPv4 and the traditional flavor of implementing it, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 03:28.160 --> 03:32.080 Now normally, with just IPv4 and the traditional flavor of implementing it, 71 03:32.080 --> 03:35.600 we wouldn't even deal with LSA types 8 and 9. 72 03:35.600 --> 03:40.320 However, because we're using OSPF version 3 to support the address family for 73 03:40.320 --> 03:40.960 IPv4, 74 03:40.960 --> 03:43.360 there also is an 8 and a 9. 75 03:43.360 --> 03:48.400 So the 8 is a link LSA and 9 is an intra area prefix LSA. 76 03:48.400 --> 03:51.440 An intra meaning routes within a given area, 77 03:51.440 --> 03:54.850 compared to inter area where those are routes that are going and being 78 03:54.850 --> 03:56.240 advertised between areas. 79 03:56.240 --> 03:58.800 So intra within, inter between. 80 03:58.800 --> 04:02.680 And to become fully adjacent neighbors, the neighbors have to agree on several WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 80 03:58.800 --> 04:02.680 And to become fully adjacent neighbors, the neighbors have to agree on several 81 04:02.680 --> 04:03.280 parameters. 82 04:03.280 --> 04:09.140 And so we in the past have used STTAMP as a way to help remember some of those 83 04:09.140 --> 04:09.760 parameters, 84 04:09.760 --> 04:13.110 including the neighbors have to agree on what is the subnet that they're both 85 04:13.110 --> 04:13.680 connected to. 86 04:13.680 --> 04:17.920 So if 10, 0, 12 is the actual network and R1 thinks it's a different network, 87 04:17.920 --> 04:19.760 than R2 does, they won't neighbor up. 88 04:19.760 --> 04:21.600 They have to agree on the timers. 89 04:21.600 --> 04:26.000 So if R1 thinks the hello interval is 11 seconds and R2 thinks it's 10 seconds, 90 04:26.000 --> 04:27.120 they will not labor up. 91 04:27.120 --> 04:28.880 They also have to agree on the network type. 92 04:28.880 --> 04:32.640 So is it, for example, a point-to-point network like a serial interface down WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 04:28.880 --> 04:32.640 So is it, for example, a point-to-point network like a serial interface down 93 04:32.640 --> 04:33.280 here, 94 04:33.280 --> 04:35.120 or is it a broadcast network? 95 04:35.120 --> 04:38.880 Or they can dynamically discover other OSPF speakers on the network. 96 04:38.880 --> 04:43.040 So here I'll put broadcast point-to-point or point-to-multipoint 97 04:43.040 --> 04:45.360 if we're using things like DMVPN. 98 04:45.360 --> 04:47.840 And the key here also is that if we're using a broadcast network, 99 04:47.840 --> 04:51.360 we're expecting to have a DR elected and set up. 100 04:51.360 --> 04:53.520 And if we're using a point-to-point or point-to-multipoint, 101 04:53.520 --> 04:57.040 we're not expecting to set up a designated router for the segment. 102 04:57.040 --> 04:58.640 The A is for area. 103 04:58.640 --> 05:00.480 They have to agree on the area number. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 04:58.640 --> 05:00.480 They have to agree on the area number. 104 05:00.480 --> 05:02.800 So if router 1 up here believes this is area 0, 105 05:02.800 --> 05:04.640 that this interface has been assigned to, 106 05:04.640 --> 05:06.640 and R2 believes this is area 1, 107 05:06.640 --> 05:08.400 that will cause them to not neighbor up. 108 05:08.800 --> 05:11.520 Another factor that has to match is the area type. 109 05:11.520 --> 05:15.680 For example, is the area a normal area, or is it a stub area? 110 05:15.680 --> 05:17.920 So right here in area, let's go to area 2. 111 05:17.920 --> 05:22.960 If R4 on the serial 3/1 interface believes it's a stub area, 112 05:22.960 --> 05:28.400 and R6 has been configured on it's serial 3/2 to believe it's a normal area 113 05:28.400 --> 05:30.560 that will also prevent them from neighboring up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 113 05:28.400 --> 05:30.560 that will also prevent them from neighboring up. 114 05:30.560 --> 05:32.240 They also need to agree on the M-T-U. 115 05:32.240 --> 05:35.970 And normally that only becomes an issue if we're dealing with, for example, a 116 05:35.970 --> 05:36.400 router 117 05:36.400 --> 05:39.600 and for example a multilayer switch where the M-T-U's are slightly different. 118 05:39.600 --> 05:42.160 So if we have two neighbors that don't agree on an M-T-U, 119 05:42.160 --> 05:43.680 we could go ahead and modify one of them, 120 05:43.680 --> 05:47.920 or we could configure OSPF2, ignore that, and continue anyway. 121 05:47.920 --> 05:49.840 But by default the M-T-U needs to match. 122 05:49.840 --> 05:52.400 And then the P is for password. 123 05:52.400 --> 05:56.080 And password is way for me to remember that authentication has to be set up 124 05:56.080 --> 05:56.400 correctly. 125 05:56.400 --> 05:59.280 So if they have to agree on the type of authentication they're going to use, 126 05:59.280 --> 06:02.640 and if a password is set, of course that password would need to match as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 126 05:59.280 --> 06:02.640 and if a password is set, of course that password would need to match as well. 127 06:02.640 --> 06:06.640 Let me clean this up. Let's also chat about the negotiation of a 128 06:06.640 --> 06:10.000 neighbor ship. I don't think we've done too much elaboration on that yet 129 06:10.000 --> 06:11.840 as part of this course. 130 06:11.840 --> 06:18.080 Let's imagine that R1 and R2 have just had these two interfaces brought up at 131 06:18.080 --> 06:19.840 the exact same time. 132 06:19.840 --> 06:24.320 And prior to that there's no other router running OSPF on this segment. 133 06:24.320 --> 06:28.000 One fun way that I used to help remind myself of the process that we're going 134 06:28.000 --> 06:28.560 to go through 135 06:28.560 --> 06:35.760 to form an adjacency, a full adjacency between R1 and R2 is IT-LF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 135 06:28.560 --> 06:35.760 to form an adjacency, a full adjacency between R1 and R2 is IT-LF. 136 06:35.760 --> 06:40.000 So think about an LF like a character that works in IT, the IT-LF, 137 06:40.000 --> 06:42.000 that can help us remember the sequence. 138 06:42.000 --> 06:45.440 So initially we're going to have a down state between two neighbors. 139 06:45.440 --> 06:48.560 And then we're going to have an I, that's the first I here in IT. 140 06:48.560 --> 06:50.800 And that's the initialization or init state. 141 06:50.800 --> 06:54.000 And it happens when we receive the hello packet from a neighbor. 142 06:54.000 --> 06:55.760 Then the T is the two-way state. 143 06:55.760 --> 06:57.680 And that's when we get a hello message from a neighbor. 144 06:57.680 --> 06:59.360 And it includes our router ID. 145 06:59.360 --> 07:03.530 Meaning the neighbor is indicating that it knows about us in its hello messages WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 145 06:59.360 --> 07:03.530 Meaning the neighbor is indicating that it knows about us in its hello messages 146 07:03.530 --> 07:03.760 . 147 07:03.760 --> 07:05.360 And when that happens in the hello messages, 148 07:05.360 --> 07:08.320 if it indicates that there's no designated router on the segment, 149 07:08.320 --> 07:10.080 they'll go ahead and have an election. 150 07:10.080 --> 07:13.240 So I'm going to put it right here, that they're going to have an election for 151 07:13.240 --> 07:13.920 the DR. 152 07:13.920 --> 07:16.000 And then the other router, if there's only two in there, 153 07:16.000 --> 07:18.880 the other router will become the backup designated router. 154 07:18.880 --> 07:21.840 And then as we continue the process, the next three letters are LF. 155 07:21.840 --> 07:24.800 And the E reminds me of two elements. 156 07:24.800 --> 07:28.240 The X start where they're beginning to negotiate their relationship 157 07:28.240 --> 07:30.480 and start sending database description packets. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 07:28.240 --> 07:30.480 and start sending database description packets. 158 07:30.480 --> 07:32.720 And then that continues to the exchange state. 159 07:32.720 --> 07:36.350 And during that process, they're each identifying what they have in their 160 07:36.350 --> 07:37.040 database 161 07:37.040 --> 07:38.560 and what they need to share with the other. 162 07:38.560 --> 07:41.760 And presuming that all goes well, the next letter here is L. 163 07:41.760 --> 07:42.880 And that's the loading state. 164 07:42.880 --> 07:46.480 Which involves the device sending requests to the other side, 165 07:46.480 --> 07:48.000 asking for updates. 166 07:48.000 --> 07:51.120 So as part of that, there's links, date, requests, 167 07:51.120 --> 07:54.240 and links, date updates that are shared between those two routers. 168 07:54.240 --> 07:57.600 And once that's done and we have a synchronized copy of the database, 169 07:57.600 --> 07:59.280 that's when it goes to a full state, 170 07:59.280 --> 08:02.080 which I affectionately refer to as a full adjacency. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 170 07:59.280 --> 08:02.080 which I affectionately refer to as a full adjacency. 171 08:02.080 --> 08:05.200 And one method that we can use to see that in action is we could bring these 172 08:05.200 --> 08:06.800 interfaces down for a moment, 173 08:06.800 --> 08:10.080 gig 1, 0 here on R1 and gig 2, 0 here on R2, 174 08:10.080 --> 08:11.600 and then bring them up. 175 08:11.600 --> 08:14.660 And with a debug running, we could actually see the play by play what's 176 08:14.660 --> 08:15.120 happening. 177 08:15.120 --> 08:16.640 So let's take a moment and demonstrate that. 178 08:16.640 --> 08:20.000 So R1, gig 1, 0, and R2, gig 2, 0. 179 08:20.000 --> 08:21.360 So we'll get R1 here. 180 08:21.360 --> 08:24.000 And I just realized they don't have OSPF configured on those two routers. 181 08:24.000 --> 08:25.440 So let's do that real quick. 182 08:25.440 --> 08:28.960 I'm going to go ahead and take the configuration for R1, 183 08:28.960 --> 08:31.680 copy and just put it in for this demo. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 183 08:28.960 --> 08:31.680 copy and just put it in for this demo. 184 08:31.680 --> 08:33.360 And then we'll do the same thing for R2. 185 08:33.360 --> 08:37.120 So we'll get R2, grab its config for OSPF version 3, 186 08:37.120 --> 08:40.880 for address, family, IPv4, copy that, and paste that in. 187 08:40.880 --> 08:43.840 All right, then on R1, we'll go ahead and do a config T, 188 08:43.840 --> 08:46.160 interface, gig 1/0. 189 08:46.160 --> 08:48.000 Let's make sure we have the right interface there. 190 08:48.000 --> 08:49.440 We'll look at our diagram. 191 08:49.440 --> 08:52.960 So up on R1, the interface going over to R2 is gig 1, 0. 192 08:52.960 --> 08:55.520 And on R2 would be interface gig 2, 0. 193 08:55.520 --> 08:57.840 So I'm going to go ahead and shut this down here on R1. 194 08:57.840 --> 09:00.000 And we'll do a similar treatment to R2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 195 09:00.000 --> 09:03.200 but going over to its interface, gig 2/0, 196 09:03.200 --> 09:04.560 and typing and shut down. 197 09:04.560 --> 09:08.000 So before we bring the interfaces up, let's go ahead and do a debug here on R1. 198 09:08.000 --> 09:09.840 I'm going to do there because I'm in configuration mode. 199 09:09.840 --> 09:14.800 And we'll do a debug, OSPF version 3, adjacency, and detail. 200 09:14.800 --> 09:17.680 And it'll give us a bunch of information regarding what's going on. 201 09:17.680 --> 09:20.560 And then I'm going to go ahead and bring both interfaces up at the same time. 202 09:20.560 --> 09:25.120 That by just simply doing a no shut and an end and I need to add on R1 and R2. 203 09:25.120 --> 09:28.320 So I'm in interface configuration mode on both routers. 204 09:28.320 --> 09:31.120 So the no shut will bring both of them up at the same time. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 204 09:28.320 --> 09:31.120 So the no shut will bring both of them up at the same time. 205 09:31.120 --> 09:33.200 So we'll go ahead and send that out. 206 09:33.200 --> 09:34.560 And then we'll watch the debugs. 207 09:34.560 --> 09:35.840 And here they go. 208 09:35.840 --> 09:36.640 And I'm going to wait. 209 09:36.640 --> 09:39.040 It's going to take up to 40 seconds because they both came up. 210 09:39.040 --> 09:40.560 There's no DR present. 211 09:40.560 --> 09:43.680 So I'm going to go ahead and give this about 35 more seconds. 212 09:43.680 --> 09:45.840 And when it's done, I'll turn off the debug. 213 09:45.840 --> 09:49.760 And then we'll take a look at the play by play as shown by the debug. 214 09:49.760 --> 09:50.400 All right. 215 09:50.400 --> 09:51.760 I'm doing an undy bug all. 216 09:51.760 --> 09:55.120 And let's scroll to the top of this debug output. 217 09:55.120 --> 09:56.640 So it went into the two A state. 218 09:56.640 --> 10:00.400 And that's because here in R1, it saw hello messages coming in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 218 09:56.640 --> 10:00.400 And that's because here in R1, it saw hello messages coming in 219 10:00.400 --> 10:03.680 that indicated that R2 knew about R1. 220 10:03.680 --> 10:06.320 So then because there's no DR, BDR on the network, 221 10:06.320 --> 10:09.760 they begin the process of that election to decide who's going to be the DR and 222 10:09.760 --> 10:10.560 BDR. 223 10:10.560 --> 10:13.360 And this is R1 preparing the database exchange, 224 10:13.360 --> 10:16.080 which implies it was going through Xdart and Exchange. 225 10:16.080 --> 10:18.800 We then send a request to the 2222 router, 226 10:18.800 --> 10:19.760 which is R2. 227 10:19.760 --> 10:21.920 We received an update from 2222. 228 10:21.920 --> 10:23.680 And then when synchronized, we went to a full state. 229 10:23.680 --> 10:25.280 And at that point, we got the console message. 230 10:25.280 --> 10:27.040 We're going to the full adjacency with R2. 231 10:27.040 --> 10:31.520 It's also showing here the results of the DR BDR election. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 231 10:27.040 --> 10:31.520 It's also showing here the results of the DR BDR election. 232 10:31.520 --> 10:34.640 So the DR is 2222. 233 10:34.640 --> 10:37.040 And that's because they both have the same default priority 234 10:37.040 --> 10:38.480 on the segment of one. 235 10:38.480 --> 10:42.320 And the router ID for 2222 is higher. 236 10:42.320 --> 10:43.520 And that was the tiebreaker. 237 10:43.520 --> 10:45.280 So router 1 became the BDR. 238 10:45.280 --> 10:46.480 And then I turned off debuggy. 239 10:46.480 --> 10:50.640 So using the idea of IT-ELF, like an LF dressed up like an IT person, 240 10:50.640 --> 10:54.800 that can help us remember the process that you go through to negotiate. 241 10:54.800 --> 10:57.840 And if there's a problem, again, just think of STT, 242 10:57.840 --> 11:01.680 AMP, for all those parameters that need to match that we talked about a little WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 242 10:57.840 --> 11:01.680 AMP, for all those parameters that need to match that we talked about a little 243 11:01.680 --> 11:02.240 while ago. 244 11:02.240 --> 11:04.160 So the objectives for this set of videos 245 11:04.160 --> 11:07.680 is to give you the opportunity to see and then do some hands-on practice 246 11:07.680 --> 11:12.160 in configuring OSPF version 3 for IPv4 for that address family. 247 11:12.160 --> 11:14.960 I also want to walk you through sitting up a passive interface, 248 11:14.960 --> 11:18.240 which we've done previously with IPv6 and traditional IPv4. 249 11:18.240 --> 11:22.000 But this time, we're going to do it with OSPF version 3's implementation 250 11:22.000 --> 11:24.400 of routing for address family IPv4. 251 11:24.400 --> 11:26.800 I'd also like to walk you through sitting up a stub area 252 11:26.800 --> 11:30.560 in a totally stub area using OSPF V3 for IPv4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 252 11:26.800 --> 11:30.560 in a totally stub area using OSPF V3 for IPv4. 253 11:30.560 --> 11:33.120 And also walk through an example of doing summarization 254 11:33.120 --> 11:37.200 at the area border routers so that we're not setting all the LSA type 3s, 255 11:37.200 --> 11:38.640 but we can send a summary. 256 11:38.640 --> 11:41.760 And you can do summarizations, for example, from area 0, 257 11:41.760 --> 11:43.520 as it goes down here, here on R3, 258 11:43.520 --> 11:46.800 or you can summarize routes that are over here in area 2 259 11:46.800 --> 11:49.040 as the ring sent up into area 0. 260 11:49.040 --> 11:51.200 And the command to do that is the range command. 261 11:51.200 --> 11:52.880 And it's implemented a little bit differently 262 11:52.880 --> 11:55.520 because we're going to do it inside the router config 263 11:55.520 --> 11:57.680 inside of the appropriate address family. 264 11:57.680 --> 11:59.920 In this case, the address family for IPv4. 265 11:59.920 --> 12:01.360 So we have a lot on our plate. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 265 11:59.920 --> 12:01.360 So we have a lot on our plate. 266 12:01.360 --> 12:04.560 We're going to start the configuration for OSPF version 3 267 12:04.560 --> 12:07.440 for address family IPv4 in the very next video. 268 12:07.440 --> 12:09.600 So I'll see you there in just a moment.