All right, so one more time,
our mission is to get from R4 to this interface,
the interface that faces PC7 on R7.
And importantly, it should take the best path to get there,
not just any old path,
because otherwise we might end up going over serial links
and fast ethernet links
when there are gig paths that are available.
So without further ado,
what I'm gonna do is I'm gonna jump back to our terminals
and I'm gonna start with R4. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and I'm gonna start with R4.
Let me go ahead and let's just minimize this one more time
and make sure we look at what's going on here.
So R4, again, should be connected to 10.0.24,
10.0.34 and 10.2.46.
And allegedly, Keith already has EIGRP up and running.
So if I give this a show IP interface brief right here,
sure enough, I see 24, 34 and 46.
So, 24, 34 and 46, that all checks out. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So, 24, 34 and 46, that all checks out.
So now what I wanna do, let's just dive right into it.
We need to ping and the interface was 10.1.7
and then this is router seven,
so the interface there will be seven.
So let's do ping 10.1.7.7, up.
All right, we have five successful pings. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
All right, we have five successful pings.
All right, I hope this has been informative.
No, I'm kidding.
Let's see then, did it go the right way?
10.1.7.7, hmm.
Now I know it should have taken more than three hops
just by looking at this,
because if it was going the right way,
it would go one, two, three, four
and then it would reach its final destination
on the fifth hop.
So that tells me something went wrong.
So what route did it take?
It went through four, six, then six, eight, then seven, eight WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
It went through four, six, then six, eight, then seven, eight
I'm pretty sure that is the serial links
that I was just making fun of.
Four, six, six, eight, seven, eight.
So yeah, I was just kidding
when I said it would take that path, but it actually did.
So the question is why?
Something must be broken around here is my hunch.
So what I do when I tackle these things WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So what I do when I tackle these things
is I was like, all right,
well, we know it's not working in this direction.
I would rather start closer to the destination
and work my way back to the source.
That's just my preferred methodology here.
So I'm gonna jump over to R5 and looking at R5,
let's just do show IP route.
And I do see EIGRP learn routes here with a little D. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
And I do see EIGRP learn routes here with a little D.
So that tells me EIGRP is up and running
and it is configured.
Let's do show IP EIGRP neighbors.
And it sees, aha, it only has one neighbor to router seven.
So if we're looking at this again,
we only have a neighbor adjacency here.
And my hunch of starting out closest to the destination
actually turned out okay.
So why don't we have an adjacency with router three? WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So why don't we have an adjacency with router three?
That's the first question that I need to answer.
If I do show IP EIGRP interfaces,
okay, I see interfaces turned on for three interfaces
and I believe that's correct.
Gig 00, Gig 10 and FastEthernet 4.0.
So if I take a look at this, that's Gig 00,
which isn't even being used in this topology on router five,
Gig 10 and Gig FastEthernet 4.0. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Gig 10 and Gig FastEthernet 4.0.
So if I've got EIGRP going out in this direction,
but I'm not discovering a neighbor,
let's see what router three thinks about this.
So I'm gonna jump over to router three,
give it a show IP, let's just do route.
Yeah, okay, we've got EIGRP learn routes in here.
And interestingly, I see 7777. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So when I look at 7777,
that's gonna be the loopback for router seven.
I should probably also have the loopback for router five.
So let's make sure of that.
If I scroll up just a hair, yep,
I see the loopback for router five,
but it's being learned via router four.
So there's definitely something going on
with my neighbor adjacency, show IP EIGRP neighbors.
Yep, and I only have an adjacency with router four, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Yep, and I only have an adjacency with router four,
that's over the FastEthernet link.
So let's take a look at this and do show IP protocols.
Press tab here, we see EIGRP four is running.
Kind of scrolling down here just a little bit,
let's bring it back up, I gotta scroll.
Bear with me while I scroll here for a second,
my mouse is super sensitive.
Okay, looking at the K values, 101000, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Okay, looking at the K values, 101000,
pretty sure that's the default K values,
we haven't tinkered with anything there.
We see our router ID of 3333.
Let's scroll down some more.
Aha, routing for networks 10.0 slash 16.
Now hang on a second, when I look at this,
this is 10.1 and this is 10.38.
This one is 10.0 and this one is 10.0. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
This one is 10.0 and this one is 10.0.
Interestingly, I don't see a peer off of router one,
so something could be broken there.
But we're not getting a neighbor adjacency to router five,
likely because of that network statement.
So let's do this, if I do show run pipe section router,
just show me the router section only.
I know it's tough, I know it's a big config,
you gotta parse and there's a lot of CPU cycles WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
you gotta parse and there's a lot of CPU cycles
and it goes right there.
Yeah, right there.
We have a network statement that only catches
the 10.0 networks, not all of my 10 networks.
So what I'm gonna do, we can knock this out right now.
We're gonna go into router, EIGRP,
I'm pretty sure I saw this was a named instance here.
That's our EIGRP, now we're in there WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
That's our EIGRP, now we're in there
and this was address family, IPV4,
Unicast Autonomous System 4,
that's of course, AS4 for IPV4.
So I'll paste it, you can highlight it to copy
and then right click to paste, that'll make this come up.
So now I'm in address family four
and I can just fix the network statement.
Network 10.0.0.0, we're gonna wildcard only the first octet WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and end and that should,
oh, look at this right there.
No EIGRP log neighbor changes,
I was waiting for that console message to pop up
and it wasn't, log it up.
Whenever there's a neighbor change,
I think Keith knew I was gonna do that,
look for that console log and then it didn't happen.
Okay, now if I do show IP EIGRP, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Okay, now if I do show IP EIGRP,
neighbors, ah, I see and there's those neighbor changes
right there, they did log those neighbor changes after all.
All right, so now I see neighbor adjacencies.
So if I flip back, we're looking at this now.
Now we have a neighbor adjacency going this way
and we have a neighbor adjacency going this way
and we have a neighbor adjacency going this way.
I didn't see 10.0.13, let's go up to 10.0.13 here. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
I didn't see 10.0.13, let's go up to 10.0.13 here.
Yeah, I don't have a, hmm,
I don't have a neighbor adjacency of 10.0.13.
Does it have the interface in it though?
Show IP EIGRP, yeah, gig one zero or zero zero,
that should be it, which one was it?
Gig one zero, right there.
So good to go in that regard.
We've got the right interface present.
Gig one zero is there, but it's not discovering a neighbor WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Gig one zero is there, but it's not discovering a neighbor
which is gonna be R1.
So, okay, oop, adjacencies are flapping here.
Oh, that looks like EIGRP,
that's IPv6 adjacencies are flapping.
Hmm, let's do show IP protocols
to give me just a huge amount of information
I can immediately tell what's wrong here.
Just by, just jumping right to it.
Why'd you show IP protocols first?
One, zero, one, then it should be zero, zero, zero, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
One, zero, one, then it should be zero, zero, zero,
but I've got zero, one, zero here, okay?
All right, let's do show, run, pipe, section, router.
I wanna make sure that there's a configuration statement
in here that's messing with my K values.
And there it is, right there.
That's the one, metric weights are all blown up. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
That's the one, metric weights are all blown up.
So, we know how to fix this.
Control C, config T, router EIGRP, was this the same name?
Our EIGRP, yes, our EIGRP.
I'm just gonna grab that whole address family statement
right there, paste it,
and we're gonna do no.
I'm gonna grab the metric weight statement,
paste it, and then end. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
paste it, and then end.
All right, so, not expecting to see EIGRP neighbor changes
showing up on the terminal here for a second,
but now if I give it a show IP EIGRP neighbors,
aha, there is a neighbor adjacency
through one, three, show IP EIGRP interfaces.
I have peers in two directions.
That should be a good sign.
Now, out of curiosity, I'm just gonna go
all the way back to router four, where we begin this thing. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
all the way back to router four, where we begin this thing.
Show IP route, we should see a route to 10.1.7,
aha, now via 10.2.4.
So, now if I do, let's just hit up a few times, trace route.
Okay, it went to two, four, one, two, one, three,
three, five, five, seven.
Let's confirm that's what we wanted.
It goes to two, four, one, two, one, three, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
It goes to two, four, one, two, one, three,
three, five, one, seven.
We are now routing traffic in the correct way.