[MUSIC PLAYING]
And here's the tasks involved in this lab.
On R7, over here, I'd like you to create a loopback, number 7,
and give it the IP address of 77.77.77.77/32,
so create that loopback.
I'd like to include that loopback into area 7,
and then furthermore, I'd like you to make sure that route
to that 32-bit route, that 77 et cetera WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to that 32-bit route, that 77 et cetera
network, that is reachable by everybody else in this OSPF
domain.
So that's your mission, should you choose to accept it.
Have some fun.
Go ahead and pause me now, and then resume me
when you're ready for the walkthrough.
All right, here we go.
Let's go ahead to R7, and let's add the loopback.
Let's see what we have first.
Show IP, interface brief.
All right, we don't have a loopback 7 yet,
so config t interface loopback 7, and IP address-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
so config t interface loopback 7, and IP address--
77.77.77.77, and this mask is this.
That looks like four octets.
Fantastic.
It's already up.
And let's add that into area 7.
I think we said 7 or 77.
I'm going to put it into area 7.
They'll serve the same purpose.
So IP, OSPF 1, area 7--
boom. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
boom.
So IP, OSPF, interface brief--
super.
So we've got this 32-bit route inside of area 7.
Now, we need to make sure it's available to the rest
of the network.
So to solve this, because it's now discontinuous--
let's put this up here.
We've got this area 7 here, this loopback interface in area 7,
and there's no area border router for area 7.
So we could do a virtual link between R7 and R3,
and that way, we could build a virtual link right here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and that way, we could build a virtual link right here
through R3, who's currently in ABR.
So let's do that.
Let's go to R7, and on R7, we'll do a config t and router OSPF--
spelling router right-- router OSPF 1,
and area 1 is going to be our transit area.
We're going to create a virtual link up
to R3, which is 3.3.3.3.
And then on R3, we're going to create the virtual link back WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then on R3, we're going to create the virtual link back
down to R7, so config t and router OSPF 1 and area 1
virtual link going down to 7.7.7.7.
And we'll just take any problems as they come.
So it shouldn't take long for us to get
a neighborship, a full adjacency over that virtual link
between R3 and R7, but I don't see it coming up.
Show IP, OSPF, virtual links. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Show IP, OSPF, virtual links.
Not a bad command.
State is down, so there's our hello timer.
The state is down.
Show IP, OSPF, interface brief.
Yeah, shows that it's down.
Now, a lot of times, that can be a reachability issue, where
we pointed to not the router ID, but we pointed WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we pointed to not the router ID, but we pointed
to the actual interface.
Let's go check our work.
Maybe I put the wrong address in.
So on R7-- oh, it's right here.
So area 1 virtual link 3.3.3.3 show IP protocols.
We're in area 1.
So is R3.
All right, there.
So why are we not neighboring? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So why are we not neighboring?
Let's make sure that R3 can either show IP OSPF--
actually, I want to do show IP protocols.
All right.
Show IP protocols, and it says it knows about--
so it appears that the router IDs are correct.
Let me see if have routes.
On R7, show IP route, OSPF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
On R7, show IP route, OSPF.
All the right letters.
All the wrong order.
Oh, look at that.
All right, we have no inter-area routes at all.
So it knows--
35, it has, though.
So that's an intra-area route.
All right, well, let's just troubleshoot this one hop
at a time.
Let's do a show IP OSPF.
Now, he's going to have a neighborship with R5
because we have OSPF learned routes.
Let's go to R5, and just in our topology that's right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's go to R5, and just in our topology that's right here,
I just want to find out if we're all
copacetic with our adjacency with R3.
So let's go to R5, and we'll do a show IP OSPF neighbors.
I remember now what I did.
This is saying that we have a neighborship
with two devices that both have the same router ID of 7.7.7.7.
Look at the addresses are different.
So 35.3 is the address of R3, and 57.7 is the address of R7. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So 35.3 is the address of R3, and 57.7 is the address of R7.
Somebody hardcoded, it looks like, the router ID of router 3
to the wrong address.
So if R7 is peering or trying to drill a virtual tunnel
to 3.3.3.3, and the router ID for R3 is 7.7.7.7,
that's a problem.
So let's go fix that on R3.
We'll verify it first.
Oh, right here.
I should've taken a look at that.
So on R3, the router ID is 7.7.7.7.
Now, in this lab environment, I don't
have-- we don't have the ability to do a clear IP OSPF process, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
have-- we don't have the ability to do a clear IP OSPF process,
so I think what I'm going to do is just remove it and put it
back in.
Config t and no router OSPF 1--
[MAKES EXPLOSION NOISE WITH MOUTH] there you go.
And router OSPF-- and then router OSPF 1,
and then I'll put my network statements here again.
In fact, I'll just copy them right here.
Doo-doo-doot, copy them, bring up Notepad, paste, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Doo-doo-doot, copy them, bring up Notepad, paste,
and I'll put some network statements up there.
I'm not trying to get organized.
I'm just trying to not have to type as much.
So we'll go ahead and run router config.
Let's copy that, right click, and paste it in.
Great, so there's our networks back.
And I'm also going to auto cost reference bandwidth
because I've set it everywhere else in this topology
to 1,000, so I want to make it consistent here.
All right, our router ID is 3.3.3.3 now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
All right, our router ID is 3.3.3.3 now.
That's great.
And let's also-- oh, the virtual link.
Let's create a virtual link down to R7.
So we'll do an area 1 virtual link and go to 7.7.7.7,
and we should get a full adjacency if everything else is
working there.
is to show IP, OSPF neighbor--
not yet.
It might take just a moment, though.
So we're adjacent with R4, which is over in area 0.
We're adjacent with R1 in area 0, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We're adjacent with R1 in area 0,
and we're adjacent with R5, which is in area 1.
And show IP OSPF virtual links--
still says it's down.
Let's go check our work on the other side.
So over here on R7, show IP OSPF virtual links--
oh, right here, it says the virtual link to OSPF
VL0 to router 333 is up. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
VL0 to router 333 is up.
Show IP OSPF neighbor--
but I don't have the neighborship.
Hmm.
So why is that not working?
Let's go back to the middleman here, and let's do--
let's go to R5 and just verify it has full adjacencies with R3
and R7.
After we change the router ID on R3,
let's make sure that's still working-- or is working now.
So back to R5, we'll do a show-- it looks like it is. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So back to R5, we'll do a show-- it looks like it is.
Show IP OSPF interface brief--
so 4/0, we have a full adjacency, and gi 1/0,
we have a full adjacency.
And then we have the loopback, which is great,
and then gi 0/0, which is not too relevant in our topology.
So we have full adjacencies.
Show IP route OSPF--
and we have a boatload of routes.
So why isn't the virtual link working between R7 and R3?
Let me just go check our work here real quick. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let me just go check our work here real quick.
So config t, router OSPF 1, area 1 virtual link to 3.3.3.3,
and go back to R3, config t, router OSPF 1,
area 1 virtual link to go to 7.7.7.7.
What did I do on this one?
Why isn't this-- why is this not working?
So we have our neighborships with the immediate neighbors.
Show IP OSPF neighbor-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Show IP OSPF neighbor--
R3 has an adjacency with R4, R1, and R5.
Show IP-- but the virtual link isn't working.
State is down right there.
So the virtual link to router 7.7.7.7, and the state is down.
Why is that?
Everything looks OK here, so let's just take a look at--
I mean, here's the kicker on this one,
is that if we do a Show IP OSPF neighbor,
we have full neighborships with everybody.
So if we do show IP OSPF interface-- WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we do show IP OSPF interface--
so they're having some kind of a communication
problem over that virtual link.
If we go to R7, do a show IP OSPF neighbor-- let's
do a show IP OSPF interface brief.
Yeah, it's not happy.
So let's just verify we can ping this guy right here.
I just want to make sure we have full connectivity between R7
and R3.
So on R3, this would be 10.1.35.3.
Let's just verify that we can ping him, just to verify it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's just verify that we can ping him, just to verify it
and rule out it's not a Layer 3 basic connectivity problem.
So ping to 10.1.35.3.
Oh, unreachable.
Let's do the other side.
Let's do .5.
So we can ping to 10.1.35.5.
That's R5's address.
But we cannot ping the other interface,
so let's go take a look and see if R5 can ping that,
its directly connected neighbor. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
its directly connected neighbor.
Ping 10.1.35.3-- maybe lets verify that address.
On R3, show IP interface brief, 10.1.35.3.
That's its IP address, so why can't we
ping him, unless there's an access list
or something involved.
Let's check in on that access list on FastEthernet4/1.
Show IP interface Fa 4/1--
inbound access list not set. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
inbound access list not set.
And so in our topology, if we're pinging from R5,
it wouldn't be an outbound access list,
because if R5's trying to ping that address itself,
it wouldn't apply to it anyway.
Let's check the routing table on R5.
Let's see if there's something wacky with routing.
So on R5, do a show IP route.
Just want to look at the whole thing.
So 10.35-- oh, yeah, this could be the problem right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So 10.35-- oh, yeah, this could be the problem right there.
I've got a static route that says
if you need to reach 10.1.35.3, a 32-bit route, go ahead
and put it in the bit bucket.
So when they were trying to negotiate the tunnel,
and R7 was talking to R3, when it went into R5 for routing,
R5 said, yeah, I'm dropping that unicast packet up to R3.
I'm killing it, and that's what's happening right here.
It's destroying that communication path.
So let's go on R5, and let's get rid of that static route.
So no IP route, and it's going to be this guy right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So no IP route, and it's going to be this guy right here.
I'll just copy and paste that and put in the mask,
and let's verify it's gone.
Show IP route static--
so we've got some static routes, but that one for 10.1.35.3
is no longer there.
And let's see if that made a difference.
Let's go to R3.
Oh, look, yeah, now we have our full adjacency over the tunnel,
so show IP OSPF neighbor, and there it is right there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
so show IP OSPF neighbor, and there it is right there.
And so now that network, if we go up
to R1, who's in the backbone, and do
a show IP route, if we want to find that 77.77 network,
there it is right there.
And if we go over to R8, it should have it,
and there it is.
Let's do a trace to that address.
And there, we have full connectivity, end to end.
All right, so here's what we did in this video and lab. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
All right, so here's what we did in this video and lab.
We injected at least one problem that
involved the need for a virtual link,
but we also had connectivity problems in that transit area,
in area 1, that was prohibiting the virtual link from being
able to be established.
That was a nasty little static route
for a specific 32-bit address that
happened to be owned by R3.
So as R3 and R7 were trying to set up the virtual think,
unfortunately, R5 was taking any packets
that were going to the .3 address
and just dumping it in the bit buckets. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and just dumping it in the bit buckets.
They couldn't actually negotiate and set up
the tunnel over area 1.
So I hope you had some fun in troubleshooting OSPF version 2
labs that involved some type of virtual link
activity and a few other problems as well.
Now, in our next set of videos, which
we'll take a look together at here in just a few minutes,
we're going to focus on OSPF version 3 for IPv6, and once
again, with our eye towards the need
and the troubleshooting of virtual links.
So I'll see you in those videos in just a moment.
Meanwhile, I hope this has been informative for you,
and I'd like to thank you for viewing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and I'd like to thank you for viewing.