In this video and hands-on lab, we
get to play with OSPF version 3 and implanting a virtual link.
[THEME MUSIC]
And here is our network.
This is a very similar topology that we've
been working with in other IPv6 related videos regarding
troubleshooting.
So just as a reminder where things are in case this is
your first section of videos, 2001:DB8:6783:RR is the IP
addressing that we're playing with,
with RR representing the two routers.
So between R3 and R4, there would be a 34 there, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So between R3 and R4, there would be a 34 there,
and between R3 and R5, there'd be a 35.
Between R1 and R2 would be a 12, and so forth.
And then the last number of the IPv6 address
is going to be the router number.
An example of that down here is the R8 off of Gi0/0.
We have 2001:DB8:6783:8::.
And let me update this right here with 64,
because we have 64-bit networks all the way across the board.
Too
Much IPv4 on the brain, I suppose. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Much IPv4 on the brain, I suppose.
So far our lab, let's imagine that we want to take this
network right here, and this network is the 2001:DB8:6783.
And because it's going between R7 and R8,
it'd be 78 in those positions right there.
Great, great, great.
So that's going to be the 78 network,
and that IP addressing is already in place.
However, this area, that network is not part of area 78.
So what I'd like to do is add this as the IPv6 OSPF area 78,
and the problem is area 78 does not have a area border router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and the problem is area 78 does not have a area border router.
So to solve that, we really have three options that we could do.
We could include this link right here between R3 and R8
and have that also mean area 78, because then we'd
have-- area 78 would have an area border router.
That would work.
That's option number one.
Option number two would be to implement a virtual link,
and that would work.
We could do that either from R8 up to R4 or R7 up to R3.
If we did it between R7 and R3, it'd be right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If we did it between R7 and R3, it'd be right here.
And the interesting thing with IPv6 virtual links
is that the syntax is the same as it was with IPv4,
and that is, we can go to R7, and we
go to router configuration mode for OSPF version 3.
We'd say area 1, where we're going
to have this transit area.
Area 1 virtual link, space, and then the router
ID of the other router that we want to logically connect to,
the area border router, and that would
be the 32-bit router ID on R3.
So in the case of-- even though we're using IPv6, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in the case of-- even though we're using IPv6,
we still point to the router ID, which would be 3.3.3.3.
And then on R3, we would go into router configuration
mode for OSPF for version 3 and say
the virtual link is going to be area 1,
and the other end of that virtual link
is going to be 7.7.7.7.
And then it's going to create that, and boom, we're done.
And then the third option is we could--
actually, we could just take these interfaces
and put them inside of area 1 or area 2.
That's another option.
And then four, we could do a GRE tunnel, where WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then four, we could do a GRE tunnel, where
you create a GRE tunnel between R7 and R3,
and then add the ends of that tunnel
into area 0, which would make R7 logically connected to area 0.
And that would also solve the problem, because then R7
could be an area border router.
What we're going to do in this lab
is we are going to focus on virtual links,
so you can see it implemented.
And our goal is to include this network here between R7 and R8
as a member of OSPF version 3's area 78.
And then to make it actually seen-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then to make it actually seen--
the 78 network seen by the rest of the network--
we would need a virtual link between R3 and R7.
Now, as a heads-up, just like in OSPF version 2, you cannot,
I repeat, you cannot implement a virtual link in an area that is
NSSA, nor can you do it in an area that is a stub area.
So on these routers, on these areas,
we want to pay attention to seeing whether they're
NSSA or stub areas.
And if we want to build a virtual link,
like I want to in this lab right now, in this, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
like I want to in this lab right now, in this,
area 1 is currently set up as an NSSA.
So to solve that, what we're going to have to do
is we're going to have to remove the NSSA type off of area 1
so that we can then build the tunnel.
So have no fear in this warm-up exercise.
I'm going to walk you through those steps,
including the implementation and verification
of the virtual link.
So have no fear.
I'll walk you through that process,
and let's do it starting right now.
So starting on the area border router R3-- actually,
we should go to R7, and let's include that interface inside WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we should go to R7, and let's include that interface inside
of area 78.
So we'll do a show IPv6 OSPF--
let's do a show IPv6 interface brief and verify what
interface we're talking about.
So between R7 and R8, that serial connection,
which is this guy right here, serial 3/1,
and that's the network 78.
So let's add that, in interface config, into area 78.
So config t interface serial 3/1 and IPv6 OSPF process WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So config t interface serial 3/1 and IPv6 OSPF process
ID 1 area 78--
badabing badaboom-- and we'll do the same thing over on R8.
So on R8, show IPv6 OSPF--
not yet.
I'm excited.
We haven't enabled OSPF on that interface yet.
Show IPv6 interface brief--
this will help us confirm which interface it is.
So it's going to be serial 3/2 based on the IP address there.
Great, so we'll go to config t interface serial 3/2 IPv6 OSPF WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Great, so we'll go to config t interface serial 3/2 IPv6 OSPF
process ID 1.
Area is going to be 78, and if we get a neighborship,
that means we did several things right on both sides.
Great.
So this network, if we looked at the OSPF database,
we're going to see-- for area 78,
we would see that information regarding that network.
So if we do a show IPv6 OSPF database--
and so we can see the LSAs for area 78, but unfortunately,
the rest of the network, if we go up to somewhere
in the backbone, or even a different router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in the backbone, or even a different router
in area 1 or area 2, they know nothing
about these 78 networks.
We do a show IPv6 route OSPF--
they know nothing about the 78 networks.
These are numerically sorted.
There's 68, and it would be right after that.
So it doesn't know about it, and that's
because we're not following the rules regarding area 78.
Needs an area border router.
So to solve this problem, what we'll do
is we'll put a virtual link in between R3 and R7
and IPv6 OSPF virtual link between those two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and IPv6 OSPF virtual link between those two.
But the problem is that area 1, indeed, is not so stubby area.
So to solve that, we're going to need
to remove the NSSA properties from area 1 for OSPF version 3.
So to do that, let's first verify
that we are a not so stubby area with a show IPv6 OSPF.
That'll do it for us.
And area 1 says it's an NSSA area.
So we're going to remove that from all three
of the routers in area 1.
That's R3, R5, and R7 on the left hand side of our topology. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That's R3, R5, and R7 on the left hand side of our topology.
So config t and IPv6--
not 7.
Not yet.
Router OSPF 1, no area 1 NSSA, and then we'll repeat that.
Do show history.
So there's two buffers.
There's one in privilege mode, one in configuration mode.
So if you do a do show history in configuration mode,
it'll show you that history.
So I'm going to go ahead and just copy those, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'm going to go ahead and just copy those,
and let's go to router 5.
Yep, config t IPv6 router OSPF 1.
Paste, and I'm going to leave myself in router configuration
mode here for a moment.
And in R7-- oh, yeah.
I thought, why are we in configuration mode?
Great, so IPv6 router OSPF 1, and we'll right click, paste.
Now, on these labs, there's a little gotcha, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, on these labs, there's a little gotcha,
and that is this.
If we go into router configuration mode for OSPF
for version 3, IPv6's flavor, and then we
type in End or Exit, and then we try
to go and use other commands, it says,
I don't know what you're doing.
So it's a lab.
Anyway, to solve that, if that happens to you,
and you go into configuration mode,
and you go out to the privilege mode prompt,
you can't go back in anything, just type in Exit and press
Enter.
And then just go ahead and log in as Bob.
No authentication beyond that is needed, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
No authentication beyond that is needed,
and your back to the races.
So now, we can do config t and all the other commands
that we could do previously before we went into IPv6 router
configuration mode.
So now what we're going to do is,
now that we've-- let's do a show IPv6 OSPF,
just to verify that OSPF area 1 is no longer a stub area,
which it isn't.
Let's put in a virtual link.
So here, we're going to build a virtual link
on R7 up to R3 and vise versa.
So config t and IPv6 router OSPF 1 and area 1, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So config t and IPv6 router OSPF 1 and area 1,
which is where the virtual link is going to go.
Area 1 virtual link, and then the other end of that
is going to be the router ID associated with the other end,
which is 3.3.3.3.
Awesome.
And then we'll go to R3, and we're already
in router configuration mode.
And from here, just type in area 1 virtual link, and the peer
is going to be 7.7.7.7.
And so that's just the router ID for that router
we're peering with, and if we get a neighborship,
that means we're in pretty good shape. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that means we're in pretty good shape.
And there it is.
So there's our neighborship right there.
So we do a show IP OSPF interface brief--
because I went into router config, and I left,
I have to go back in.
My apologies on that.
And we'll do a show IPv6 OSPF interface brief,
and there we have virtual link 0.
It shows us that we have one neighbor that we see,
and we're also fully adjacent with one neighbor.
Show IPv6 OSPF neighbors, and sure enough-- we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Show IPv6 OSPF neighbors, and sure enough-- we're
fully adjacent with R7.
If we go to R7, we should be fully adjacent with R3.
I'm going to stay in configuration mode
just so I don't have to log in as Bob again.
Do a show IPv6 OSPF neighbor, and we could also
do a do show IPv6 OSPF virtual link.
And [INAUDIBLE] spell virtually almost right.
There we go.
So this shows us that the virtual link is up.
That's great news.
And as a result, that 78 network that
wasn't around a few minutes ago on the rest the network-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
wasn't around a few minutes ago on the rest the network--
now going up to R1, we do show IPv6 route OSPF,
and we should have the 78 network, which is right there.
Because now network 78, which is an area 78--
area 78 has an area border router,
and that is our good friend right here, R7.
So here, if we do a do show IPv6 OSPF
and press Enter and Space a couple of times,
it is logically connected to the backbone.
And if we scroll up in this output just a little bit,
it also indicates right here, it is an area border router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it also indicates right here, it is an area border router
because it's connected to the backbone.
It's also connected to--
well, in this case, it's also connected to area 1.
It's also connected to area 78.
So in this hands-on lab, we've had the opportunity
to do some practice with some of the commands
to verify virtual links and IP OSPF version 3's configuration
and whether interfaces are enabled
or not an neighborships.
And in the next two videos and two hands-on labs,
what we're going to do is we are going
to do some troubleshooting, where we'll have
a lab that's presented to us.
It'll have at least one problem related to virtual links WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It'll have at least one problem related to virtual links
and at least one problem, or maybe more,
regarding something else in the OSPF world
that we can then use to hone our skills and troubleshoot.
So I look forward to seeing you in those videos
in just a few moments.
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing.