EIGRP - holding time expired

Unanswered Question
Feb 4th, 2007


what will be cause holding time expired in eigrp?


Feb 2 14:30:18.635: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor (Vlan1) is down: holding time expired

Feb 2 14:32:39.708: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor (Vlan1) is up: new adjacency



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Amit Singh Mon, 02/05/2007 - 00:39

Hi Samuel,

The neighbor is flapping up and down due to holding time expired. This means the router did not receive an eigrp packet from its neighbor and the hold time expired,causing the neighbor to reset.

%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor (Vlan1)) is down: holding time expired

"If no hellos are received within the hold time, which is 15 seconds by default on most links, the router informs the neighbor that the neighbor relationship has been torn down and logs a syslog message."

1. Send a stream of 10000 count, once using 100 byte and once using 1500 byte packets,using extended

ping, to the neighbor's directly connected interface IP address. Are there any packet drops or time


Does the neighbor respond if you ping the EIGRP multicast address

2. Perform "debug eigrp packet hello" on both routers to verify that the neighbors are ending and receiving EIGRP hello packets.

Check the routing table entry to verify the next-hop address is correct for the neighbor.

3. Other possibilities that can bring the neighbor relationship down are unidirectional links, uncommon subnet mismatches, mismatched masks, layer 2 problems, ACL deny statement, etc.

The detailed steps can be found here:

Troubleshooting EIGRP - Neighbor Check


HTH,Please rate if it does.

-amit singh

sivaprasad.bpavan Mon, 04/18/2016 - 06:42

Try to remove the interface running the dynamic routing from eigrp network.

Please reply if works or not. 


This Discussion