All right, my friend.
Here it is, troubleshooting lab number one.
So our objective in this lab is to get full connectivity
from R7 all the way over to R8 using IPv6.
So the IPv6 address on gig 0/0 of R8
is 2001 DB8 6783 8 colon colon with an 8 for the last number.
And on R7 if we can get a full trace, hopefully, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And on R7 if we can get a full trace, hopefully,
using the optimal path over path A instead of path B,
that would be preferred as well.
And we're looking for full connectivity from R7 to R8.
So I'm going to go quiet for a moment,
give you a chance to launch the lab,
work through this topology, work through the troubleshooting.
And then when you resume me-- go ahead and click on pause,
if you would.
And then when you resume me, I'll go ahead
and we'll come together for the walk-through
of troubleshooting this specific OSPF related problem.
All right.
Here we go for the walk-through.
The task was to be able to ping all the way from-- or trace WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The task was to be able to ping all the way from-- or trace
or have a connectivity all the way from R7 to R8.
So let's go to R8.
We'll do a show IPv6 interface brief just
to make sure we know what we're trying to hit.
We'll grab that IPv6 address, go back to R7
on the left-hand side of our toplogy.
Oh, I dragged it down wrong.
There we go.
We'll go back to R7.
We'll do a trace and we'll do a paste.
And wow.
OK.
It's not going very far.
So we don't have to wait.
We can do a Control Shift 6. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We can do a Control Shift 6.
That should break out.
Great.
And let's do a show--
let's take a look at our routes.
Show IPv6 route.
And we'll say just OSPF learned routes because that's
what we're focusing on.
Show IPv6 route OSPF.
There we go.
All right.
Well, OK.
So this implies a few things.
So here are the codes, OI.
If we look at OI that's an OSPF inter-area.
We have O for OSPF.
We have the ON2, which is right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We have the ON2, which is right here.
That's an NSSA external type two.
So we have some routes, which means
that we have some neighborships that we've learned from.
So here in R7, if we do a show IPv6 OSPF neighbor,
we're going to have a neighborship
because we're learning routes.
So let's move higher up in the topology.
So R7 didn't have any routes to get to that 8 network
over here.
Let's jump up to--
you know, there's a couple ways of doing this.
We could jump up a couple routers closer,
or we could go really close, like, to R6 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or we could go really close, like, to R6
and see if it's there.
Let's go to R3.
Let's just skip a couple routers and go up
to R3, the area border router and take a look at that.
And see if it knows about that route.
Because it's in area zero, and as a result,
if the route is in area zero, and R3 knows about it,
then we can troubleshoot somewhere between R3 and R7.
So let's go take a look at R3.
So up on R3 we'll do a show IPv6.
I just washed my hands.
I can't do a thing with them.
Show IPv6 route for OSPF learned routes.
So it sees a whole bunch of these external, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So it sees a whole bunch of these external,
or these NSSA routes.
And it sees 57.
We are missing a ton of routes here, too.
So let's check our neighborships.
R3 three should be a neighbor with R1 and R5 and R4.
And let's go verify that.
Show IPv6 OSPF neighbor.
OK.
Well, what would cause this guy not
to neighbor up with R1 and R3?
If OSPF wasn't enabled.
We'll do a show IPv6 OSPF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We'll do a show IPv6 OSPF.
So, oh, it says it has two interfaces in the backbone
and their both--
but nothing's active.
Hmm.
Let's do show IPv6 protocols.
So that shows the interfaces that
are supposed to be enabled for OSPF for IPv6.
But I'm going to show IPv6 OSPF interface brief.
Yeah, but we're not getting neighborships
for that first zero over here on the right WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
for that first zero over here on the right
is the full adjacency for 4/0 and gig 1/0.
So there's lots of things we could have done.
We could look at the interfaces, se if the timers are off.
We could see if there is an MTU mismatch.
We could see if--
from an earlier show command I saw what it was, though.
Let's do a show IP IPv6 OSPF.
And for the backbone error, which says inactive,
meaning we're not participating in it,
I see this guy right here, MD5 authentication. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I see this guy right here, MD5 authentication.
And if we went to another router,
like, router 1, and did a show IPv6 OSPF and pressed Enter.
It says for the backbone that there's no authentication.
So basically what's happening is that--
I've got a leaf blower going on in the background.
So basically what's happening is OSPF on R3
is requiring authentication.
And it appears R1, and we could also check on R4 with a show WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And it appears R1, and we could also check on R4 with a show
IPv6 OSPF For area zero they are not requiring authentication.
So here's R3.
So we need to remove that.
So let's do a config T router IPv6 router OSPF process ID 1.
And we'll just do no authentication.
Oh, it's going to be area, no area zero authentication IPsec WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Oh, it's going to be area, no area zero authentication IPsec
SPI.
OK.
If we scroll up a little bit, in the output here it was SPI 256.
All right.
And now it gives us an option for a carriage
return for enter.
So that should remove it.
And if that works, our neighborships-- oh, there we
go.
Our neighborships just came up with R4 and R1.
That is fantastic.
Now, in this lab, you know, labs are interesting. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, in this lab, you know, labs are interesting.
Once we go into IPv6's router OSPF process, like we just did,
and we go out.
And we're just ganked.
And I don't know all the reasons why that is.
But if that happens to you in this lab, all you need to do
is this-- exit, logout, and press Enter.
Log back in as Bob and you're right back to where you were.
So now we go into configuration mode
and do everything we could do before.
So if you run into that issue where
you go into IPv6 OSPF router config WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
you go into IPv6 OSPF router config
and you exit out and then you can't do anything, just type
in exit.
Log in as Bob and Bob's your uncle.
It'll be fine.
All right.
So let's check and see whether or not on R7,
let's go back to R7 in our topology, just as a visual.
This is R7 down here on the bottom left.
Let's see if we have the route to the eight network
over on the far right.
So we'll do a show IPv6 route OSPF.
And these are numerically sorted for us.
So there's the four network.
And there's the 12 network, but no eight. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And there's the 12 network, but no eight.
So we have definitely more routes than we used to.
Let's go further in our topology and see where.
So let's see if R3 has the route.
That would be good idea.
So show IPv6 route OSPF learned routes.
Looking for the eight network, I see the seven network.
I see the 12 network, but no eight network.
So area zero doesn't have it.
And so that means we should go closer to where the problem is. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so that means we should go closer to where the problem is.
And that closer is we could go down to R4, who's in area two.
And let's see if he has the route.
If he doesn't the route, then we'll get closer to the problem
as well.
So let's run over to R4.
And on R4 we'll go to the right router.
We'll do a show IPv6 OSPF route.
Show IPv6 OS-- oh.
Yeah, show IPv6 six route OSPF.
WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
All right.
We're looking for the eight network.
There's the seven network.
And there's the 12 network.
It's not there.
So let's see if R4 has an adjacency with the right side,
with R6.
Because that's the only place we'd
be learning it from with the LSAs
that we're sharing in that area.
So let's just see if that adjacency exists.
Show IPv6 OSPF neighbor.
No, no R6.
So let's do a show IPv6 OSPF interface brief. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's do a show IPv6 OSPF interface brief.
And this interfaces serial 3/1 that's going down to R6's 3/2.
So it's enabled for OSPF.
If we need to look at the timers, we could do that, too.
Let's go to R6 and do a show IPv6 OSPF interface brief.
So I'll verify OSPF is enabled on those interfaces.
And here it is.
So then we could look at the timers.
Show IPv6 OSPF interface for serial 3/2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Show IPv6 OSPF interface for serial 3/2.
You could also do a debug IPv6 OSPF hellos.
I believe that would do it and show us the timers.
We are concerned about that.
But these timers on R6 look OK.
And if we go to R4 and do a show IPv6 OSPF
interface for serial 3/1, those timers look OK.
All right.
What I did with these labs is I built these labs a while ago. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
What I did with these labs is I built these labs a while ago.
And now when I'm in them, I remember
a lot of the challenges I put in them,
but I don't remember which ones I put where.
So these timers look good.
And if we do a ping to 2001 DB8:6783 colon--
this is 46, colon colon six.
OK.
So I've got connectivity.
It's not a matter of the fact I can't get there from here.
We're directly connected over that serial link. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We're directly connected over that serial link.
Let's just compare and contrast R4 and R6.
Let's do a show IPv6 OSPF.
And we'll bring up R6, do a show IPv6 OSPF.
Now R6 is not a-- it's not an area border router.
It's not connected to the backbone.
But it is in area two.
So let's see here, number of areas in this interfaces, two,
no authentication.
Go back to R4, number of interfaces in this area is one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Go back to R4, number of interfaces in this area is one.
That's OK.
It's a stub.
Well, there we go.
Either area two is a stub area or it's not a stub area,
but whatever the case is, everybody needs to agree.
So let's go, let's find the referee.
Oh, we are on the referee.
R4 is the area border router.
And so he's most likely to be correct.
We could also go to R8 and see what R8 thinks.
Although everybody in the area, area two, has to agree that
it's a stub or not a stub.
So let's do show IPv6 OSPF, also says it's a stub. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's do show IPv6 OSPF, also says it's a stub.
So basically, R-- what device was it?
R6 here in the middle doesn't think it's a stub area
and that's why it's not neighboring up.
They have to agree.
That's our area problem that we're now focusing
on in this troubleshooting lab.
So we'll go to R6 and we'll just tell it
that area two is a stub area.
So router six config T OSPF process ID one area two stub. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So router six config T OSPF process ID one area two stub.
All right.
We have full adjacencies on both sides for OSPF version 3.
So one of the key things is, too,
is that because OSPF version 2 is also
running for IPv4, like ships in the night, if we bring down
an interface and bring up an interface
and we see OSPF messages, we want
to be sure we're looking at the right flavor, version
two for IPv4, or version 3 for IPv6.
All right, let's go back to R7 and see whether or not
we have the route to the eight network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we have the route to the eight network.
So we'll do a show IPv6 route OSPF.
And there it is right there.
There is a route.
So let's go ahead and do a trace.
So just copying that in my buffer, trace to--
I'll paste-- and then colon colon eight.
5, 3, 1, 2, 4, 6, and 8.
Home run.
Now, the opportunity we have here
is in troubleshooting we did have at least one OSPF area WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
is in troubleshooting we did have at least one OSPF area
issue.
It was R6 who thought it was a normal area instead of a stub
area.
So we corrected that.
But we also had an authentication issue up on,
I think it was, R3, where R3 was told,
yeah, we're using the authentication for area zero.
And as a result, it thought it should use authentication.
The other two routers in the area it should've been adjacent
with didn't.
And that was the problem.
So I've got one more lab regarding
troubleshooting IPv6 OSPF.
It will include at least one area related issue
and one or more other challenges as well-- again, because I want WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and one or more other challenges as well-- again, because I want
to keep you on your toes and give you the practice
in troubleshooting and looking and finding
the problems in an OSPF version 3 network
and then solving them.
So I'm grateful that you joined me for this lab.
And I'll see you in the next one.
Meanwhile, I hope this has been informative for you.
And I'd like to thank you for viewing.