RE: EIGRP adjacency Flapping

From: Ahsan Mohiuddin (ahsan.mohiuddin@yahoo.com)
Date: Mon Mar 17 2008 - 04:45:39 ART


You are using the "neighbor" command under eigrp 100 on R3 and R1, right?

cisco-addicted <cisco.addicted@gmail.com> wrote: Dears,

 No ip split-horizon eigrp 100 already configured, and I am running , and I
am using real 2811 routers with 256/64 memory. Even I checked the process
for CPU & memory and it is in the normal level.

 

 

Regards

 

Moe

From: Jonathan Greenwood II [mailto:gwood83@gmail.com]
Sent: Monday, March 17, 2008 3:55 AM
To: cisco-addicted
Subject: Re: EIGRP adjacency Flapping

 

I would start with maybe on the Hub interface disabling eigrp split horizon:

 

no ip split-horizon eigrp 100

 

R/

 

Jonathan

On Sun, Mar 16, 2008 at 7:42 PM, cisco-addicted
wrote:

Dears,

 I configured a partial frame relay between three routers (R1, R2 & R3) with
R2 as a HUB and R1 & R3 the spokes.

The L2 configuration for mapping the DLCI is working fine and I can ping all
the interfaces with broadcast keywork added in the mapping statement.

The problem is we I configured the EIGRP AS 100 between them the adjacency
come up, but I always got the following error in R3 ( the spoke) mentioning
that the other Spoke's IP address is not down.!!!!!

May someone explain what is the reason for this flapping???

Rack1R3(config-router)#

*May 9 05:25:03.785: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
183.1.123.1 (Serial1/0) is down: retry limit exceeded

Rack1R3(config-router)#

*May 9 05:25:49.965: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
183.1.123.1 (Serial1/0) is up: new adjacency

Rack1R3(config-router)#

Rack1R3#

*May 9 05:26:01.445: %SYS-5-CONFIG_I: Configured from console by console

Rack1R3#

*May 9 05:28:54.477: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
183.1.123.1 (Serial1/0) is down: retry limit exceeded

Rack1R3#

*May 9 05:29:20.069: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
183.1.123.1 (Serial1/0) is up: new adjacency

Rack1R3#

Thanks in advance gang.

Moe



This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:53 ART