WEBVTT 1 00:00.000 --> 00:03.840 So I have reset the lab environment for the walkthrough and here's our tasks. 2 00:03.840 --> 00:08.860 We are to configure OSPF version 3 for address family IPv4 as shown in the top 3 00:08.860 --> 00:09.280 ology. 4 00:09.280 --> 00:13.440 And then once we verify basic connectivity, they want us to go ahead and update 5 00:13.440 --> 00:14.720 area 2 and make it a 6 00:14.720 --> 00:19.270 totally stubby area. And then the final task here is on our three, the area 7 00:19.270 --> 00:20.480 border router between 8 00:20.480 --> 00:25.540 the backbone area and area 1, summarize area 0 routes that begin with 10, 0 9 00:25.540 --> 00:26.480 anything to a 10 00:26.480 --> 00:32.140 /16 and advertise that summary into area 1. So with those lab tasks in mind, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:26.480 --> 00:32.140 /16 and advertise that summary into area 1. So with those lab tasks in mind, 11 00:32.140 --> 00:32.720 let's go to the lab 12 00:32.720 --> 00:36.330 environment and let's do this walkthrough. And here we go and start off by 13 00:36.330 --> 00:37.680 bringing up the topology 14 00:37.680 --> 00:40.590 here on the desktop. That looks great and then we'll go ahead and open up 15 00:40.590 --> 00:41.920 server 1 nug right here 16 00:41.920 --> 00:45.590 by simply double clicking on server 1 dash nug and we'll give that just a 17 00:45.590 --> 00:47.040 moment to initialize. 18 00:47.040 --> 00:53.120 Fantastic there it is. So we do show IP protocols and show IPv6 protocols just 19 00:53.120 --> 00:53.840 to confirm we aren't 20 00:53.840 --> 00:57.680 running any routing protocols yet. So let me pick it up to topology again and 21 00:57.680 --> 00:58.240 let's start our 22 00:58.240 --> 01:02.260 configuration on our one. So on our one, here's the configuration we're going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 00:58.240 --> 01:02.260 configuration on our one. So on our one, here's the configuration we're going 23 01:02.260 --> 01:03.200 to deploy. So I have 24 01:03.200 --> 01:06.300 it here in my notepad document that's on the desktop if you want to use that 25 01:06.300 --> 01:07.360 for reference. So on our 26 01:07.360 --> 01:11.850 one, we're going to go into configuration mode, start the router process for OS 27 01:11.850 --> 01:13.440 PF V3, process ID1, 28 01:13.440 --> 01:16.720 set the auto cost reference bandwidth to 1000 and that way our gigabit links 29 01:16.720 --> 01:17.680 look like a better 30 01:17.680 --> 01:20.990 or lower cost than the fast Ethernet. And then for these three interfaces, we 31 01:20.990 --> 01:22.000 'll place all three of 32 01:22.000 --> 01:28.730 them in area zero as part of address family IPv4 within OSPF V3, process ID1. 33 01:28.730 --> 01:29.440 So I'm going to take that 34 01:29.440 --> 01:33.590 configuration for our one, copy it to my clipboard and then go to our one and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:29.440 --> 01:33.590 configuration for our one, copy it to my clipboard and then go to our one and 35 01:33.590 --> 01:34.640 paste it in. And then I 36 01:34.640 --> 01:37.820 going to repeat that process for the other routers as well. So the syntax for 37 01:37.820 --> 01:38.880 our two will be virtually 38 01:38.880 --> 01:42.750 identical because all of its interfaces are in area zero. So we'll go to our 39 01:42.750 --> 01:43.840 two, paste that in. 40 01:43.840 --> 01:47.850 And then our three is our first area border router and let's look at the top 41 01:47.850 --> 01:49.040 ology and that is 42 01:49.040 --> 01:54.040 right here. So it has two interfaces in area zero and one interface here in 43 01:54.040 --> 01:55.200 area one, which is going 44 01:55.200 --> 01:58.540 to make it an area border router. So we'll take the configuration for that, 45 01:58.540 --> 02:00.080 copy it and paste it in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 01:58.540 --> 02:00.080 copy it and paste it in 46 02:00.080 --> 02:04.280 here on R3. And I'll repeat that process for our four, five, six, seven, and 47 02:04.280 --> 02:05.520 eight. Now when you do 48 02:05.520 --> 02:09.710 the hands on lab, I would encourage you at least for a couple of the routers, 49 02:09.710 --> 02:11.040 just do it by hand, 50 02:11.040 --> 02:13.600 make sure you're comfortable with the commands. And then once you've done it a 51 02:13.600 --> 02:14.560 few dozen times, 52 02:14.560 --> 02:17.630 feel free to start using the text document for copy and paste once you're 53 02:17.630 --> 02:18.800 comfortable with the commands. 54 02:18.960 --> 02:23.120 So we'll go on to our four, go to our four, paste it in, go to our five, take 55 02:23.120 --> 02:24.400 the configuration 56 02:24.400 --> 02:28.080 for that. All of its interfaces are in area one. So we'll copy that, go to our 57 02:28.080 --> 02:29.040 five, paste it in, 58 02:29.040 --> 02:33.690 and then we'll go to our six. All of its interfaces are in area two. So we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 02:29.040 --> 02:33.690 and then we'll go to our six. All of its interfaces are in area two. So we'll 59 02:33.690 --> 02:34.800 copy that config, 60 02:34.800 --> 02:38.280 go to our six, paste it in. And the next one is our seven. All of its 61 02:38.280 --> 02:39.920 interfaces are in area one. 62 02:39.920 --> 02:43.860 So we'll copy that, put in our buffer and paste it in on our seven. And then 63 02:43.860 --> 02:44.560 last router is 64 02:44.560 --> 02:48.400 router eight. And all of its interfaces are in area two. So we'll grab that 65 02:48.400 --> 02:49.360 part of the config, 66 02:49.360 --> 02:54.380 copy, go to our eight, and right click, and boom. Now we've got it. So what are 67 02:54.380 --> 02:55.040 some of the commands 68 02:55.040 --> 02:59.920 we could use to verify OSPF version three? Well, we could do a show OSPF V3 69 02:59.920 --> 03:01.280 press enter. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 02:59.920 --> 03:01.280 press enter. So 70 03:01.280 --> 03:05.870 here it's enabled for address family IPv4. We could do a show run, pipe section 71 03:05.870 --> 03:06.880 router. And that will 72 03:06.880 --> 03:10.630 show us the configuration that we have on this router for OSPF V3. This is like 73 03:10.630 --> 03:11.200 a truncated 74 03:11.200 --> 03:14.490 my output a little bit. So we'll do a show run, pipe section router again. 75 03:14.490 --> 03:16.240 Fantastic. Maybe do a show 76 03:16.240 --> 03:20.960 OSPF V3 database. Now if you only want to see the IPv4 or IPv6, if we were 77 03:20.960 --> 03:22.400 running both address families, 78 03:22.400 --> 03:26.550 we could put before the word database, we could specify IPv4 or IPv6. If we don 79 03:26.550 --> 03:27.200 't specify, 80 03:27.200 --> 03:31.310 it'll show you all of it. So it's currently we only have IPv4, address family WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 80 03:27.200 --> 03:31.310 it'll show you all of it. So it's currently we only have IPv4, address family 81 03:31.310 --> 03:32.240 setup. So here's our 82 03:32.240 --> 03:37.360 LSA type ones, the router LSAs, LSA type twos by the DRs. And then we have the 83 03:37.360 --> 03:38.400 enter area prefix 84 03:38.400 --> 03:41.640 link states. And effectively those are the LSA type threes, which in the 85 03:41.640 --> 03:42.880 traditional flavor of 86 03:42.880 --> 03:48.170 OSPF for IPv4, those are called summary LSAs. And effectively, they're all the 87 03:48.170 --> 03:48.800 networks that are 88 03:48.800 --> 03:54.260 being advertised into area two by the ABR. In this case, that ABR is router 89 03:54.260 --> 03:55.440 four. And of course, 90 03:55.440 --> 04:01.370 we also do show IP route and then OSPF V3. And so see OSPF V3, learned routes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 03:55.440 --> 04:01.370 we also do show IP route and then OSPF V3. And so see OSPF V3, learned routes. 91 04:01.370 --> 04:02.320 And there are 92 04:02.320 --> 04:06.800 inter area routes. And we have one intra area route right there. And that's the 93 04:06.800 --> 04:08.720 network between our four 94 04:08.720 --> 04:12.620 and our six. And we look at our topology, we can confirm that as well. 95 04:12.620 --> 04:14.080 Fantastic. So if we want a 96 04:14.080 --> 04:18.440 ping, we could try a ping across the network. We could ping from, for example, 97 04:18.440 --> 04:20.080 PC8 down on the 192.168. 98 04:20.080 --> 04:25.080 One network over to PC7, over on the 1017 network. Let's go and do that. So let 99 04:25.080 --> 04:25.840 's go out of the tab 100 04:25.840 --> 04:34.400 here for PC8. And we'll do a ping to 10.1.7.10. And that's working. So they've WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 100 04:25.840 --> 04:34.400 here for PC8. And we'll do a ping to 10.1.7.10. And that's working. So they've 101 04:34.400 --> 04:37.280 been traced to 10.1.7.10. 102 04:37.280 --> 04:41.040 Let's show the exact path going through our eight, our six, our four, our two, 103 04:41.040 --> 04:41.920 our one, our three, 104 04:41.920 --> 04:45.520 our five. And then finally, hit the destination at our seven. We can also use 105 04:45.520 --> 04:46.720 this PC, the client 106 04:46.720 --> 04:51.320 and egg machine at 10.0.1.50. It's reachable right here in the upper and corner 107 04:51.320 --> 04:52.400 . So we double click 108 04:52.400 --> 04:57.930 here on client and egg, open up a window there. It's IP addresses 10.0.1.50. So 109 04:57.930 --> 04:59.040 let's ping that PC7 110 04:59.040 --> 05:03.530 address again. So I remember what it is is 10.1.7.10. And that seems to be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 04:59.040 --> 05:03.530 address again. So I remember what it is is 10.1.7.10. And that seems to be 111 05:03.530 --> 05:05.040 working. We could also do a 112 05:05.040 --> 05:09.110 trace from a Windows computer that's spelled TRACRT. And we'll do a dash G if 113 05:09.110 --> 05:10.320 you don't bother doing name 114 05:10.320 --> 05:15.190 resolution. And we'll trace to 10.1.7.10. Let's be going through our one or 115 05:15.190 --> 05:16.720 three or five or seven 116 05:16.720 --> 05:20.330 to help find a hits the destination. And there we have it. Fantastic. So we go 117 05:20.330 --> 05:21.520 ahead and close client 118 05:21.520 --> 05:26.770 nug. And let's take a look at our next task. So now that OSPFE3 for IPv4 is set 119 05:26.770 --> 05:27.920 up and working, 120 05:27.920 --> 05:32.310 now they want to configure area two as a totally stubby area. So let's do that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 120 05:27.920 --> 05:32.310 now they want to configure area two as a totally stubby area. So let's do that 121 05:32.310 --> 05:33.200 next. So what we're 122 05:33.200 --> 05:36.870 going to do is on our four, our six and our eight. We're going to specify the 123 05:36.870 --> 05:39.200 area two is a stub area. 124 05:39.200 --> 05:42.420 And then at the area of border router, we're going to add the keyword no dash 125 05:42.420 --> 05:43.680 summary after that. 126 05:43.680 --> 05:48.560 So it's not going to send all the detailed LSA type threes. It'll simply send a 127 05:48.560 --> 05:49.440 default route. 128 05:49.440 --> 05:52.250 And that's it. So let's configure multiple routers at the same time. Let's go 129 05:52.250 --> 05:54.160 to our four right here. 130 05:54.160 --> 05:56.840 And let's also use this icon right here. This is going to give us the 131 05:56.840 --> 05:58.480 opportunity to send multiple 132 05:58.480 --> 06:02.210 commands to multiple routers simultaneously. So if we do a config T and then a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 05:58.480 --> 06:02.210 commands to multiple routers simultaneously. So if we do a config T and then a 133 06:02.210 --> 06:03.760 router, OSPFE3, 134 06:03.760 --> 06:08.710 process ID1. And then right here we can do the area two stub if we wanted to. 135 06:08.710 --> 06:08.960 And that would 136 06:08.960 --> 06:13.430 apply to both address families for IPv6 and IPv4. Or if we want to do it just 137 06:13.430 --> 06:15.040 for the address family 138 06:15.040 --> 06:21.200 for IPv4, we type in address family and a shortcut there for IPv4, unit cast. 139 06:21.200 --> 06:21.840 And then here if we say 140 06:21.840 --> 06:27.280 area two stub that'll apply just for the IPv4 address family and it won't apply 141 06:27.280 --> 06:28.400 to both IPv4 and 142 06:28.400 --> 06:33.420 IPv6. So let's go ahead and send it over to our four, our six and our eight. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 06:28.400 --> 06:33.420 IPv6. So let's go ahead and send it over to our four, our six and our eight. 143 06:33.420 --> 06:34.000 And with those three 144 06:34.000 --> 06:37.720 routers selected, we'll click on send. So now it's just a stub area. Not 145 06:37.720 --> 06:39.680 totally stub, just a stub area. 146 06:39.680 --> 06:44.100 So if we were to go down to for example our eight and type in end here and if 147 06:44.100 --> 06:45.520 we did a show IP route, 148 06:45.520 --> 06:50.890 OSPFE3 and press dinner, here now we have our default route, which is an LSA 149 06:50.890 --> 06:52.320 type three that the 150 06:52.320 --> 06:55.890 area border router advertised. But we still have our inter area routes because 151 06:55.890 --> 06:56.640 all we're really doing 152 06:56.640 --> 07:01.710 is filtering out any external LSAs LSA type fives. So if we want to make this a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 152 06:56.640 --> 07:01.710 is filtering out any external LSAs LSA type fives. So if we want to make this a 153 07:01.710 --> 07:02.640 totally stub area 154 07:02.640 --> 07:06.440 and also filter out all the additional LSA type threes with the exception of 155 07:06.440 --> 07:07.440 the default route, 156 07:07.440 --> 07:11.470 we can go back to our four and hit the up arrow key and the address family for 157 07:11.470 --> 07:12.800 IPv4. And so we say area 158 07:12.800 --> 07:18.610 two stub space, no summary and boom, it is done. We've just specified that this 159 07:18.610 --> 07:20.480 is a totally stub area. 160 07:20.480 --> 07:24.800 So we do a show OSPFE3 here at the area border router. Here's showing that I 161 07:24.800 --> 07:26.480 have two areas, one normal 162 07:26.480 --> 07:30.290 area, that's the backbone area and one stub area, that's area two. And in the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 162 07:26.480 --> 07:30.290 area, that's the backbone area and one stub area, that's area two. And in the 163 07:30.290 --> 07:31.440 detail here for area two, 164 07:31.440 --> 07:35.500 it says it's a stub and by the way, no summary LSAs are being sent into this 165 07:35.500 --> 07:36.880 area. Meaning none of the 166 07:36.880 --> 07:41.370 detailed routes from outside area two. And we hit the up arrow key. What we 167 07:41.370 --> 07:42.320 should expect to see is 168 07:42.320 --> 07:45.900 all the inter area routes with the exception of the default route should no 169 07:45.900 --> 07:47.360 longer be here. And boom, 170 07:47.360 --> 07:51.840 they're gone. But do we still have connectivity? Let's go ahead and do a trace 171 07:51.840 --> 07:53.360 and let's trace over to 172 07:53.360 --> 07:59.180 PC7. The address there is 10.1.7.10 and that should still fly all the way 173 07:59.180 --> 08:00.720 around the network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 173 07:59.180 --> 08:00.720 around the network. 174 08:00.720 --> 08:04.400 Awesome. Are we done? Let's take a look at our tasks and the answer is nope, we 175 08:04.400 --> 08:05.200 got one more. 176 08:05.200 --> 08:09.610 On our three, summarize area zero, 10 zero networks as they're being advertised 177 08:09.610 --> 08:11.120 into area one. So we'll use 178 08:11.120 --> 08:15.390 the range command and the address family for IPv4 to go ahead and set up that 179 08:15.390 --> 08:16.960 summary route. So let's go 180 08:16.960 --> 08:20.070 to the correct router and that's going to be our three where we're going to 181 08:20.070 --> 08:21.680 that summary. So we'll go to 182 08:21.680 --> 08:25.680 our three and to save us a little bit of typing, let's do a show run, pipe, 183 08:25.680 --> 08:26.800 section router. And then we'll 184 08:26.800 --> 08:30.640 go into configuration mode. Then we'll go into router configuration for OSPFE3, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 184 08:26.800 --> 08:30.640 go into configuration mode. Then we'll go into router configuration for OSPFE3, 185 08:30.640 --> 08:32.640 process ID1. And then 186 08:32.640 --> 08:36.330 further more we'll go into address family IPv4 unicast. And then here we'll set 187 08:36.330 --> 08:38.080 up the summary. So the 188 08:38.080 --> 08:41.830 routes that we're trying to summarize from are in area zero. So we'll save for 189 08:41.830 --> 08:42.960 area zero. I want to go 190 08:42.960 --> 08:48.700 ahead and use 10.0.0.0 with a 16 bit mask. So that'll be in dotted decimal 255. 191 08:48.700 --> 08:50.720 25. Oh, you know what? 192 08:50.720 --> 08:54.980 I think I do that every time I do it. I think the word range, I say the word 193 08:54.980 --> 08:55.920 range, and if I often 194 08:55.920 --> 08:59.390 don't put in range space and that's one of the benefits of using context 195 08:59.390 --> 09:01.040 sensitive help occasionally WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 195 08:59.390 --> 09:01.040 sensitive help occasionally 196 09:01.040 --> 09:05.050 and we'll use zero zero. And that effectively is going to set up a summary of 197 09:05.050 --> 09:06.720 10.0 anything 198 09:06.720 --> 09:11.410 and any more detailed LSAs that match that range are not going to be sent 199 09:11.410 --> 09:12.960 through to area one. So 200 09:12.960 --> 09:16.830 let's do a question mark and that looks great. So now if we are to go down to 201 09:16.830 --> 09:17.920 one of the routers, 202 09:17.920 --> 09:21.560 let's take a look at our topology. Let's go down to router five. It should no 203 09:21.560 --> 09:22.240 longer see the 204 09:22.240 --> 09:28.520 detailed 10.0.13 or 10.0.12 or 10.0.34. But instead it should see that one 10.0 205 09:28.520 --> 09:29.920 slash 16. summary 206 09:29.920 --> 09:34.540 being advertised here by our three. So let's go to our five and verify that. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 206 09:29.920 --> 09:34.540 being advertised here by our three. So let's go to our five and verify that. So 207 09:34.540 --> 09:35.440 here on our five 208 09:35.440 --> 09:40.620 we'll do a show IP route for OSPF V3 learned routes, press enter, and sure 209 09:40.620 --> 09:41.760 enough there is our 210 09:41.760 --> 09:45.040 summary route and the other detailed routes. And let's take a look at this real 211 09:45.040 --> 09:45.840 quick. The detailed 212 09:45.840 --> 09:50.890 routes for 10.0.12, the 10.0.13 and 10.0.24 are all being summarized into the 213 09:50.890 --> 09:52.720 10.0/16. So thanks for 214 09:52.720 --> 09:56.960 joining me in this set of videos as we've taken a look at working with routing 215 09:56.960 --> 09:58.640 for IPv4 using the 216 09:58.640 --> 10:04.380 address family for IPv4 under the umbrella and process of OSPF version three. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 216 09:58.640 --> 10:04.380 address family for IPv4 under the umbrella and process of OSPF version three. 217 10:04.380 --> 10:05.120 And I look forward to 218 10:05.120 --> 10:08.290 seeing you in another set of videos very, very soon. And until then, I hope 219 10:08.290 --> 10:09.840 this has been informative 220 10:09.840 --> 10:12.320 and I'd like to thank you for viewing.