WEBVTT 1 00:00.000 --> 00:03.960 So for configuring OSPF version three to support the address 2 00:03.960 --> 00:07.440 family IPv4, we are going to go into router configuration mode 3 00:07.440 --> 00:13.200 for the routers with the command router OSPF V3 space and then our 4 00:13.200 --> 00:16.600 process number. So we can use process one or process two, whatever 5 00:16.600 --> 00:19.400 number you want to use there is fine. I'll put little spaces here 6 00:19.400 --> 00:22.400 as well. And then once we configure that, we then go into the 7 00:22.400 --> 00:25.800 interfaces associated with that router and then specify they 8 00:25.800 --> 00:30.200 want them to join that OSPF version three process ID and assign WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:25.800 --> 00:30.200 want them to join that OSPF version three process ID and assign 9 00:30.200 --> 00:33.480 which area those interfaces belong to. It's also important to be 10 00:33.480 --> 00:37.960 aware that these interfaces were running OSPF V3 for IPv4. Those 11 00:37.960 --> 00:42.360 interfaces have to be enabled for IPv6 because behind the scenes, 12 00:42.360 --> 00:46.800 they are actually using multicast addresses IPv6, multicast 13 00:46.800 --> 00:50.040 addresses to communicate back and forth in center. Hello. So if 14 00:50.040 --> 00:53.880 IPv6 is not enabled on the interfaces behind the scenes, OSPF 15 00:53.880 --> 00:57.720 version three will not support routing for IPv4. So to repeat 16 00:57.720 --> 01:00.120 that process over and over for each of the routers. So on our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:57.720 --> 01:00.120 that process over and over for each of the routers. So on our 17 01:00.120 --> 01:03.440 three, this interface and this interface would be an area zero, 18 01:03.440 --> 01:06.720 this interface to be an area one, zero three such one over here 19 01:06.720 --> 01:11.040 would be an area two and gig two zero and F a four such one 20 01:11.040 --> 01:14.080 being area zero and all the interfaces on our one and all the 21 01:14.080 --> 01:16.800 interfaces on our two would be an area zero. And these 22 01:16.800 --> 01:19.920 serial links right here, there and there, we are not using 23 01:19.920 --> 01:23.080 them initially as part of our OSPF routing domain. We're 24 01:23.080 --> 01:26.720 only including the interfaces encompassed by the areas area zero, 25 01:26.720 --> 01:30.040 area one and area two. So with that in mind, let's walk through the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:26.720 --> 01:30.040 area one and area two. So with that in mind, let's walk through the 26 01:30.040 --> 01:33.600 configuration of OSPF version three to support the address 27 01:33.600 --> 01:37.160 family of IPv4. So to do that, we are back in the lab environment. 28 01:37.160 --> 01:40.400 Now I already configured on our one and our two, some of the 29 01:40.400 --> 01:43.720 IPv6 routing with OSPF version three. So I'm going to go ahead and 30 01:43.720 --> 01:46.360 take my notepad document here. I'm going to scroll to the very 31 01:46.360 --> 01:48.880 top of it. So I'm going to go ahead and take that off. So I 32 01:48.880 --> 01:51.840 really only need the no router OSPF version three one. So I 33 01:51.840 --> 01:54.280 really only need this command right there. So I'm going to go ahead and 34 01:54.280 --> 01:58.560 take that, copy it. I'm going to use this icon right there and 35 01:58.560 --> 02:03.800 go into configuration mode and say do a control V and end. And I WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:58.560 --> 02:03.800 go into configuration mode and say do a control V and end. And I 36 02:03.800 --> 02:06.640 want to apply that to our one and our two. So I'll send that 37 02:06.640 --> 02:10.800 script. And now I've removed OSPF from router one and router two. 38 02:10.800 --> 02:14.400 Fantastic. So I would encourage you as you're configuring, if 39 02:14.400 --> 02:16.680 you want to use this notepad document, it's called OSPF 40 02:16.680 --> 02:20.800 configs. It's sitting right here on the desktop of server one 41 02:20.800 --> 02:24.360 dash nugged. That's where our multi tab buddy is as well. So if 42 02:24.360 --> 02:27.440 you'd like to use it as a help or a guide, that sounds great. 43 02:27.440 --> 02:30.800 But I would encourage you to at least do two or three routers WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:27.440 --> 02:30.800 But I would encourage you to at least do two or three routers 44 02:30.800 --> 02:34.400 manually by hand. And if you want to copy paste the rest, feel 45 02:34.400 --> 02:37.880 free to do so. So in this notepad document, if we scroll down, 46 02:37.880 --> 02:42.360 I'm actually going near the bottom. I have a section called OSPF 47 02:42.360 --> 02:46.600 V3 with IPv4 only. And that has the configuration. So basically 48 02:46.600 --> 02:50.200 is router OSPF V3 plus Citi one on all of them. I'm doing 49 02:50.200 --> 02:53.080 auto cost reference bandwidth to be a thousand on all routers. 50 02:53.080 --> 02:56.400 And that way my gigabit links look better cost wise than a fast 51 02:56.400 --> 03:00.640 ether link. And then I'm going to the relevant interfaces and enabling WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 02:56.400 --> 03:00.640 ether link. And then I'm going to the relevant interfaces and enabling 52 03:00.640 --> 03:04.960 them for OSPF address family IPv4. And then assigning the correct 53 03:04.960 --> 03:10.440 area area zero for our one are two all area zero also are three two 54 03:10.440 --> 03:15.160 interfaces in area zero and one interface in area one. So we take 55 03:15.160 --> 03:19.080 look at our topology and look at our three gig one zero and F a 56 03:19.080 --> 03:23.040 four zero or can mean area zero and F a four slash one is in area 57 03:23.040 --> 03:26.360 one. So I'm going to scroll the top of this grab those configs 58 03:26.360 --> 03:29.480 and put them in. So here's our one will go back to multi tab 59 03:29.480 --> 03:33.080 buddy. Make sure on the right tab paste it in and then repeat that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:29.480 --> 03:33.080 buddy. Make sure on the right tab paste it in and then repeat that 60 03:33.080 --> 03:37.240 process for our two and our three and our four et cetera, all 61 03:37.240 --> 03:40.640 the way down to our eight. So I'll go ahead and do that right 62 03:40.640 --> 03:43.200 now. All right. So let's now configure. So we did a spot check. 63 03:43.200 --> 03:47.160 Let's go to our four and this couldn't do a show run section 64 03:47.160 --> 03:50.360 router just to confirm we have so router OSPF version three 65 03:50.360 --> 03:53.600 process ID one the auto cost for our span with such a thousand 66 03:53.600 --> 03:58.000 across all routers and by default is showing us address family IPv4 67 03:58.000 --> 04:01.680 unit cast and that's because we enabled the interfaces for OSPF WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 03:58.000 --> 04:01.680 unit cast and that's because we enabled the interfaces for OSPF 68 04:01.680 --> 04:06.000 version three plus the D1 for IPv4 and assign them an area. So if we 69 04:06.000 --> 04:10.480 also went back and assigned an interface to address family IPv6, 70 04:10.480 --> 04:13.280 it would automatically show that additional category here as 71 04:13.280 --> 04:17.800 well case in point if we go to interface gig two slash zero and we 72 04:17.800 --> 04:21.880 hit that per key a few times and instead of saying OSPF B3 73 04:21.880 --> 04:27.720 process ID one IPv4 if we said IPv6 and press enter. Then we exit 74 04:27.720 --> 04:31.120 out and do a show run. I section router. You'll notice that it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 74 04:27.720 --> 04:31.120 out and do a show run. I section router. You'll notice that it 75 04:31.120 --> 04:34.480 has the additional address family section now. There for us. So if 76 04:34.480 --> 04:36.720 we need to go make changes or work specifically in those 77 04:36.720 --> 04:39.840 address families, they'll be there for us. And because our focus 78 04:39.840 --> 04:42.880 is IPv4 only only go back into that interface, which is 79 04:42.880 --> 04:46.760 gig two zero and I'm going to go ahead and say no. OSPF version 80 04:46.760 --> 04:51.000 three, press say D1 IPv6 area two. And that way I'm not adding 81 04:51.000 --> 04:54.720 additional OSPF version three routing for address family IPv6. 82 04:54.720 --> 04:58.640 We're just focused here on IPv4. So to test our connectivity, 83 04:58.640 --> 05:03.520 let's go, you know what server one nug has an IP address of 192, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 04:58.640 --> 05:03.520 let's go, you know what server one nug has an IP address of 192, 84 05:03.520 --> 05:09.440 161.100. It should have a deep hole gateway of dot eight. And 85 05:09.480 --> 05:12.680 server one nug is actually this computer right here that we're 86 05:12.680 --> 05:15.320 using with multi tab putty. So if we bring up a command prompt 87 05:15.320 --> 05:22.440 here on server one nug and type in ping to 192.168.1.8. And this 88 05:22.440 --> 05:25.000 is verify that's our rates address real quick. So here's our 89 05:25.000 --> 05:31.880 eight to show IP interface brief and survey says 192 168.1.8 is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 05:25.000 --> 05:31.880 eight to show IP interface brief and survey says 192 168.1.8 is 90 05:31.880 --> 05:35.240 our eight gig zero zero interface address, which is this one 91 05:35.240 --> 05:38.240 right here facing towards server one nug. So if we go back to 92 05:38.240 --> 05:41.200 server one nug and go back to the command prompt and we try to 93 05:41.200 --> 05:45.080 ping that address. That's a very good sign. And based on our 94 05:45.080 --> 05:48.880 topology, if routing is working correctly, we should from server 95 05:48.880 --> 05:51.680 one nug over here on the far bottom right of our topology, we 96 05:51.680 --> 05:56.720 should be able to ping and trace over to PC seven, which is 10.1.7.10. 97 05:56.720 --> 06:01.640 So let's try that next. Let's do a ping to 10.1.7.10. Survey says WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 97 05:56.720 --> 06:01.640 So let's try that next. Let's do a ping to 10.1.7.10. Survey says 98 06:01.640 --> 06:05.200 that works. And let's do a trace. So on a Windows computer, 99 06:05.200 --> 06:07.840 trace is spelled a little bit funny. You can bring this up a 100 06:07.840 --> 06:11.440 little higher. So we can see it. So it's T-R-A-C-E-R-T and a 101 06:11.440 --> 06:14.040 Windows computer will do -D if you don't bother doing name 102 06:14.040 --> 06:17.760 resolution. And then we'll get that same destination of 10.1.7.10 103 06:17.760 --> 06:21.920 press enter. And our first hop is dot eight, which is 104 06:21.920 --> 06:25.160 router eight, then dot six, which is router six, then four and 105 06:25.160 --> 06:28.480 two and one and three and five and seven until we got to the 106 06:28.480 --> 06:31.960 final destination of that PC. So our path through the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 106 06:28.480 --> 06:31.960 final destination of that PC. So our path through the 107 06:31.960 --> 06:35.680 network seems to be working. And that's all due to OSPF 108 06:35.720 --> 06:39.480 version three with support for address family IPv4. So if we go 109 06:39.480 --> 06:42.760 back to router eight, for example, let's do a few show commands. 110 06:42.760 --> 06:48.360 Let's show IP route OSPF now be for press enter. I mean, if 111 06:48.360 --> 06:52.040 you worked with OSPF and IPv4 for a long time, this command 112 06:52.040 --> 06:55.720 should show you the IP routes that are learned via OSPF. But 113 06:55.720 --> 06:59.360 the problem is they're not learned via quote unquote OSPF. 114 06:59.360 --> 07:03.160 They're actually learned via OSPF version three. So we do a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 114 06:59.360 --> 07:03.160 They're actually learned via OSPF version three. So we do a 115 07:03.160 --> 07:07.600 show IP route OSPF V3. That's then going to show us the routes 116 07:07.600 --> 07:11.200 that were learned via OSPF version three for address family IPv4. 117 07:11.200 --> 07:14.880 So there's the IA is the inter area routes. And we have one local 118 07:14.880 --> 07:18.520 route in area two. And that's the 10 to 46 network. And that's 119 07:18.520 --> 07:22.520 the network between our four and our six. Also, if we did a 120 07:22.520 --> 07:26.760 debug OSPF V3 hello, impressed enter, I just want you to 121 07:26.760 --> 07:30.800 notice what addresses are used for the multicast addresses as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 07:26.760 --> 07:30.800 notice what addresses are used for the multicast addresses as 122 07:30.800 --> 07:33.520 they're setting hello back and forth. And that'll be good. I'll do an 123 07:33.520 --> 07:38.160 unall turn off debugging. Take a look at this FF 02 colon colon five. 124 07:38.160 --> 07:42.760 That's the all OSPF routers for OSPF version three with a 125 07:42.760 --> 07:46.360 multicast address in the world of IPv6. And if we are sending a 126 07:46.360 --> 07:50.800 message to a designated router, it'd be FF 02 colon colon six. 127 07:50.800 --> 07:52.880 But I just want to make sure you're aware that behind the scenes, 128 07:52.880 --> 07:57.400 if we don't have IPv6 enabled on the interfaces, OSPF version 129 07:57.400 --> 08:01.160 three will not support IPv4 routing because behind the scenes, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 129 07:57.400 --> 08:01.160 three will not support IPv4 routing because behind the scenes, 130 08:01.160 --> 08:04.760 it's using IPv6 multicast addresses. All right. So let's take a 131 08:04.760 --> 08:08.920 look at a few other show commands. We need to show OSPF V3 space 132 08:08.920 --> 08:13.120 question mark. So if you want to see just the IPv4 address family 133 08:13.120 --> 08:17.720 stuff, you can type in IPv4. And then you can say interface and 134 08:17.720 --> 08:20.360 we'll go ahead and say brief press center. And that'll show us 135 08:20.360 --> 08:24.640 just for IPv4 address family, the OSPF version three enabled 136 08:24.640 --> 08:27.640 interfaces and their current status. So those two interfaces are 137 08:27.640 --> 08:31.600 participating in OSPF version three for address family IPv4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 137 08:27.640 --> 08:31.600 participating in OSPF version three for address family IPv4. 138 08:31.600 --> 08:35.720 They're both part of OSPF V3 process ID1 and they're both 139 08:35.720 --> 08:38.720 associated with area two. So here's confirming the address 140 08:38.720 --> 08:42.520 family. And there's the cost for our fast ethernet versus our 141 08:42.520 --> 08:46.600 gigabit ethernet. And currently this router, our eight is the 142 08:46.600 --> 08:50.000 designated router for both of the segments. And off of the F a 143 08:50.000 --> 08:53.680 four slash one, we have one fully adjacent neighbor. So the F is 144 08:53.680 --> 08:57.080 for fully adjacent and the C is for count. So one neighbor is 145 08:57.080 --> 08:59.480 there and we are fully adjacent with that neighbor. The see 146 08:59.480 --> 09:04.120 those neighbors, we can do a show OSPF version three IPv4 neighbor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 08:59.480 --> 09:04.120 those neighbors, we can do a show OSPF version three IPv4 neighbor 147 09:04.120 --> 09:07.960 press center. And that will show us our neighbors for IPv4. Now 148 09:07.960 --> 09:11.320 if we were running IPv6 also you just swap out the IPv4 typev6. 149 09:11.320 --> 09:14.560 And that would show you the IPv6 address family neighbor 150 09:14.560 --> 09:18.120 jacencies. So our neighbors router ID is 6666. They have a 151 09:18.120 --> 09:22.760 full adjacency and it is a BDR. And that's because we are the 152 09:22.760 --> 09:27.120 DR as shown right here. If you're going to do a show OSPF V3 153 09:27.120 --> 09:30.000 without any other options is press enter, that will confirm our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 154 09:30.000 --> 09:33.360 router ID locally is showing us the process ID, which address 155 09:33.360 --> 09:36.240 family were supporting. We have one normal area. And that's 156 09:36.240 --> 09:39.560 area two. There's two interfaces in the area. And our reference 157 09:39.560 --> 09:43.320 bandwidth, we bumped up from the default of 102 1000. If we do a 158 09:43.320 --> 09:47.400 show IPv6 protocols that indicates that OSPF process ID one is 159 09:47.400 --> 09:50.080 running, although behind the scenes is not just the traditional 160 09:50.080 --> 09:55.040 OSPF, it literally is OSPF V3. And if you want to see the OSPF 161 09:55.040 --> 10:00.040 V3 database, we do show OSPF V3 space. And then if you want to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 161 09:55.040 --> 10:00.040 V3 database, we do show OSPF V3 space. And then if you want to 162 10:00.040 --> 10:04.600 see both IPv4 and IPv6, you can just go ahead and not specify 163 10:04.600 --> 10:07.400 either one just put in database. Now in our case, we only have 164 10:07.400 --> 10:11.600 IPv4. So it's only going to show us the OSPF V3 database for 165 10:11.600 --> 10:14.960 IPv4. So here's our LSA type ones. We have three of them 166 10:14.960 --> 10:18.720 because we have three routers in area two. Here we have one 167 10:19.080 --> 10:22.440 network link state LSA, that's the LSA type two generated by 168 10:22.440 --> 10:26.040 the DR. And that's 8888 where there's two or more routers on 169 10:26.040 --> 10:28.640 that common segment. So our eight is generating the net link 170 10:28.640 --> 10:33.160 state. That's the LSA type two. And then we have multiple LSA type WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 170 10:28.640 --> 10:33.160 state. That's the LSA type two. And then we have multiple LSA type 171 10:33.160 --> 10:37.600 threes as shown right here. So an IPv4's traditional OSPF that 172 10:37.600 --> 10:41.640 would be called summary LSAs and IPv6. The LSA type three is 173 10:41.640 --> 10:44.520 recalled inter area prefix link states. And effectively 174 10:44.520 --> 10:48.080 showing us all the LSAs that the ABR rather four has 175 10:48.080 --> 10:51.800 advertised into area two. And then because we're running OSPF 176 10:51.800 --> 10:56.080 version three, we also have LSA type eights as shown here and LSA 177 10:56.080 --> 11:00.240 type nines. Even though we're only supporting IPv4 unicast WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 177 10:56.080 --> 11:00.240 type nines. Even though we're only supporting IPv4 unicast 178 11:00.240 --> 11:02.640 routing that address family, we're still going to have the 179 11:02.640 --> 11:06.720 LSA types eights and nines. So another we've set up OSPF V3 to 180 11:06.720 --> 11:09.760 support the address family for IPv4. In the next video, I'd 181 11:09.760 --> 11:12.960 like to walk you through how we set up a passive interface with 182 11:12.960 --> 11:14.360 OSPF V3.