cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
91711
Views
44
Helpful
31
Replies

EIGRP continually flapping

pugs17211721
Level 1
Level 1

This is the message that I am getting from my 1941w router. I have a isakmp tunnel built with a GRE tunnel going through it. I keep getting the following message, continously.

Nov 16 08:58:09.352 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 08:59:47.361 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 08:59:51.217 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 09:01:27.230 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 09:01:27.782 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 09:03:03.792 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 09:03:04.372 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 09:04:40.381 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 09:04:40.909 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 09:06:13.774 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 09:06:18.282 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 09:07:54.296 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 09:07:58.436 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

Nov 16 09:09:29.521 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is down: Interface PEER-TERMINATION received

Nov 16 09:09:30.233 EST: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.20.255.97 (Tunnel31) is up: new adjacency

The other end of the device is a 2801 router and it doesnt show anything in the logs. Anyone have any ideas? Thanks.

31 Replies 31

You are advertising the tunnel source in the eigrp statement.   If this is the preferred route on the remote end you end up with recursive routing.  Recommended to remove "network 172.20.0.0" and put in 172.20.255.96 0.0.0.3 so you are not advertising the tunnel source through the tunnel routing protocol.

Dan

I had a similar problem and got it resolved..

On the dmvpn spoke, (GRE over ipsec) the tunnel was continually flapping.

the public ip address on the dmvpn spoke is 99.X.X.X

Upon debug I realized that there is a static route on the peer (hub router) poining to 99.x.x.x which is again redistributed into eigrp..so spoke router is now having this as a local route as well as a route redistributed via eigrp ..so it was falpping..

i fixed this by implementing a block route-map..

hope this helps...

Regards Vinayak

What I did to fix my issue that I was having above was to lower my MTU on the tunnel interface. After I changed that to 1400 everything else has worked smoothly.

Hello,

Oh yes - that's yet another issue to have in mind - large routing tables compounded with MTU issues on tunnel interfaces. Thanks for sharing and reminding us of that!

Best regards,

Peter

MajidShirzadeh
Level 1
Level 1

Hi Guys !

I got DUAL-5-NBRCHANGE error after I turn up a site to MPLS network, could you help me with that please ?

Feb  1 11:35:12.008 Central: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(512) 1: Neighbor 192.168.201.74 (Tunnel18) is down: holding time expired

Feb  1 11:50:01.486 Central: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(512) 1: Neighbor 192.168.201.74 (Tunnel18) is up: new adjacency

Feb  1 19:25:50.005 Central: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(512) 1: Neighbor 10.1.150.6 (GigabitEthernet8/33) is down: interface down

Feb  1 19:26:03.742 Central: %SYS-5-CONFIG_I: Configured from console by mgriffin on vty0 (10.1.211.93)

Feb  1 19:29:12.434 Central: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(512) 1: Neighbor 10.1.150.6 (GigabitEthernet8/33) is up: new adjacency

Feb  1 19:33:40.546 Central: %SYS-5-CONFIG_I: Configured from console by mgriffin on vty0 (10.1.211.93)

Feb  1 21:31:38.013 Central: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(512) 1: Neighbor 192.168.201.66 (Tunnel16) is down: Interface PEER-TERMINATION received

Feb  1 21:31:41.509 Central: %DUAL-5-NBRCHANGE: EIGRP-IPv4:(512) 1: Neighbor 192.168.201.66 (Tunnel16) is up: new adjacency

Majid,

The reason may very well be similar to the issues already described in this thread. Have you carefully went each suggestion posted here so far and made sure that none of them applies to you? In particular, are you sure you do not advertise the network in which the tunnel endpoint resides through the EIGRP running over that tunnel?

Best regards,

Peter

Here is my MTU size!

Core site, MTU Size on tunnel interface =17868 and customer tunnel MTU size = 1514, so what do you think ?

I set mine at 1400, but how I got there was through trial and error. I was at 1514, adjusted it to 1300 and it worked better. Then i slowly workd my way up the chain to find out where the stable point is and left it ther.

hlopez606
Level 1
Level 1

I have the same error, what I can do?

 

1y13w: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.16.20.250 (Vlan2) is up: new adjacency
1y13w: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.16.20.250 (Vlan2) is down: holding time expired

Perhaps you can give us some more information about your environment? How often does this happen?

 

The error message indicates that holding time expired. This means that you have established a neighbor relationship, that you have sent EIGRP packets to the neighbor and the neighbor has not responded.  The holding time is the amount of time that you wait for a response. So there is a possibility that the real issue may be on the neighbor and not on your router.

 

HTH

 

Rick

HTH

Rick

deepak george
Level 1
Level 1

Dear Members,

 

Do we have a solution for the same as we faced the same issue wherein the tunnel keeps flapping with the same error message, however there is no downtime reported. Please advise what to do