EIGRP Hold Time and Hello Packets

Most people have learned that the EIGRP hold timer is renewed when it receives a hello packet from a neighbor. This is correct however the hello packet is not the only packet that renewes it…all EIGRP packets do. In order to demonstrate this we’ll take a look at the following two routers:

R1 R2 EIGRP AS 12

First I will configure EIGRP on both routers, nothing special I just want to make sure we have a neighbor adjacency:

R1(config)#router eigrp 12
R1(config-router)#network 192.168.12.0
R2(config)#router eigrp 12
R2(config-router)#network 192.168.12.0

Now I will increase the hold time so it doesn’t drop the neighbor adjacency so quickly. I’ll set it to 1 hour:

R2(config-if)#ip hold-time eigrp 12 3600

When we take a look at R1 you’ll see that it uses 3600 seconds as the hold time for R2:

R1#show ip eigrp neighbors 
IP-EIGRP neighbors for process 12
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
0   192.168.12.2            Fa0/0            3597 00:00:51    3   200  0  21

We have 3597 seconds and counting…now I will set the hello timer to a low value so that we can find out if other EIGRP packets will renew the hold time. I’ll set it to 5 minutes:

R2(config)#interface fastEthernet 0/0
R2(config-if)#ip hello-interval eigrp 12 300

R1 will now only receive a hello packet from R2 every 5 minutes. To show that different EIGRP packets will renew the hold time I will enable a debug on R1 so that we can see what kind of packets it receives from R2:

R1#debug eigrp packets 
EIGRP Packets debugging is on
    (UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)

Now I will create a new loopback interface on R2 and advertise it in EIGRP. This will cause some traffic between R1 and R2. Before I do this, let’s take a quick look at the current state of the hold time again:

look again at table:

R1#show ip eigrp neighbors 
IP-EIGRP neighbors for process 12
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
0   192.168.12.2            Fa0/0            3504 00:04:23    3   200  0  21

Right now we are down to 3504 seconds…let’s advertise that loopback interface in EIGRP:

We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 655 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

535 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Forum Replies

  1. Yesterday I did the same lab, hehe, same results.

    R2#show ip eigrp neighbors
    EIGRP-IPv4 Neighbors for AS(1)
    H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                                (sec)         (ms)       Cnt Num
    0   192.168.1.1             Fa1/0            167 00:17:51   81   486  0  17
    
    R2#
    *Sep 11 19:02:43.279: EIGRP: Received QUERY on FastEthernet1/0 nbr 192.168.1.1
    *Sep 11 19:02:43.279:  AS 1, Flags 0x0:(NULL), Seq 18/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
    *Sep 11 19:02:43.283: EIGRP: Enqueuein
    ... Continue reading in our forum

  2. Hi Rene,

    In case of hybrid FR hub and spoke configuration, all with serial interfaces ( R1 is the hub router - with 2 logical sub-interfaces, one point-to-point, and another one multipoint, R2 is a spoke router for the point-to-point connection, R3,R4,R5 are the spokes for the multipoint connection). In this case, R1 point-to-point subif has different timer values (Hello: 5s) than the multipoint subif (Hello: 60s) as the latter is considered to be slower link. However all this hub-and-spoke topology is configured in one EIGRP AS (AS:100). My question is do we n

    ... Continue reading in our forum

  3. Hello Kostas

    This is an excellent question and it reveals some of the nuances of EIGRP.

    When using Ethernet as the layer 2 protocol, holdown and hello timers for EIGRP don’t have to be consistent over the whole AS. Each EIGRP neighbour relationship must have its timers configured correctly, but those can be different from relationship to relationship. However there is one case where timers must be configured the same, and this is the case you describe above.

    This case is when you have multiple routers on a network that form adjacencies. All those routers mus

    ... Continue reading in our forum

  4. Hello Laz,

    Your answer is really helpful and I appreciate your time to respond me.
    Thank you for clarifying my concerns. :slight_smile:

    Kostas

1 more reply! Ask a question or join the discussion by visiting our Community Forum