|
0:00:13
|
Next, we have the timers in EIGRP
|
|
0:00:16
|
that are gonna control how often
|
|
0:00:20
|
and how longer waiting before
|
|
0:00:24
|
but we'll see that the logic here is a
|
|
0:00:29
|
where typically, like in OSPF, we have the
|
|
0:00:34
|
which control how often
|
|
0:00:37
|
and how long we would wait for
|
|
0:00:41
|
before we declare them as
|
|
0:00:45
|
Now, with EIGRP, it's actually the opposite.
|
|
0:00:49
|
The hello interval does control how
|
|
0:00:55
|
but the EIGRP hold time is the value
|
|
0:01:01
|
to tell the remote neighbor how
|
|
0:01:06
|
So, the hold time configured on
|
|
0:01:09
|
the remote neighbor,
|
|
0:01:12
|
Now also, the timers do not have to match
|
|
0:01:18
|
but really, there's no reason why
|
|
0:01:21
|
So, you can set them as
|
|
0:01:25
|
there's not really any logic as to
|
|
0:01:29
|
Now, we can see this when we
|
|
0:01:31
|
and look at the Show IP
|
|
0:01:39
|
we see that for the...
|
|
0:01:42
|
Fast Ethernet 0/1 link, the
|
|
0:01:47
|
Whereas on serial 0/0/0,
|
|
0:01:52
|
So, depending on what the
|
|
0:01:55
|
the hello interval is gonna
|
|
0:01:59
|
Now, if we were to look at the
|
|
0:02:03
|
let's go to the main documentation.
|
|
0:02:08
|
Then, to IOS.
|
|
0:02:11
|
Cisco IOS.
|
|
0:02:12
|
And in this case, I'm gonna try
|
|
0:02:16
|
because remember, we saw before, the...
|
|
0:02:19
|
the EIGRP Command Reference is not linked
|
|
0:02:25
|
So, let's go to 12.2 Mainline.
|
|
0:02:32
|
then, Command References.
|
|
0:02:36
|
Then, the Routing Protocol
|
|
0:02:40
|
and then, the EIGRP Commands.
|
|
0:02:42
|
So, we'll see in here, there's not gonna
|
|
0:02:47
|
but the vast majority of the EIGRP topics
|
|
0:02:52
|
and any of the current releases.
|
|
0:02:56
|
So,if we look at the IP hello interval,
|
|
0:03:01
|
it says that "The...
|
|
0:03:04
|
IP hello interval..."
|
|
0:03:13
|
It says, "For low speed non-broadcast
|
|
0:03:18
|
For all other networks, it's 5."
|
|
0:03:23
|
Then, for the hold time,
|
|
0:03:25
|
it says, "For NBMA, the hold time is 180
|
|
0:03:33
|
But you can see from the
|
|
0:03:35
|
it doesn't really tell us that the hold
|
|
0:03:41
|
not the local neighbor.
|
|
0:03:46
|
So, if we were to go to...
|
|
0:03:56
|
router 5's configuration here, and we'll go
|
|
0:04:02
|
We'll say that our IP EIGRP, or IP hello...
|
|
0:04:07
|
hello interval for EIGRP AS number 1,
|
|
0:04:10
|
we'll say that this is every 10 seconds.
|
|
0:04:14
|
And the IP hold time for
|
|
0:04:20
|
If we now go to the remote end on switch 2,
|
|
0:04:29
|
we see that for router 5,
|
|
0:04:31
|
it says that the hold time
|
|
0:04:37
|
So, it means that 3 seconds
|
|
0:04:39
|
If we keep looking at this detailed output,
|
|
0:04:42
|
we'll see that the countership
|
|
0:04:47
|
because router 5 should be
|
|
0:04:51
|
But when we look at switch 2
|
|
0:04:57
|
we see that on our VLAN 58,
|
|
0:05:00
|
the hello interval is 5 seconds,
|
|
0:05:03
|
which is not the same as we
|
|
0:05:06
|
So, even though the different values were
|
|
0:05:10
|
On router 5, if we look at the
|
|
0:05:20
|
it says that "For switch 2, the
|
|
0:05:27
|
We'll see that since the default hello is 5 and the
|
|
0:05:34
|
Then, this output should never
|
|
0:05:38
|
Assuming that the neighbor is up.
|
|
0:05:41
|
So, every 5 seconds, we're gonna
|