EIGRP Adjacency Dropping

[Natalia Woloseckyj]

Hi All,

I have a production L3 3750 stack with 2 WAN connections, which is connected to the companies WAN infrastructure using EIGRP.

Recently there have been a number of hello drops from one site, which is causing the EIGRP adjacency to drop and so the whole site goes down from the rest of the WAN.

Physical cabling has been replaced towards the ISP router, and the ISP have found no issues on their equipment or circuit.

Can anyone advise why this could be happening, on occassions the utilisation is high on the link, so reasons for the hello packets to be not reach the end point, but other times the links are lowly used.

The WAN links are active/standby, so the active is always used, but the EIGRP adjacency is dropped by both links.

Advise????

Many Thanks,

Natalia                

[paul driver]

Hello,

Depending on what IOS you are running, when the eigrp adjacency is being dropped it will get reported in the log buffer regarding the reason for the reset, eigrp log-neighbor-changes under the eigrp process is set to deatult for newer ios's

if possible can you post the logs for this issue.

res

Paul

Please don't forget to rate this post if it has been helpful.

[Natalia Woloseckyj]

You can see from the log that the STUB is denying the hello packets, which is the ISP router....

Mar  4 08:55:53.916 GMT: EIGRP: Holdtime expired

Mar  4 08:55:53.916 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.60 (VlanXXX) is down: holding time expired

Mar  4 08:55:53.916 GMT: Going down: Peer 10.200.0.60 total=1 stub 0, iidb-stub=0 iid-all=1

Mar  4 08:55:53.916 GMT: EIGRP: Handle deallocation failure [1]

Mar  4 08:55:53.933 GMT: EIGRP: Neighbor 10.200.0.60 went down on VlanXXX

Mar  4 08:55:53.933 GMT: EIGRP: Enqueueing QUERY on VlanXXX tid 0 iidbQ un/rely 0/1 serno 9584-9586

Mar  4 08:55:53.941 GMT: EIGRP: Build goodbye tlv for 10.200.0.60

Mar  4 08:55:53.941 GMT: EIGRP: Sending HELLO on VlanXXX

Mar  4 08:55:53.941 GMT:   AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/1

Mar  4 08:55:53.941 GMT: EIGRP-IPv4(1): table(Default-IP-Routing-Table): 172.100.00.176/32 - denied by stub

Mar  4 08:55:53.941 GMT: EIGRP-IPv4(1): table(Default-IP-Routing-Table): 192.168.200.148/30 - denied by stub

Mar  4 08:55:53.941 GMT: EIGRP-IPv4(1): table(Default-IP-Routing-Table): 192.168.250.148/30 - denied by stub

Mar  4 08:55:53.941 GMT: EIGRP: Sending QUERY on VlanXXX tid 0

Mar  4 08:55:53.941 GMT:   AS 1, Flags 0x0:(NULL), Seq 531/0 interfaceQ 0/0 iidbQ un/rely 0/0 serno 9584-9586

Mar  4 08:55:54.143 GMT: EIGRP: Holdtime expired

Mar  4 08:55:54.151 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.57 (VlanXXX) is down: holding time expired

Mar  4 08:55:54.151 GMT: EIGRP: Sending HELLO on VlanXXX

Mar  4 08:55:54.151 GMT:   AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0

Mar  4 08:55:54.151 GMT: Going down: Peer 10.200.0.57 total=0 stub 0, iidb-stub=0 iid-all=0

Mar  4 08:55:54.151 GMT: EIGRP: Handle deallocation failure [0] Mar  4 08:55:53.916 GMT: EIGRP: Holdtime expired
Mar  4 08:55:53.916 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.60 (VlanXXX) is down: holding time expired
Mar  4 08:55:53.916 GMT: Going down: Peer 10.200.0.60 total=1 stub 0, iidb-stub=0 iid-all=1
Mar  4 08:55:53.916 GMT: EIGRP: Handle deallocation failure [1]
Mar  4 08:55:53.933 GMT: EIGRP: Neighbor 10.200.0.60 went down on VlanXXX
Mar  4 08:55:53.933 GMT: EIGRP: Enqueueing QUERY on VlanXXX tid 0 iidbQ un/rely 0/1 serno 9584-9586
Mar  4 08:55:53.941 GMT: EIGRP: Build goodbye tlv for 10.200.0.60
Mar  4 08:55:53.941 GMT: EIGRP: Sending HELLO on VlanXXX
Mar  4 08:55:53.941 GMT:   AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/1
Mar  4 08:55:53.941 GMT: EIGRP-IPv4(1): table(Default-IP-Routing-Table): 172.100.00.176/32 - denied by stub
Mar  4 08:55:53.941 GMT: EIGRP-IPv4(1): table(Default-IP-Routing-Table): 192.168.200.148/30 - denied by stub
Mar  4 08:55:53.941 GMT: EIGRP-IPv4(1): table(Default-IP-Routing-Table): 192.168.250.148/30 - denied by stub
Mar  4 08:55:53.941 GMT: EIGRP: Sending QUERY on VlanXXX tid 0
Mar  4 08:55:53.941 GMT:   AS 1, Flags 0x0:(NULL), Seq 531/0 interfaceQ 0/0 iidbQ un/rely 0/0 serno 9584-9586
Mar  4 08:55:54.143 GMT: EIGRP: Holdtime expired
Mar  4 08:55:54.151 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.57 (VlanXXX) is down: holding time expired
Mar  4 08:55:54.151 GMT: EIGRP: Sending HELLO on VlanXXX
Mar  4 08:55:54.151 GMT:   AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
Mar  4 08:55:54.151 GMT: Going down: Peer 10.200.0.57 total=0 stub 0, iidb-stub=0 iid-all=0
Mar  4 08:55:54.151 GMT: EIGRP: Handle deallocation failure [0]

[paul driver]

Hello,

So all layer 1-2 possible issues have been checked?

Can you:
ping the peer when the neighbor relationship resets?
ping 224.0.0.10 - do you get a responce?

debug eigrp packet hello

You can also try increasing the eigrp hold time?

res

Paul

Please don't forget to rate this post if it has been helpful.

[Natalia Woloseckyj]

Unfortunately the switch is remote, so this cannot be executed until the link has been re-established.

What would be the answer if you could or not ping whilst it is being reset?

[paul driver]

Hello

This is could suggest a possible physical connectivity issue between your site and the ISP.

Has any recent changes on your network been performed - be it physical or software/config etc.. which would effect connection?

The error being reported is stating eigrp hasn't received a response to it hello's towards its peer and the hold-down timer
( 3x the hello interval) has expired.

Could you post the running config of your sites router and if possible the output frm the debug eigrp packets hello

res

Paul

Please don't forget to rate this post if it has been helpful.

[Natalia Woloseckyj]

Mar  4 08:45:56 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received

Mar  4 08:46:01 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 08:55:54 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received

Mar  4 08:55:58 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 09:05:58 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Peer Termination received

Mar  4 09:06:02 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 09:06:10 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received

Mar  4 09:06:15 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 09:21:10 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Peer Termination received

Mar  4 09:21:15 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 09:21:35 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received

Mar  4 09:21:40 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 10:20:42 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Peer Termination received

Mar  4 10:20:47 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

Mar  4 10:21:02 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received

Mar  4 10:21:06 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency Mar  4 08:45:56 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received
Mar  4 08:46:01 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 08:55:54 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received
Mar  4 08:55:58 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 09:05:58 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Peer Termination received
Mar  4 09:06:02 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 09:06:10 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received
Mar  4 09:06:15 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 09:21:10 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Peer Termination received
Mar  4 09:21:15 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 09:21:35 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received
Mar  4 09:21:40 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 10:20:42 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Peer Termination received
Mar  4 10:20:47 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency
Mar  4 10:21:02 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is down: Interface PEER-TERMINATION received
Mar  4 10:21:06 GMT: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.200.0.59 (GigabitEthernet0/1) is up: new adjacency

This is the log from the ISP router....

[paul driver]

Hello,

Is the eigrp config the same on either side of this connection?

Any ACLs active?

Show ip eigrp neigbours from both sides of the connectiom?

res

Paul

Please don't forget to rate this post if it has been helpful.