WS-C4500X EIGRP adjacency holding time expired

[guyandriano]

Hi

I have a WS-C4500X-32  at my core connected to 3 WAN routers 2 x C2911 and 1 x C2811 running EIGRP. All four devices form adjacency with each other via a dedicated vlan on the WS-C4500X.

Today the WS-C4500X lost adjacency with all three routers, however the routers maintained adjacency with each other.

Anyone have any idea what could cause this, is this a know issue with the cat4500e-UNIVERSALK9-M), Version 03.05.00.E 

Router IOS 

C2911  c2900-universalk9-mz.SPA.153-3.M2.bin

C2911 c2900-universalk9-mz.SPA.151-4.M4.bin

C2811 c2800nm-adventerprisek9-mz.124-25d.bin

Any help would be most appreciated

Sep 25 17:23:33.980 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.3 (Vlan200) is down: holding time expired
Sep 25 17:23:39.231 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.3 (Vlan200) is up: new adjacency
Sep 25 17:25:42.572 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.10 (Vlan200) is down: holding time expired
Sep 25 17:25:46.392 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.10 (Vlan200) is up: new adjacency
Sep 25 17:30:37.511 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.3 (Vlan200) is down: holding time expired
Sep 25 17:30:42.531 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.3 (Vlan200) is up: new adjacency
Sep 25 17:34:29.760 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.2 (Vlan200) is down: holding time expired
Sep 25 17:34:32.724 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.2 (Vlan200) is up: new adjacency
Sep 25 17:35:02.841 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.10 (Vlan200) is down: holding time expired
Sep 25 17:35:05.908 gmt: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.2.55.10 (Vlan200) is up: new adjacency

[Richard Burts]

I do not know for sure what is causing this but I do have some thoughts to share. Remember that EIGRP processes send hello packets and expect to receive hello packets. The error of holding time expired indicates that your switch EIGRP process did not receive hello packets from the neighbor. It is interesting that the issue happens with each neighbor but not at the same time. I wondered about the possibility of something like a broadcast storm that could impact receipt and forwarding of hello packets. But something like that would more likely impact the neighbors at the same time. Is this happening consistently (and if so how frequently) or is this more of an isolated instance?

HTH

Rick

[guyandriano]

Hi Richard, thanks for taking the time.

This is the first time it has happened on this network. Although I only installed the 4500X VSS stack on Saturday. Everything has been fine apart from this incident Cisco Tac have no idea either.

I have attached a diagram of the network, the routers are circles switches ovals and blue.

I'm thinking its more a bug with the 4500 code as strange that the routers received the hello mcasts but not the switch. Traffic between router traverses the switch that didn't receive the hello's.

Aslo the 200 vlan is dedicated only for eigrp, so only 4 hosts in that vlan 3 routers and the switch stack.