cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
625
Views
0
Helpful
2
Replies

EIGRP down, but pings OK?

ronayu
Level 1
Level 1

EIGRP neighbor just went down.

-------------------------------------------

Feb 16 01:43:14.477 CET: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 109: Neighbor 10.63.1.230 (GigabitEthernet0/3.130) is down: holding time expired

The neighbor is not on sh eigrp neigh

---------------------------------------------------

The interface is up/up.

--------------------------------------

gw2#sh int g0/3.130

GigabitEthernet0/3.130 is up, line protocol is up

gw2#sh ip ro 10.63.1.230

Routing entry for 10.63.1.228/30

  Known via "connected", distance 0, metric 0 (connected, via interface)

  Redistributing via eigrp 109

  Routing Descriptor Blocks:

  * directly connected, via GigabitEthernet0/3.130

      Route metric is 0, traffic share count is 1

but pings to the neighbor are ok.

-----------------------------------------------

Sending 5, 100-byte ICMP Echos to 10.63.1.230, timeout is 2 seconds:

!!!!!

How does it ping?

2 Replies 2

SOcchiogrosso
Level 4
Level 4

Looks like your pinging a connected interface connected interfaces are always in the routing table sine they are connected.

Sent from Cisco Technical Support iPad App

-- CCNP, CCIP, CCDP, CCNA: Security/Wireless Blog: http://ccie-or-null.net/

I can understand the confusion about the EIGRP neighbor being down but ping to the neigbor address still works. For explanation let us start with the consideration that EIGRP neighbor down does not mean that neighbor host is down but only that something has impacted the EIGRP process.

Then let us look a bit closer at the message when the neighbor went down. It says that "holding time expired". This means that the router has missed 3 EIGRP hello messages from the neighbor and declares that the neighbor relationship needs to be re-initialized. So what would make the router miss 3 hello messages? Perhaps there is congestion on the link and the hello packets got dropped? Perhaps there is something on the neighbor router that impacted its EIGRP process? There might be other reasons why the hello packet did not get through but that would not prevent the ping packet and the ping response.

HTH

Rick

HTH

Rick