WEBVTT 1 00:00.000 --> 00:04.800 Before we can begin doing ranges and summarization between backbone areas and 2 00:04.800 --> 00:06.160 non backbone areas or 3 00:06.160 --> 00:11.280 creating an area as a stub, what we need to do first is have IPv6's OSPF 4 00:11.280 --> 00:11.760 implemented. 5 00:11.760 --> 00:15.250 And that's what we're going to do in this video. So here is our topology 6 00:15.250 --> 00:16.080 diagram and we're going 7 00:16.080 --> 00:19.810 to pretty much mirror what we did with IPv4 in previous videos by having all 8 00:19.810 --> 00:21.360 the interfaces on R1, 9 00:21.360 --> 00:25.360 be associated with area zero, all the interfaces on R2, be associated with area 10 00:25.360 --> 00:25.680 zero, 11 00:25.680 --> 00:29.160 and then over here on R3 we'll have gig one zero and f8 four slash zero, be 12 00:29.160 --> 00:30.480 associated with OSPF WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:29.160 --> 00:30.480 associated with OSPF 13 00:30.480 --> 00:35.300 version three for area zero and these two interfaces four slash one and gig two 14 00:35.300 --> 00:36.720 zero here on R4 15 00:36.720 --> 00:40.320 will be associated with area zero and then this interface and this interface 16 00:40.320 --> 00:41.200 respectively will be 17 00:41.200 --> 00:45.870 an area one and area two and then our five all of its interfaces and on R7 all 18 00:45.870 --> 00:47.120 of its interfaces 19 00:47.120 --> 00:52.230 will be an area one. Well over here are six and our eight all of its interfaces 20 00:52.230 --> 00:52.720 will be associated 21 00:52.720 --> 00:56.160 with area two. So with that in mind let me walk through the configuration for 22 00:56.160 --> 00:59.120 OSPF V3 for IPv6. 23 00:59.120 --> 01:02.420 So here is our lab environment and at the tail end of the set of videos I'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:59.120 --> 01:02.420 So here is our lab environment and at the tail end of the set of videos I'll 24 01:02.420 --> 01:03.440 put you on a hands-on 25 01:03.440 --> 01:08.040 labs you two can get the practice working with configuring and verifying OSPF 26 01:08.040 --> 01:09.360 version three for 27 01:09.360 --> 01:13.700 IPv6. So if we double click on the topology here on the desktop to open it up 28 01:13.700 --> 01:14.880 there's our topology 29 01:14.880 --> 01:19.680 and we are going to be dealing with the IPv6 address space which is 2001 DB8678 30 01:19.680 --> 01:20.720 3 and then the 31 01:20.720 --> 01:24.220 red number represents each of these subnets and to get to the console of all of 32 01:24.220 --> 01:25.040 our routers we're 33 01:25.040 --> 01:28.570 going to do that through server one. So we'll double click here on server one 34 01:28.570 --> 01:29.200 and give that a moment 35 01:29.200 --> 01:32.510 to initialize and here it comes great great great and then we'll click on it to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:29.200 --> 01:32.510 to initialize and here it comes great great great and then we'll click on it to 36 01:32.510 --> 01:33.680 activate it there 37 01:33.680 --> 01:38.790 and here are the tabs for router one two three and just as a sanity check let's 38 01:38.790 --> 01:40.240 go to a router one 39 01:40.240 --> 01:45.120 and let's do a show IPv6 interface brief just to verify that we have the IPv6 40 01:45.120 --> 01:45.760 addresses that we think 41 01:45.760 --> 01:52.800 we do and so here on gig zero zero it's 2001 DB8673 one perfect on gig one zero 42 01:52.800 --> 01:53.600 that's the interface 43 01:53.600 --> 02:00.460 going over to our two its IP address is 2001 DB86783 12 and on gig two zero WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 01:53.600 --> 02:00.460 going over to our two its IP address is 2001 DB86783 12 and on gig two zero 44 02:00.460 --> 02:01.920 that's the interface going 45 02:01.920 --> 02:07.660 down to our three it has the IPv6 address starting with 2001 DB86783 13 46 02:07.660 --> 02:09.040 fantastic and if we take a 47 02:09.040 --> 02:12.770 peek at our topology that matches those respective subnets again everything 48 02:12.770 --> 02:15.520 starting with 2001 DB86783 49 02:15.520 --> 02:19.050 and then the red number here as part of the IPv4 address also is going to be 50 02:19.050 --> 02:21.600 the IPv6 subnet address as well 51 02:21.600 --> 02:26.400 so that looks great so I'll go ahead and exit out now if you want some help in 52 02:26.400 --> 02:27.920 configuring this 53 02:27.920 --> 02:32.230 let me share with you a text document externally open is this one right here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:27.920 --> 02:32.230 let me share with you a text document externally open is this one right here 54 02:32.230 --> 02:33.120 called OSPF 55 02:33.120 --> 02:38.320 configs if you scroll down in this text document here on server one dash nug 56 02:38.320 --> 02:39.440 there's a section for 57 02:39.440 --> 02:45.320 OSPF version three configuration and here it is so so this example is for both 58 02:45.320 --> 02:47.440 IPv4 and IPv6 and 59 02:47.440 --> 02:51.090 all we're concerned about right now is IPv6 so if we had routing process that 60 02:51.090 --> 02:51.920 we're running we 61 02:51.920 --> 02:55.440 could go ahead and remove those let me just verify coming back to our routers 62 02:55.440 --> 02:57.600 by doing a show IPv6 63 02:57.600 --> 03:03.350 protocols and just verify that currently we are not running OSPF for IPv6 but WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 02:57.600 --> 03:03.350 protocols and just verify that currently we are not running OSPF for IPv6 but 64 03:03.350 --> 03:04.080 we're about to change 65 03:04.080 --> 03:06.950 that so let me go ahead and go back to our text document here and let me share 66 03:06.950 --> 03:08.000 with you the example 67 03:08.000 --> 03:12.150 of further configuration here on r1 so we aren't configuring the address family 68 03:12.150 --> 03:13.200 for IPv4 so I'm 69 03:13.200 --> 03:17.670 going to go ahead and remove the interface commands to say that we want to 70 03:17.670 --> 03:19.760 enable OSPF for IPv4 71 03:19.760 --> 03:23.410 because we're not going to enable it here we're focused here primarily just on 72 03:23.410 --> 03:24.560 IPv6 so the syntax 73 03:24.560 --> 03:28.250 will be going into configuration mode typing router OSPF version three and then 74 03:28.250 --> 03:29.120 the process ID 75 03:29.120 --> 03:31.950 that we want to use for that routing process I'm going to use the auto cost WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 03:29.120 --> 03:31.950 that we want to use for that routing process I'm going to use the auto cost 76 03:31.950 --> 03:32.960 reference bandwidth 77 03:32.960 --> 03:37.400 across the board of 1000 and that way my gig of ethernet links look like a cost 78 03:37.400 --> 03:37.920 of one 79 03:37.920 --> 03:42.040 well fast to the net links look like a cost of 10 so then we go to each of the 80 03:42.040 --> 03:43.200 interfaces and in each 81 03:43.200 --> 03:46.790 interface we'd say OSPF version three the process ID that we used when we 82 03:46.790 --> 03:47.920 generated that and then 83 03:47.920 --> 03:53.270 specify IPv6 as opposed to IPv4 and then specify which area this interface 84 03:53.270 --> 03:55.600 belongs to so gig 000 gig 1 85 03:55.600 --> 04:00.290 0 and gig 2 0 are all going to be associated with area 0 on our one is I would WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 85 03:55.600 --> 04:00.290 0 and gig 2 0 are all going to be associated with area 0 on our one is I would 86 04:00.290 --> 04:01.440 encourage you to do a 87 04:01.440 --> 04:06.360 few of these manually just to verify your comfort with the commands and how to 88 04:06.360 --> 04:07.440 input it and then once 89 04:07.440 --> 04:09.890 you've done two or three routers and you're comfortable with it you can go 90 04:09.890 --> 04:11.440 ahead and use this text document 91 04:11.440 --> 04:15.240 and begin cutting and pasting so for example let's go to r1 let's do r1 92 04:15.240 --> 04:17.120 manually so here on r1 we 93 04:17.120 --> 04:20.830 got the right router fantastic let's go to configuration mode and type in 94 04:20.830 --> 04:23.840 router OSPF v3 space and let's use 95 04:23.840 --> 04:29.800 process ID one and I was excited it typed router wrong you'd think cca after 96 04:29.800 --> 04:31.600 two decades would never WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 96 04:29.800 --> 04:31.600 two decades would never 97 04:31.600 --> 04:35.990 type that incorrectly but there you go so router OSPF version three process ID 98 04:35.990 --> 04:37.360 one fantastic we're now in 99 04:37.360 --> 04:40.780 router configuration mode I'm also going to do the auto cost reference 100 04:40.780 --> 04:43.280 bandwidth set it to 1000 now 101 04:43.280 --> 04:46.990 that's done and that's going to apply to both IPv4 and IPv6 if you're config 102 04:46.990 --> 04:47.920 uring both then we'll 103 04:47.920 --> 04:52.190 go to our interfaces to enable those interfaces to participate as part of OSPF 104 04:52.190 --> 04:53.200 process ID one and 105 04:53.200 --> 04:58.940 assign them to area 0 so on our one is gig 0 0 gig 1 0 and gig 2 0 so we'll 106 04:58.940 --> 05:00.640 type an interface range WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 106 04:58.940 --> 05:00.640 type an interface range 107 05:00.640 --> 05:08.160 and do gig 0 slash 0 comma gig 1 slash 0 comma and gig 2 slash 0 press enter 108 05:08.160 --> 05:08.480 and now we're an 109 05:08.480 --> 05:11.730 interface range configuration for all three of those interfaces from here we 110 05:11.730 --> 05:12.880 can type in OSPF 111 05:12.880 --> 05:18.000 version three process ID one and space question mark and then we'll specify IPv 112 05:18.000 --> 05:19.600 6 space and then we'll 113 05:19.600 --> 05:23.000 specify what area this interface is going to go into so there's the area 114 05:23.000 --> 05:24.240 command right there so we'll 115 05:24.240 --> 05:28.790 type an area space and a question mark and we're going to specify the area so 116 05:28.790 --> 05:29.600 this is going to be the 117 05:29.600 --> 05:33.020 backbone area for those three interfaces and we're done so if I type in end WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 05:29.600 --> 05:33.020 backbone area for those three interfaces and we're done so if I type in end 118 05:33.020 --> 05:35.200 here and we do a show OSPF 119 05:35.200 --> 05:39.520 B3 interface brief press enter they're all in the weight state so there's ver 120 05:39.520 --> 05:40.320 ifying that there's 121 05:40.320 --> 05:44.420 no other DR out there and in just a moment or two once we get a few seconds 122 05:44.420 --> 05:46.000 they'll change to DR 123 05:46.000 --> 05:49.670 for all three of those ethernet interfaces as there's nobody else configured 124 05:49.670 --> 05:51.920 for IPv6's OSPF yet 125 05:51.920 --> 05:55.390 so it's been a moment let me hit the up arrow key and not quite long enough we 126 05:55.390 --> 05:56.320 're going to have to wait 127 05:56.320 --> 06:00.160 40 seconds that's the default dead interval and through the magic of editing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 127 05:56.320 --> 06:00.160 40 seconds that's the default dead interval and through the magic of editing 128 06:00.160 --> 06:00.640 that's probably 129 06:00.640 --> 06:04.720 been closer to 40 seconds now do the upper arrow key and press enter and now 130 06:04.720 --> 06:05.680 this router is a 131 06:05.680 --> 06:08.860 designated router on all three of those segments and just to remind ourselves 132 06:08.860 --> 06:10.080 of what those are 133 06:10.080 --> 06:15.120 that's gig 00 gig 1 0 and gig 2 0 now another thing I should point out is that 134 06:15.120 --> 06:16.400 if we're using OSPF 135 06:16.400 --> 06:22.960 V3 we'd also want to make sure that IPv6 unicast routing is enabled so for not 136 06:22.960 --> 06:23.600 sure of that we can 137 06:23.600 --> 06:27.370 just go into configuration mode and type in ipv6 unicast dash routing press 138 06:27.370 --> 06:28.640 enter and boom it's now 139 06:28.640 --> 06:32.200 enabled because without that OSPF version 3 whether we're using address WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 139 06:28.640 --> 06:32.200 enabled because without that OSPF version 3 whether we're using address 140 06:32.200 --> 06:34.640 families for IPv6 or IPv4 141 06:34.640 --> 06:38.240 it won't function as expected meaning it won't function so we need to make sure 142 06:38.240 --> 06:39.040 we're enabling 143 06:39.040 --> 06:42.800 IPv6 unicast routing if it's not on by default and that will vary a little bit 144 06:42.800 --> 06:43.760 based on the 145 06:43.760 --> 06:47.250 version and platform and router and iOS that you're running all right so let's 146 06:47.250 --> 06:47.920 do some basic 147 06:47.920 --> 06:52.590 show commands on router 1 we can do a show IPv6 protocols so now it's showing 148 06:52.590 --> 06:54.160 here that we have OSPF 149 06:54.160 --> 06:59.150 process ID 1 that's running fantastic there's our router ID we have one normal 150 06:59.150 --> 07:00.160 area and we have three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 150 06:59.150 --> 07:00.160 area and we have three 151 07:00.160 --> 07:05.260 interfaces associated with that area which is area 0 and if we did show IPv6 OS 152 07:05.260 --> 07:06.400 PF interface brief 153 07:06.400 --> 07:09.840 that command also is going to show us the interfaces now that's very similar 154 07:09.840 --> 07:10.800 check this out to this 155 07:10.800 --> 07:16.160 command show OSPF V3 interface brief so just be aware that some of the older 156 07:16.160 --> 07:17.360 show commands for IPv6 157 07:17.360 --> 07:22.800 OSPF routing may still work with the newer flavor or implementation of OSPF V3 158 07:22.800 --> 07:23.520 but also be aware that 159 07:23.520 --> 07:27.340 not all of those commands are going to work but some of them still do we'll 160 07:27.340 --> 07:29.120 give you a show OSPF V3 161 07:29.120 --> 07:32.750 all by itself press center and here's showing us the output we're running OSPF WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 161 07:29.120 --> 07:32.750 all by itself press center and here's showing us the output we're running OSPF 162 07:32.750 --> 07:34.240 V3 process ID 1 163 07:34.240 --> 07:38.660 and this is looking at the address family for IPv6 there's our router ID of 1.1 164 07:38.660 --> 07:40.080 .1.1 which is the 165 07:40.080 --> 07:43.990 highest IP address on a loopback interface I currently have here on our one is 166 07:43.990 --> 07:44.480 showing us the 167 07:44.480 --> 07:48.110 reference bandwidth right here of 1000 megabits per second because I set that 168 07:48.110 --> 07:48.560 and if we hit 169 07:48.560 --> 07:51.800 space bar going down a bit further we have one area and that's our area 0 the 170 07:51.800 --> 07:52.480 backbone it's 171 07:52.480 --> 07:56.260 currently showing inactive because there's no other OSPF speakers on that 172 07:56.260 --> 07:57.600 network segment so next 173 07:57.600 --> 08:01.820 let's go to r2 which is give me a very similar configuration so on r2 in fact WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 173 07:57.600 --> 08:01.820 let's go to r2 which is give me a very similar configuration so on r2 in fact 174 08:01.820 --> 08:02.560 let me go to my 175 08:02.560 --> 08:06.480 note pad real quick and here on r2 I'm going to go ahead and remove the 176 08:06.480 --> 08:07.840 configuration for the 177 08:07.840 --> 08:11.640 address family IPv4 on the interfaces again because we're focused here on IPv6 178 08:11.640 --> 08:13.120 only so effectively 179 08:13.120 --> 08:18.180 it configurations identical to what we had over on r1 all the interfaces gig 0 180 08:18.180 --> 08:20.000 0 gig 1 0 and gig 2 0 181 08:20.000 --> 08:25.090 are going to become OSPF enabled for IPv6 with OSPF version 3 and putting those 182 08:25.090 --> 08:26.480 interfaces in area 0 183 08:26.480 --> 08:30.760 so we'll right click copy go to r2 and paste it in and we should get a neighbor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 183 08:26.480 --> 08:30.760 so we'll right click copy go to r2 and paste it in and we should get a neighbor 184 08:30.760 --> 08:32.480 adjacency between us 185 08:32.480 --> 08:37.120 and r1 which is showing up right there and that's because r1 had already been 186 08:37.120 --> 08:37.680 established as the 187 08:37.680 --> 08:42.350 DR for the segment and r2 saw that that DR was there and they agreed on terms 188 08:42.350 --> 08:43.280 and they became 189 08:43.280 --> 08:48.110 fully adjacent neighbors so if we did a show IPv6 protocols impress enter is 190 08:48.110 --> 08:48.960 showing us the interfaces 191 08:48.960 --> 08:54.060 associated with error 0 right here we did show OSPF V3 interface brief it'll 192 08:54.060 --> 08:55.040 show us our interfaces 193 08:55.040 --> 08:59.280 in their states so gig 1 0 and 0 0 should be DR is here in just a few moments 194 08:59.280 --> 09:00.400 the dead interval for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 194 08:59.280 --> 09:00.400 the dead interval for 195 09:00.400 --> 09:03.920 ethernet is 40 seconds so if we wait that 40 seconds there's the other two 196 09:03.920 --> 09:05.280 interfaces right there 197 09:05.280 --> 09:08.860 where there's no other speakers and as a result r2 1 the DR election we'll be 198 09:08.860 --> 09:10.720 to a show OSPF V3 199 09:10.720 --> 09:15.220 database now we type that in this can show us both IPv4 and IPv6 if you have 200 09:15.220 --> 09:15.760 both address 201 09:15.760 --> 09:20.570 families configured but since we don't have IPv4 configured on this device we 202 09:20.570 --> 09:21.200 can just do a show 203 09:21.200 --> 09:25.250 OSPF V3 database or if you wanted to filter it out just to IPv6 right here we 204 09:25.250 --> 09:26.080 have the option of 205 09:26.080 --> 09:31.510 saying IPv6 and then we can type in database and press enter so here are lsa WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 205 09:26.080 --> 09:31.510 saying IPv6 and then we can type in database and press enter so here are lsa 206 09:31.510 --> 09:32.720 type ones from each 207 09:32.720 --> 09:38.460 of the routers here's our lsa type 2 where r1 is the advertising router and we 208 09:38.460 --> 09:39.920 don't have yet any lsa 209 09:39.920 --> 09:44.380 type 3s and that's because we don't yet have any other interfaces inside of any 210 09:44.380 --> 09:45.680 other areas besides 211 09:45.680 --> 09:51.100 area 0 then we have the IPv6 specific lsa is the type 8 right here and the lsa 212 09:51.100 --> 09:52.240 type 9 right here 213 09:52.240 --> 09:57.040 so if we do a show IPv6 OSPF neighbors impress enter here it's showing us our 214 09:57.040 --> 09:58.000 neighbor another 215 09:58.000 --> 10:02.910 by seeing that same output is using this show OSPF V3 IPv6 neighbor impressing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 215 09:58.000 --> 10:02.910 by seeing that same output is using this show OSPF V3 IPv6 neighbor impressing 216 10:02.910 --> 10:03.920 enter and it's the 217 10:03.920 --> 10:08.640 same results so again some of the legacy commands with traditional IPv6 OSPF 218 10:08.640 --> 10:10.400 version 3 they still work 219 10:10.400 --> 10:14.950 but this is the more current way of showing the OSPF V3 IPv6 neighbors with 220 10:14.950 --> 10:16.320 this command right here 221 10:16.320 --> 10:20.000 all right so let's continue and let's make our way down to r3 which is the area 222 10:20.000 --> 10:21.040 border router 223 10:21.040 --> 10:24.480 so if we go back to our notes here and go down to r3 the biggest difference 224 10:24.480 --> 10:25.360 here is that we're 225 10:25.360 --> 10:30.260 going to have at least one interface in area 0 and we have to actually gig 1 0 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 225 10:25.360 --> 10:30.260 going to have at least one interface in area 0 and we have to actually gig 1 0 226 10:30.260 --> 10:31.520 and f a 4 0 and then 227 10:31.520 --> 10:35.570 one other interface in a different area in this case area 1 and I'm going to 228 10:35.570 --> 10:36.720 remove the address 229 10:36.720 --> 10:40.270 family for IPv4 I'm not going to work and configure that on each of the 230 10:40.270 --> 10:41.440 interfaces so I'm going to go 231 10:41.440 --> 10:45.580 ahead and remove the IPv4 component here because once again we're just focused 232 10:45.580 --> 10:46.720 on IPv6 so here's our 233 10:46.720 --> 10:51.680 configuration for r3 and right click on it copy and we'll go to r3 and paste it 234 10:51.680 --> 10:52.400 in and it should 235 10:52.400 --> 10:57.060 have a neighbor ship come up right away between it and r1 which it does right 236 10:57.060 --> 10:58.160 there we can verify 237 10:58.160 --> 11:03.800 that with a show OSPF V3 IPv6 neighbor and that should verify it as well and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 237 10:58.160 --> 11:03.800 that with a show OSPF V3 IPv6 neighbor and that should verify it as well and 238 11:03.800 --> 11:04.720 then look at our 239 11:04.720 --> 11:09.550 interfaces we can do a show OSPF V3 interface brief just like that and verify 240 11:09.550 --> 11:11.120 our local interfaces 241 11:11.120 --> 11:14.850 and their current state so this one's the BDR that's where we're partnering up 242 11:14.850 --> 11:16.000 with r1 and the other 243 11:16.000 --> 11:20.960 two interfaces which are both ethernet which are f a 4 0 and 4 1 after a moment 244 11:20.960 --> 11:21.840 we should be the DR 245 11:21.840 --> 11:25.900 on both those segments as well because there's no other yet configured OSPF 246 11:25.900 --> 11:26.880 speakers so we'll go 247 11:26.880 --> 11:30.330 ahead and hit the up arrow key press enter and sure enough we have the DR for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 247 11:26.880 --> 11:30.330 ahead and hit the up arrow key press enter and sure enough we have the DR for 248 11:30.330 --> 11:31.600 those other two segments 249 11:31.600 --> 11:35.650 all right let's continue with r4 so r4 is very similar I'm going to remove 250 11:35.650 --> 11:37.600 again the interface 251 11:37.600 --> 11:42.130 address family IPv4 enablement here so it's just the IPv6 only so in this 252 11:42.130 --> 11:43.200 router we have 300 253 11:43.200 --> 11:48.430 interfaces that are participating in area 0 and we have one interface serial 3- 254 11:48.430 --> 11:48.960 1 that's going to 255 11:48.960 --> 11:54.380 be participating in area 2 so we'll go ahead and copy that right click copy and 256 11:54.380 --> 11:54.880 then go ahead 257 11:54.880 --> 11:58.670 and paste it in and we should get our neighbor jsonc both with r2 which is a 258 11:58.670 --> 11:59.840 message right here 259 11:59.840 --> 12:06.400 and also r3 then we can verify the show OSPF V3 neighbors and show OSPF V3 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 259 11:59.840 --> 12:06.400 and also r3 then we can verify the show OSPF V3 neighbors and show OSPF V3 260 12:06.400 --> 12:08.400 interface brief so here 261 12:08.400 --> 12:12.360 on gig 0 0 we're still waiting the dead interval just to verify that we don't 262 12:12.360 --> 12:13.040 have a DR out there 263 12:13.040 --> 12:16.960 already and then once we waited at least 40 seconds there that should go ahead 264 12:16.960 --> 12:18.480 and turn to a DR 265 12:18.480 --> 12:21.520 our responsibility on the gig 00 on r4. 266 12:21.520 --> 12:25.080 And if you look at our topology, gig 00 is not shown 267 12:25.080 --> 12:27.640 on r4, but there is a gig 00 interface, 268 12:27.640 --> 12:29.120 and that's what it's currently waiting on. 269 12:29.120 --> 12:32.080 So if we go back to r4, hit the upper key in press center. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 269 12:29.120 --> 12:32.080 So if we go back to r4, hit the upper key in press center. 270 12:32.080 --> 12:34.560 Sure enough, it's the DR on its gig 00. 271 12:34.560 --> 12:36.500 And here on r4, if we do a show, IPv6 route, 272 12:36.500 --> 12:39.760 for OSPF from press center, here's our OSPF routes. 273 12:39.760 --> 12:43.940 So we've got the 1 subnet and the 2 subnet and the 12 subnet 274 12:43.940 --> 12:46.820 and the 13 subnet and the 35 subnet. 275 12:46.820 --> 12:48.380 And notice here the 35 subnet. 276 12:48.380 --> 12:51.420 If you look at our topology, that's the subnet right over here. 277 12:51.420 --> 12:55.380 That subnet, based on the interface FAA4/1 on r3, 278 12:55.380 --> 12:56.900 that's associated with area 1. 279 12:56.900 --> 13:00.220 And that's why over here on r4, that subnet of 35 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 279 12:56.900 --> 13:00.220 And that's why over here on r4, that subnet of 35 280 13:00.220 --> 13:02.340 is showing up as an inter-area route. 281 13:02.340 --> 13:07.020 Also, that means if we here on r4 did a show, OSPF v3, 282 13:07.020 --> 13:09.340 IPv6 database, and press center. 283 13:09.340 --> 13:12.660 Now we have our LSA type ones for area 0, 284 13:12.660 --> 13:16.660 our LSA type 2's for area 0, and we'll get on a bit further 285 13:16.660 --> 13:18.980 what used to be called the summary LSAs, 286 13:18.980 --> 13:23.340 the type 3 LSAs in IPv4, the LSA 3's for IPv6, 287 13:23.340 --> 13:25.380 are referred to as inter-area prefix, 288 13:25.380 --> 13:26.540 and thus we have right here. 289 13:26.540 --> 13:29.300 So r3 is advertising the 35 network, 290 13:29.300 --> 13:32.100 and r4 is advertising the 46 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 290 13:29.300 --> 13:32.100 and r4 is advertising the 46 network. 291 13:32.100 --> 13:36.260 So if we look at our topology, the 35 is over here in area 1. 292 13:36.260 --> 13:40.100 And the 46 subnet is over between our 4 and r6. 293 13:40.100 --> 13:42.540 And then once again, we have the LSA types 8 and 9, 294 13:42.540 --> 13:46.820 which are unique to IPv6's implementation of OSPF v3. 295 13:46.820 --> 13:49.460 And as we continue on, it's now starting to show us the details 296 13:49.460 --> 13:53.700 we're going to the LSA type ones and twos and threes for area 2. 297 13:53.700 --> 13:56.460 And that's because r4, which we're currently sitting at, 298 13:56.460 --> 13:58.820 has an interface in both of those areas. 299 13:58.820 --> 14:01.340 And as a result, it has the LSAs for everything that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 299 13:58.820 --> 14:01.340 And as a result, it has the LSAs for everything that's 300 14:01.340 --> 14:04.140 in area 0, and also everything that's in area 2. 301 14:04.140 --> 14:05.900 All right, let's continue our configuration. 302 14:05.900 --> 14:09.020 Now here on r5, I'm going to remove the IPv4 portion again 303 14:09.020 --> 14:10.340 from the notepad document. 304 14:10.340 --> 14:13.420 And let's configure OSPF v3, process ID1 on r5, 305 14:13.420 --> 14:16.260 and all of its interfaces are in area 1. 306 14:16.260 --> 14:17.900 So we'll go ahead and go to r5. 307 14:17.900 --> 14:18.500 And away we go. 308 14:18.500 --> 14:19.740 And again, when you do the hands-on lab, 309 14:19.740 --> 14:22.780 feel free to do two or three routers manually. 310 14:22.780 --> 14:24.180 And if you want to save a little bit of time, 311 14:24.180 --> 14:26.260 once you're comfortable with the commands and the show commands, 312 14:26.260 --> 14:29.340 you can go ahead and start doing it from the notepad document. 313 14:29.340 --> 14:30.700 So we'll go to r6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 313 14:29.340 --> 14:30.700 So we'll go to r6. 314 14:30.700 --> 14:33.220 r6 has all of its interfaces in area 2. 315 14:33.220 --> 14:35.900 I want to go ahead and remove the IPv4 portion here, 316 14:35.900 --> 14:38.020 because we're focusing only on IPv6 here. 317 14:38.020 --> 14:39.500 And we'll copy that. 318 14:39.500 --> 14:42.740 Right click, make sure on the right tab for r6 and paste it in. 319 14:42.740 --> 14:43.660 And that looks good. 320 14:43.660 --> 14:46.540 And we'll continue down to r7 on the left hand side. 321 14:46.540 --> 14:48.740 All of its interfaces are in area 1. 322 14:48.740 --> 14:52.420 So I'm going to enable just IPv6 and not IPv4. 323 14:52.420 --> 14:54.180 So we'll go ahead and copy that. 324 14:54.180 --> 14:56.340 And go to r7 and paste it in. 325 14:56.340 --> 14:58.620 Now, last one is r8. 326 14:58.620 --> 15:01.380 All of its interfaces are going to be in area 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 326 14:58.620 --> 15:01.380 All of its interfaces are going to be in area 2. 327 15:01.380 --> 15:04.460 And just put in IPv6 OSPF version 3. 328 15:04.460 --> 15:05.740 So we do a copy. 329 15:05.740 --> 15:08.860 And then go to r8, right click, and paste it in. 330 15:08.860 --> 15:11.260 And then from here, let's do a couple of quick verifications. 331 15:11.260 --> 15:12.620 So here is our topology. 332 15:12.620 --> 15:16.180 And so r8 should know about all the routes in area 0, 333 15:16.180 --> 15:18.300 all the routes in area 1, because we 334 15:18.300 --> 15:20.420 have the area border route or r4, 335 15:20.420 --> 15:23.140 advertising all those LSA type 3s down to us. 336 15:23.140 --> 15:25.660 So here on r8, let's do a few basic checks show, 337 15:25.660 --> 15:27.860 OSPF v3, interface brief. 338 15:27.860 --> 15:29.620 Right, we have two interfaces. 339 15:29.620 --> 15:32.020 Gig 00 is about to become the DR. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 339 15:29.620 --> 15:32.020 Gig 00 is about to become the DR. 340 15:32.020 --> 15:34.060 That's the one facing up to the right hand, bottom right 341 15:34.060 --> 15:35.180 hand side of our topology. 342 15:35.180 --> 15:36.260 So we'll give that a few moments. 343 15:36.260 --> 15:39.380 And just confirm that goes to a DR state for gig 00. 344 15:39.380 --> 15:41.060 And again, that would take up to 40 seconds 345 15:41.060 --> 15:42.620 if there isn't a DR already on that segment. 346 15:42.620 --> 15:43.580 Fantastic. 347 15:43.580 --> 15:44.980 Then regarding neighbor ships, we 348 15:44.980 --> 15:49.060 can do a show, OSPF v3, neighbor, and press enter. 349 15:49.060 --> 15:50.580 And just by typing in neighbor, that's going 350 15:50.580 --> 15:53.620 to show me neighbors for address family IPv4, 351 15:53.620 --> 15:55.540 if it's configured and IPv6. 352 15:55.540 --> 15:56.940 Or we could do this. 353 15:56.940 --> 15:58.860 If you have both running ones, you just one of the sets. 354 15:58.860 --> 16:03.620 We can do a show, OSPF v3, and then type in IPv6 space neighbor. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 354 15:58.860 --> 16:03.620 We can do a show, OSPF v3, and then type in IPv6 space neighbor. 355 16:03.620 --> 16:06.740 And that will limit the output just to IPv6 address family 356 16:06.740 --> 16:07.380 neighbors. 357 16:07.380 --> 16:10.660 So the router with the router ID of 6666, which is R6, 358 16:10.660 --> 16:11.740 is our neighbor. 359 16:11.740 --> 16:12.900 We have full adjacency. 360 16:12.900 --> 16:14.740 And that router is a DR. 361 16:14.740 --> 16:18.460 So locally on that interface, passing it 4/1, 362 16:18.460 --> 16:21.300 we are the BDR, as shown right here, as we looked at our local 363 16:21.300 --> 16:22.180 interfaces. 364 16:22.180 --> 16:23.900 And router 6 is acting as the DR. 365 16:23.900 --> 16:26.020 And that's because the DR was already in place, 366 16:26.020 --> 16:28.740 because we configured our six a few minutes ago. 367 16:28.740 --> 16:29.900 So now if we looked at the-- 368 16:29.900 --> 16:34.940 so we did a show OSPF v3, IPv6 database, impressed enter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 368 16:29.900 --> 16:34.940 so we did a show OSPF v3, IPv6 database, impressed enter. 369 16:34.940 --> 16:38.700 Here we can see we have in area 2, we have three router 370 16:38.700 --> 16:41.220 LSAs coming from the three routers in that area. 371 16:41.220 --> 16:43.380 We have one net link state. 372 16:43.380 --> 16:44.940 That's the LSA type 2. 373 16:44.940 --> 16:47.660 In this case, coming from R6 for a common segment, 374 16:47.660 --> 16:50.180 where we have two routers connected to that segment. 375 16:50.180 --> 16:53.100 And if you'd like a little bit, here are all the LSA type 3s 376 16:53.100 --> 16:56.260 that are being sent into area 2 by router 4. 377 16:56.260 --> 16:59.180 And over here on the right is showing us the exact prefixes 378 16:59.180 --> 17:02.980 that are being advertised in those respective LSA type 3s. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 378 16:59.180 --> 17:02.980 that are being advertised in those respective LSA type 3s. 379 17:02.980 --> 17:05.620 So if we did a show IPv6 route, and I'm 380 17:05.620 --> 17:08.860 going to tag on OSPF, we just OSPF learned routes, 381 17:08.860 --> 17:09.780 impressed enter. 382 17:09.780 --> 17:12.580 Here are OSPF learned routes on R8, 383 17:12.580 --> 17:14.100 and at the space bar to continue. 384 17:14.100 --> 17:16.460 So right here is the seven network, 385 17:16.460 --> 17:19.580 and that is the network where R7 is directly connected. 386 17:19.580 --> 17:23.660 So if we look at our topology, 2001 DB867837 network 387 17:23.660 --> 17:27.820 is the one off of R7s gig 00, where PC7 is. 388 17:27.820 --> 17:29.500 So we should be able to, if everything's working, 389 17:29.500 --> 17:31.820 and every has a correct default gateway setup, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 389 17:29.500 --> 17:31.820 and every has a correct default gateway setup, 390 17:31.820 --> 17:33.980 we should be able to ping, for example, 391 17:33.980 --> 17:40.780 from PC8 over at 2001 DB86783 colon colon 10 over to PC7 392 17:40.780 --> 17:41.940 at whatever its IP address is. 393 17:41.940 --> 17:43.020 Let's verify that real quick. 394 17:43.020 --> 17:44.580 So here is PC7. 395 17:44.580 --> 17:49.420 If we do a show IPv6 on this little virtual machine, 396 17:49.420 --> 17:53.820 here's its IPv6 address, 2001 DB867837 colon colon 10. 397 17:53.820 --> 17:54.540 I'll copy that. 398 17:54.540 --> 17:56.980 We'll go over to PC8, which has the IP address 399 17:56.980 --> 18:00.220 of 2001 DB8678, colon colon 10. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 399 17:56.980 --> 18:00.220 of 2001 DB8678, colon colon 10. 400 18:00.220 --> 18:05.220 And let's do a ping, and I'll paste in the IP address of PC7, 401 18:05.220 --> 18:06.780 and that's working. 402 18:06.780 --> 18:09.340 Let's also do a trace, just to verify that. 403 18:09.340 --> 18:12.500 So we'll do a trace, space, and paste in that same 404 18:12.500 --> 18:15.060 destination address, and that's gonna show us the path 405 18:15.060 --> 18:17.140 that's taking based on this last octet. 406 18:17.140 --> 18:20.020 So R8 is the first router, and then went to R6, 407 18:20.020 --> 18:21.820 based on the last octet, and then four, 408 18:21.820 --> 18:25.740 and then R2, and then R1, and R3, and five, and seven, 409 18:25.740 --> 18:28.140 until finally it landed at the final destination, 410 18:28.140 --> 18:29.340 which is PC7. 411 18:29.340 --> 18:31.700 We can also do the same types of tests from the routers. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 411 18:29.340 --> 18:31.700 We can also do the same types of tests from the routers. 412 18:31.700 --> 18:34.980 So here at R8, for example, we could do a ping. 413 18:34.980 --> 18:39.820 Let's take R7, and just do a quick show IPv6, 414 18:39.820 --> 18:41.220 interface brief. 415 18:41.220 --> 18:42.780 Take a look at its IP addresses. 416 18:42.780 --> 18:45.900 So this IP address right there is off gig 0, on R7. 417 18:45.900 --> 18:48.460 So I'm gonna copy that, go back to R8, 418 18:48.460 --> 18:50.380 and let's not do a ping, let's do a trace. 419 18:50.380 --> 18:54.620 Let's trace all the way to that address on R7, 420 18:54.620 --> 18:56.980 and that's another way of verifying our connectivity 421 18:56.980 --> 18:58.100 through the entire network. 422 18:58.100 --> 19:01.180 Now, just like in IPv4's implementation of OSPF, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 422 18:58.100 --> 19:01.180 Now, just like in IPv4's implementation of OSPF, 423 19:01.180 --> 19:04.540 if we want to have a passive interface with IPv6, 424 19:04.540 --> 19:07.060 using OSPFB3, we can do that as well, 425 19:07.060 --> 19:09.220 and I'll walk through that in the very next video. 426 19:09.220 --> 19:11.260 So I'll see you there in just a moment.