So for configuring OSPF version three to support the address
family IPv4, we are going to go into router configuration mode
for the routers with the command router OSPF V3 space and then our
process number. So we can use process one or process two, whatever
number you want to use there is fine. I'll put little spaces here
as well. And then once we configure that, we then go into the
interfaces associated with that router and then specify they
want them to join that OSPF version three process ID and assign WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
want them to join that OSPF version three process ID and assign
which area those interfaces belong to. It's also important to be
aware that these interfaces were running OSPF V3 for IPv4. Those
interfaces have to be enabled for IPv6 because behind the scenes,
they are actually using multicast addresses IPv6, multicast
addresses to communicate back and forth in center. Hello. So if
IPv6 is not enabled on the interfaces behind the scenes, OSPF
version three will not support routing for IPv4. So to repeat
that process over and over for each of the routers. So on our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that process over and over for each of the routers. So on our
three, this interface and this interface would be an area zero,
this interface to be an area one, zero three such one over here
would be an area two and gig two zero and F a four such one
being area zero and all the interfaces on our one and all the
interfaces on our two would be an area zero. And these
serial links right here, there and there, we are not using
them initially as part of our OSPF routing domain. We're
only including the interfaces encompassed by the areas area zero,
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
area one and area two. So with that in mind, let's walk through the
configuration of OSPF version three to support the address
family of IPv4. So to do that, we are back in the lab environment.
Now I already configured on our one and our two, some of the
IPv6 routing with OSPF version three. So I'm going to go ahead and
take my notepad document here. I'm going to scroll to the very
top of it. So I'm going to go ahead and take that off. So I
really only need the no router OSPF version three one. So I
really only need this command right there. So I'm going to go ahead and
take that, copy it. I'm going to use this icon right there and
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
go into configuration mode and say do a control V and end. And I
want to apply that to our one and our two. So I'll send that
script. And now I've removed OSPF from router one and router two.
Fantastic. So I would encourage you as you're configuring, if
you want to use this notepad document, it's called OSPF
configs. It's sitting right here on the desktop of server one
dash nugged. That's where our multi tab buddy is as well. So if
you'd like to use it as a help or a guide, that sounds great.
But I would encourage you to at least do two or three routers WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But I would encourage you to at least do two or three routers
manually by hand. And if you want to copy paste the rest, feel
free to do so. So in this notepad document, if we scroll down,
I'm actually going near the bottom. I have a section called OSPF
V3 with IPv4 only. And that has the configuration. So basically
is router OSPF V3 plus Citi one on all of them. I'm doing
auto cost reference bandwidth to be a thousand on all routers.
And that way my gigabit links look better cost wise than a fast
ether link. And then I'm going to the relevant interfaces and enabling WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
ether link. And then I'm going to the relevant interfaces and enabling
them for OSPF address family IPv4. And then assigning the correct
area area zero for our one are two all area zero also are three two
interfaces in area zero and one interface in area one. So we take
look at our topology and look at our three gig one zero and F a
four zero or can mean area zero and F a four slash one is in area
one. So I'm going to scroll the top of this grab those configs
and put them in. So here's our one will go back to multi tab
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
buddy. Make sure on the right tab paste it in and then repeat that
process for our two and our three and our four et cetera, all
the way down to our eight. So I'll go ahead and do that right
now. All right. So let's now configure. So we did a spot check.
Let's go to our four and this couldn't do a show run section
router just to confirm we have so router OSPF version three
process ID one the auto cost for our span with such a thousand
across all routers and by default is showing us address family IPv4
unit cast and that's because we enabled the interfaces for OSPF WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
unit cast and that's because we enabled the interfaces for OSPF
version three plus the D1 for IPv4 and assign them an area. So if we
also went back and assigned an interface to address family IPv6,
it would automatically show that additional category here as
well case in point if we go to interface gig two slash zero and we
hit that per key a few times and instead of saying OSPF B3
process ID one IPv4 if we said IPv6 and press enter. Then we exit
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
out and do a show run. I section router. You'll notice that it
has the additional address family section now. There for us. So if
we need to go make changes or work specifically in those
address families, they'll be there for us. And because our focus
is IPv4 only only go back into that interface, which is
gig two zero and I'm going to go ahead and say no. OSPF version
three, press say D1 IPv6 area two. And that way I'm not adding
additional OSPF version three routing for address family IPv6.
We're just focused here on IPv4. So to test our connectivity,
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
let's go, you know what server one nug has an IP address of 192,
161.100. It should have a deep hole gateway of dot eight. And
server one nug is actually this computer right here that we're
using with multi tab putty. So if we bring up a command prompt
here on server one nug and type in ping to 192.168.1.8. And this
is verify that's our rates address real quick. So here's our
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
eight to show IP interface brief and survey says 192 168.1.8 is
our eight gig zero zero interface address, which is this one
right here facing towards server one nug. So if we go back to
server one nug and go back to the command prompt and we try to
ping that address. That's a very good sign. And based on our
topology, if routing is working correctly, we should from server
one nug over here on the far bottom right of our topology, we
should be able to ping and trace over to PC seven, which is 10.1.7.10.
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
So let's try that next. Let's do a ping to 10.1.7.10. Survey says
that works. And let's do a trace. So on a Windows computer,
trace is spelled a little bit funny. You can bring this up a
little higher. So we can see it. So it's T-R-A-C-E-R-T and a
Windows computer will do -D if you don't bother doing name
resolution. And then we'll get that same destination of 10.1.7.10
press enter. And our first hop is dot eight, which is
router eight, then dot six, which is router six, then four and
two and one and three and five and seven until we got to the
final destination of that PC. So our path through the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
final destination of that PC. So our path through the
network seems to be working. And that's all due to OSPF
version three with support for address family IPv4. So if we go
back to router eight, for example, let's do a few show commands.
Let's show IP route OSPF now be for press enter. I mean, if
you worked with OSPF and IPv4 for a long time, this command
should show you the IP routes that are learned via OSPF. But
the problem is they're not learned via quote unquote OSPF.
They're actually learned via OSPF version three. So we do a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
They're actually learned via OSPF version three. So we do a
show IP route OSPF V3. That's then going to show us the routes
that were learned via OSPF version three for address family IPv4.
So there's the IA is the inter area routes. And we have one local
route in area two. And that's the 10 to 46 network. And that's
the network between our four and our six. Also, if we did a
debug OSPF V3 hello, impressed enter, I just want you to
notice what addresses are used for the multicast addresses as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
notice what addresses are used for the multicast addresses as
they're setting hello back and forth. And that'll be good. I'll do an
unall turn off debugging. Take a look at this FF 02 colon colon five.
That's the all OSPF routers for OSPF version three with a
multicast address in the world of IPv6. And if we are sending a
message to a designated router, it'd be FF 02 colon colon six.
But I just want to make sure you're aware that behind the scenes,
if we don't have IPv6 enabled on the interfaces, OSPF version
three will not support IPv4 routing because behind the scenes, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
three will not support IPv4 routing because behind the scenes,
it's using IPv6 multicast addresses. All right. So let's take a
look at a few other show commands. We need to show OSPF V3 space
question mark. So if you want to see just the IPv4 address family
stuff, you can type in IPv4. And then you can say interface and
we'll go ahead and say brief press center. And that'll show us
just for IPv4 address family, the OSPF version three enabled
interfaces and their current status. So those two interfaces are
participating in OSPF version three for address family IPv4. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
participating in OSPF version three for address family IPv4.
They're both part of OSPF V3 process ID1 and they're both
associated with area two. So here's confirming the address
family. And there's the cost for our fast ethernet versus our
gigabit ethernet. And currently this router, our eight is the
designated router for both of the segments. And off of the F a
four slash one, we have one fully adjacent neighbor. So the F is
for fully adjacent and the C is for count. So one neighbor is
there and we are fully adjacent with that neighbor. The see
those neighbors, we can do a show OSPF version three IPv4 neighbor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
those neighbors, we can do a show OSPF version three IPv4 neighbor
press center. And that will show us our neighbors for IPv4. Now
if we were running IPv6 also you just swap out the IPv4 typev6.
And that would show you the IPv6 address family neighbor
jacencies. So our neighbors router ID is 6666. They have a
full adjacency and it is a BDR. And that's because we are the
DR as shown right here. If you're going to do a show OSPF V3
without any other options is press enter, that will confirm our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
router ID locally is showing us the process ID, which address
family were supporting. We have one normal area. And that's
area two. There's two interfaces in the area. And our reference
bandwidth, we bumped up from the default of 102 1000. If we do a
show IPv6 protocols that indicates that OSPF process ID one is
running, although behind the scenes is not just the traditional
OSPF, it literally is OSPF V3. And if you want to see the OSPF
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
V3 database, we do show OSPF V3 space. And then if you want to
see both IPv4 and IPv6, you can just go ahead and not specify
either one just put in database. Now in our case, we only have
IPv4. So it's only going to show us the OSPF V3 database for
IPv4. So here's our LSA type ones. We have three of them
because we have three routers in area two. Here we have one
network link state LSA, that's the LSA type two generated by
the DR. And that's 8888 where there's two or more routers on
that common segment. So our eight is generating the net link
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
state. That's the LSA type two. And then we have multiple LSA type
threes as shown right here. So an IPv4's traditional OSPF that
would be called summary LSAs and IPv6. The LSA type three is
recalled inter area prefix link states. And effectively
showing us all the LSAs that the ABR rather four has
advertised into area two. And then because we're running OSPF
version three, we also have LSA type eights as shown here and LSA
type nines. Even though we're only supporting IPv4 unicast WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
type nines. Even though we're only supporting IPv4 unicast
routing that address family, we're still going to have the
LSA types eights and nines. So another we've set up OSPF V3 to
support the address family for IPv4. In the next video, I'd
like to walk you through how we set up a passive interface with
OSPF V3.