Now we've got the same premise here,
the same objective getting from R4
through the most efficient route down here to gig 00.
But this time we're using IPv6.
Now here's the IPv6 addressing that Keith left us.
2001, DB86783, this is the same.
Then the big red X followed by a bunch of zeros.
What's the big red X?
Replace it with these numbers that you see right there. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Replace it with these numbers that you see right there.
So we need to get from 2001, DB86783,
colon, probably something like 24,
all the way around to 2001, DB86783, colon 57.
That's gonna be our objective.
Now let's take a look at the lay of the land here
for a second, let's get back here
and let's jump over to R7.
Press enter to get started.
Let's give it a show IPv6 interface brief. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Let's give it a show IPv6 interface brief.
And let's see, what interface was it
that I was caring about again?
One zero, no, 00.
So let's look at gig 00.
There is 6783, colon seven,
and then the router ID of seven right there.
So if I go to router four and give this a ping
to paste right there to this address,
can we get there?
No success rate, none. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
No success rate, none.
Why?
No valid route.
Show IPv6 route.
And let's take a look at what we got.
Lot of 2001 DB8s, then some local interfaces here,
like two, three, four, six, eight.
Let's hit space bar a few times.
I'm seeing the one, two, one, three,
two, four, three, four, three, eight,
four, six, six, eight, seven, eight. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
four, six, six, eight, seven, eight.
So I do see routes being learned by EIGRP.
This is the linking routes.
This is the loopback addresses and so on.
So again, I kind of feel like using
the same methodology here.
This time, we don't even have a route
to 2001 DB86783, colon seven.
We don't even have it at all.
So considering we have one, two, three, four, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So considering we have one, two, three, four,
we don't have five, six, and eight,
tells me something's wrong with router five.
So if we look, where's router five again?
Yeah, kind of why I like starting
closer to the destination.
Again, that's just me.
Let's take a look here.
So if I jump over to router five, here we are.
Let's give it a show ipv6 route.
And I have no EIGRP learned routes. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
And I have no EIGRP learned routes.
Show ipv6 EIGRP interfaces.
Okay, interesting because I do have EIGRP on
and I even have a peer of gig one zero.
Gig one zero is down towards router seven right here.
Okay, but I'm still not learning any routes, am I?
So if I have a peer, but I'm not learning any routes, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So if I have a peer, but I'm not learning any routes,
that could tell me something is really off
with stub operations or something is really off
with passive operations.
Show ipv6 protocols.
You know I like that one, right?
Okay, K values look good.
They're the default values.
I see the interfaces that are participating in this.
I don't see any network statement here.
And if I give it a show ipv6 EIGRP neighbors, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
And if I give it a show ipv6 EIGRP neighbors,
again, we see the neighbor adjacency up.
But again, we're not learning anything.
Show run section router.
We know it's gonna hang for a second.
Big process to parse all that output.
Here it comes.
Do, do, do, do, do, do, do.
All right, let's take a look.
Okay, we've got address family ipv6.
We have some authentication going on here. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
We have some authentication going on here.
No network statements or included interfaces.
Let's compare this to a known working router,
like router four.
If I give this a show run section router,
pause it for a second while it loads,
hit space bar a couple times,
and we have almost the exact same configuration here. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Looking at the topology again,
router five and router four
had really similar configurations,
but router five doesn't appear to be learning any prefixes.
So if I go back to router five here, show ipv6 route.
Again, we don't see any dual learned route.
So if I give it a show ipv6 EIGRP neighbors,
hmm, it only sees a connection of gig one zero. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
hmm, it only sees a connection of gig one zero.
Show ipv6 EIGRP interfaces.
Again, we only see one neighborship via R7.
So what's going on with R7 first of all?
Let's take a look here.
If I give it a show ipv6 route.
Okay, we have EIGRP learned routes.
Looks like they're via router eight. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Looks like they're via router eight.
Okay, so something is going on
between router seven and router five.
Let's take a look at that running config.
Come on, any second now.
Here we go.
Aha, router seven isn't advertising anything WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
because it's configured to be a stub with receive only EIGRP.
Well, that's gonna be a big problem right there.
Nobody knows how to get to router seven.
So we'll go into config T.
We will go into our process of EIGRP
process of EIGRP, our EIGRP.
We're gonna grab this big address family statement
for autonomous system six for ipv6. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
for autonomous system six for ipv6.
And we're gonna remove the stub receive only.
So this is a stub router
that is not configured to do anything.
Okay, oh, new adjacencies all over the place.
Now, if I go to router five,
let's take a look at those interfaces.
We have the peer, we knew we had a peer.
Let's take a look at the neighbor adjacency.
We knew we had the neighbor adjacency.
Let's look at the routes.
Ah, now we're learning prefixes. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Ah, now we're learning prefixes.
That's good news.
Okay, so does that fix our problem?
Let's try and run our ping test again.
Aha, now we do have a ping test.
Let's trace route to that prefix.
Come on.
Okay, it went, ah, it went down again.
Four, six, six, eight, seven, eight.
It went over those serial links.
Okay, so it went this way again. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Okay, so it went this way again.
The suboptimal route one more time.
Okay, so that tells me something's up
maybe between R3 and R1 or R1 and R2.
Let's take a look.
Okay, back on R3, let's do show IPv6 EIGRP interfaces.
Okay, I have peers, but do I have peers
off the right interfaces? WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
off the right interfaces?
Because router three had a lot of connections, right?
It actually had like four.
Okay, ah, gate one, zero.
Pretty sure that was the one that didn't have a connection.
Yeah, we don't have a peer.
Oh no, we do, we do.
We have a peering connection off one, zero.
We don't off zero, zero, which is not in use.
Okay, so we only have to worry about these four interfaces,
one, zero, four, zero, four, one, and three, two. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
one, zero, four, zero, four, one, and three, two.
And we have one, zero, three, two, four, zero.
We didn't have one through four, one.
I don't know why I just did that.
In fact, that's probably a problem
because four, one is how we get from three to five,
isn't it?
Let's see.
Yeah, four, one is how we get from three to five.
So there's a problem between four, one and four, zero.
Okay, so let's do show IPv6 protocols. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Okay, so let's do show IPv6 protocols.
K values, one, zero, one, zero, zero, zero, looks good.
Interface four, one isn't even in the list.
Show IPv6 EIGRP interfaces.
Okay, four, one's not even in the list.
So let's see why.
Show run section router. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Show run section router.
Okay, it loads up.
Spacebar, well, that'll do it.
You just turn the interface off.
This isn't even passive or stub.
This is saying this interface right here,
FastEthernet four, one is explicitly disallowed
from doing anything related to EIGRP.
Let's get that out of there.
Config T, router EIGRP, our EIGRP. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Config T, router EIGRP, our EIGRP.
Let's go into that address family.
And then let's just do,
let's move into AF interface and then do no shut.
Oh, well, immediately gets a new adjacency.
Show IPv6 EIGRP interfaces. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Show IPv6 EIGRP interfaces.
Okay, I see a peer that should be going up to R1.
Let's test our ping one more time.
Actually, let's do our tracer out.
Aha, now we're going up to two, over to one,
down to three, down to five, and down to seven.
So now we're going two, one, three, five, seven.
Woo, tricky labs, but good job.
We ended up getting there. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
We ended up getting there.
Now, onto our challenge section.
I hope this has been informative for you
and I'd like to thank you for viewing.