EIGRP process crash

Kevin Dorrell · ‎10-28-2007

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 141.11.102.1 on Serial2 from LOADING to FULL, Loading Done

Oct 28 17:27:38.721: %BGP-5-ADJCHANGE: neighbor 141.11.106.1 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 141.11.101.1 Up

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

Oct 28 17:27:50.109: destroy peer: 141.11.25.2

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

Oct 28 17:27:50.857: destroy peer: 141.11.65.6

Oct 28 17:27:51.549: %OSPFv3-5-ADJCHG: Process 100, Nbr 141.11.106.1 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

Luxembourg

Richard Burts · ‎10-28-2007

Kevin

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?

HTH

Rick

HTH

Rick

Kevin Dorrell · ‎10-30-2007

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

Luxembourg