Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

EIGRP process crash

Running 12.2(15)T17 in a lab environment on a 2520. Half way through my lab exercise, this router suddenly has no EIGRP neighbors. The neighbors still think they have adjacencies. Then they start flapping too - not through dead-time, but because retry exceeded.

Looking back through the log, I find, just following a reload:

Oct 28 17:27:38.197: %OSPFv3-5-ADJCHG: Process 100, Nbr on Serial2 from LOADING to FULL, Loading Done

Oct 28 17:27:38.721: %BGP-5-ADJCHANGE: neighbor Up

<b>Oct 28 17:27:41.981: %SCHED-3-UNEXPECTEDEVENT: Process received unknown event (maj 0, min 0).

-Process= "IP-EIGRP: HELLO", ipl= 0, pid= 93

-Traceback= 381B580</b>

Oct 28 17:27:45.841: %BGP-5-ADJCHANGE: neighbor Up

Oct 28 17:27:50.093: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 12: Neighbor (Serial2) is down: holding time expired

Oct 28 17:27:50.109: destroy peer:

Oct 28 17:27:50.789: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 12: Neighbor (Ethernet0) is down: holding time expired

Oct 28 17:27:50.857: destroy peer:

Oct 28 17:27:51.549: %OSPFv3-5-ADJCHG: Process 100, Nbr on OSPF_VL0 from LOADING to FULL, Loading Done

Has anyone any idea what that could be about? At the time, I was not touching anything to do with the EIGRP. The only thing that should have been going on was some IPv6 routes turning up through the OSPFv3.

Kevin Dorrell


Hall of Fame Super Silver

Re: EIGRP process crash


Interesting issue. I have not seen it and do not have any particular information about it. But to make the obvious point: a Traceback is always a sign of some software issue. I wonder if it might be its response to unexpected traffic (perhaps IPv6). Have you tried the output interpreter or the error decoder on CCO?



Re: EIGRP process crash

Well, I looked on the error decoder, and as I expected I got the usual "This indicates an internal software error. Please contact your support team.", which is not much good to me.

I have narrowed it down a bit. It is definitely a software issue: I swapped over two routers in the topology, and the bug moved - that is, it was on R5, after the swap it was still on R5.

It seems that my R5 does not like IPv4 EIGRP and IPv6 OSPF running through the same Ethernet0 interface on a 2520. It's partner, R6, has a very similar topology but does not show the same symptom. On the other hand, R6 is a 2611, and the interface is a subinterface of F0/0.

I guess I simply will not be able to complete that exercise.

Kevin Dorrell