So in this walkthrough, we're going to walk through the lab tasks.
We should involve setting up OSPFV3 for the address family for IPv6 as shown in
the topology.
And then once we verify that, we'll configure area two as a totally stubby area
.
It will also set up a summary.
So any routes that begin with those first 48 bits and will make one summary
that will advertise
up into area zero. And that's going to get happened on R3 because that's the
area border router
between area one and the backbone area. So with that in mind, I have reset my
lab environment.
Let's go to it right now and let's do this walkthrough together. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's go to it right now and let's do this walkthrough together.
So a few moments ago, I just clicked on reset and it'll take just a moment or
two for this to fully
initialize. And when it's done, we'll go ahead and start the walkthrough. All
right, so here we go.
Let's go ahead and open up the stupology diagram on the desktop of server one -
nug that looks good
and we use that for our reference. This same topology is also included as part
of the skill.
So if you want to put that on a separate screen or print it for reference, that
's going to be helpful as well.
And then let's go ahead and we'll double click here on server one nug to open WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then let's go ahead and we'll double click here on server one nug to open
that up
because that's how we're going to get to our console access for each of the
routers.
Is VS server one nug? All right, and here it comes. Fantastic. And then we also
have in the
background the OSPF configs doc should we want to use that as well. So what I'm
going to do is because
we've already done this a couple times. I'm going to scroll down to the IPv6 OS
PF section as part of
this configuration file. And here it is. OSPF version three with IPv4 and IPv6.
And let's go ahead and
start with r1. Now in this lab environment, I'm not asking you to do IPv4. So I WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
start with r1. Now in this lab environment, I'm not asking you to do IPv4. So I
'm not going to even bother
doing the IPv4 portions for that address family. We're focused just on IPv6. So
in the
instant of time, I'm going to use this notepad document, take those configs,
copy them, and put them
on to r1. Then I repeat that process for r2. So in r2, I'll take the config for
r2. I'll remove the
enablement of the address family for IPv4 on the interfaces. And then once that
's done, I'll take the
config for r2. Copy that. And all of its interfaces are going to be an area
zero. So we'll copy that,
then go to the right tab for r2 and paste it in. And then I'm going to repeat WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
then go to the right tab for r2 and paste it in. And then I'm going to repeat
that for r3,
r4, r5, r6, r7, and r8. All right. So OSPF B3 process ID1 has been configured
on all eight
routers. And if we want to verify some basic routing, we do a show IP. Of
course, I have a show IPv6
route for OSPF learned routes, press center. And at the moment, we don't have
any yet because I'm
still waiting on a membership, I think, with r6. So if we look at our topology,
that should be coming
in shortly. And once we get that notification of the console here, we'll then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in shortly. And once we get that notification of the console here, we'll then
take a look at our
routing table. And there's our JsonC right there. And what? What? What? I'm
joking because what I
also did, I just paste it in the IPv4 enablement as well. So we actually have
two of JsonC's, one for
address family IPv4. And based on what the lab was asking for, also one here
for IPv6. So if we do
a show OSPF B3 IPv6 neighbor, it should just the neighbor ships for IPv6. And
there's our full
of JsonC up with r6. So now if we get the upper key a couple of times to show WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of JsonC up with r6. So now if we get the upper key a couple of times to show
IPv6 route that we're
learning via OSPF, we should have all the routes in our routing table. So there
's the seven network
right there. This is to a trace. So let's go ahead and copy that and let's do a
trace. And we'll
paste that in. And r7's last octet is seven there, press center. And there we
have the trace
all the way from r8 all the way to r7. And then as you do the lab also feel
free to practice with
many of the show commands that we've issued up to this point. For example, show
IPv6 protocols show IPv6 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
IPv6 protocols show IPv6
interface brief just to verify what addresses are there. Show OSPF version
three interface brief
and show OSPF B3. And I'm going to go ahead and say just for IPv6. So here's
the OSPF B3
information regarding process one for address family IPv6. There's the router
ID. There's our reference
bandwidth that we set to a thousand. There is the one normal area because this
is r8. It is in area
two. And it's not yet a stub because we haven't configured that yet. But it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
two. And it's not yet a stub because we haven't configured that yet. But it
will be once we configured
as a stub in fact, let's take that next step right now and configure area two
as a stub. So to do that
we need to go to r4, r6, and r8 to do that. So let's go ahead and use this
option right here.
Still carriage return icon. And what we'll do is we'll go into configuration
mode for each of our
routers and type in router. OSPF B3, process ID1. And then we'll say area two
stub. Now if we did area two
stub, no summary on a router such as r6 or r8, it wouldn't matter because they WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
stub, no summary on a router such as r6 or r8, it wouldn't matter because they
are not area border
routers. The only router that's going to care about not advertising the lc type
three is it's going to be
an area border router. So we could, if we wanted to, we could get away with
this. If we go back to
the multi tab putty here, we could say no summary right there. And then end.
And that would make it
a totally stubby area. And r6 and r8 would know its area two stub and the no
summary part wouldn't matter
to them. It's only applicable to the area border router. So I'm going to go WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to them. It's only applicable to the area border router. So I'm going to go
ahead and send that to r8,
r6, and r4, click on send script. And we should be set. So let's go double
check here on r4,
the show OSPF B3. So this is showing us that we have one normal area. That's
the backbone area
and one stub area. That's area two. And it's also reinforcing that right here
under area two. It says
it is a stub area. So if we went down to r8 and down on r8 where a moment ago
if we scroll up,
we had a whole bunch of inter area routes as shown right here from earlier a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we had a whole bunch of inter area routes as shown right here from earlier a
few minutes ago. Now if
we had the rq a few times and do a show ipv6 route, ospf, impress enter. Now we
have our default route.
That we learned courtesy of r4 that's our area border router. And we have one
intra area route here
of 2001 db678346. But we have none of the other lsa type 3s. However, we still
have access
to reach those other networks because we have our default route. So if we did a
trace route again,
I'll let the up arrow key till we find that. There it is. If we trace route WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'll let the up arrow key till we find that. There it is. If we trace route
over to our sevens gig
zero zero address, impress enter. It can go ahead and verify for us that we
have full connectivity
from r8 all the way around the horn down to r7. So let's check our tasks and
verify we did it. We
set up ospf v3. We verified basic connectivity. We configured area two as a
totally stub area.
And we verified connectivity. Oh, I almost forgot. We need to summarize the
routes beginning with
2001 db67834 those first 48 bits and create a summary route from area one as we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
2001 db67834 those first 48 bits and create a summary route from area one as we
advertise those
into area zero. And again, we're going to do that on r3 because that's the area
border router between
area one and the backbone area. So let's head over to r3 and we'll set up that
range configuration
inside of ospf. Let's go ahead and show the configuration for our routing with
show run section
router. And let's go into configuration mode. And from configuration mode, we
'll go into router ospf v3
for process id1 by typing that in. And then further, we'll go in the address
family for ipv6
unit cast because that's what we want to do the summary for. And then here we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
unit cast because that's what we want to do the summary for. And then here we
're going to type
in area. And then the area we want to summarize routes for which is area one.
And we want to do 2001
db8 colon 678 3 colon colon slash 48. And we press enter. Oh, I put 49. Oh, and
I put 49. And I also
forgot to put the range command. So let's go ahead and fix that. So area one
range. And that is the
same command, the range word, whether we're in ipv4 or ipv6. So area one range,
the summary we want
to do. And I want a 48 bit summary, not a 49 bit summary, although that 49th WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to do. And I want a 48 bit summary, not a 49 bit summary, although that 49th
bit would also be a
0. So that probably work. But we press enter here. And now with that range in
place, we'll go ahead
up to r1. And here on r1, if you do a show ipv6 route, and we'll tag on ospf
just for ospf
learned routes in press center. Here we have our 48 bit route. But what isn't
showing up are those
other detailed routes. So what I mean by those other detailed routes, I'm
referring to the 35 subnet
and the 57 subnet and the 7 subnet because they're being suppressed. And
instead of advertising all
those lc type 3s for those individual routes, it's advertising this one summary WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
those lc type 3s for those individual routes, it's advertising this one summary
of 2001 db868348.
So if we want to verify full connectivity, we can go back to r8. We can hit the
up arrow key and do
a trace route all the way through the network down to r7. And that's just still
function because
everybody every single route in our topology has some type of routing
information, including
default routes or more specific routes to forward the packets in the right
direction.
So thanks for joining me in this set of videos and into skill regarding working
with ospf version 3 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with ospf version 3
for the address family for ipv6 and idlc4dcingu my friend in another set of
videos very very soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.