[c-nsp] problem with EIGRP

[Cheung, Rick]

	It may be this: CSCsa43492, an input queue wedge on the T0 of the
other router. The sending router would have a queue count > 0, and the
receiving router's input T0 interface would have an input queue size > max
size.

	It's fixed in 12.3.13.

	Or, it could be an MTU issue on the T0 interface. Try the ip mtu
1400 on both ends of the T0 interface. The EIGRP queue count should
decrement quickly after configuration.



Thanks,
Rick Cheung

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of MADMAN
Sent: Monday, February 21, 2005 10:37 AM
To: Nikolay Abromov
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] problem with EIGRP


   Though I don't see the recursive routing error are you running into this:

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094690
.shtml

   Dave



Nikolay Abromov wrote:
> Hi There, 
> 
> 
> I've got a problem with EIGRP, I run eigrp session over tunnel and the
> session
> goes down in about 1min. below there are some logs from both routers
> 
> 
> Router A (7206 VXR-NPE-G1,IOS version 12.3.12) 
> 
> %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1111: Neighbor 1.1.1.1 (Tunnel3) is down:
> retry limit exceeded
> %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1111: Neighbor 1.1.1.1 (Tunnel3)
> %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1111: Neighbor 1.1.1.1 (Tunnel3) is down:
> retry limit exceeded
> %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1111: Neighbor 1.1.1.1 (Tunnel3) is up:
> new adjacency
> 
> 
> Router B (1750, IOS version 12.1.20)
> 
> EIGRP: Received HELLO on Tunnel1 nbr 1.1.1.2
> AS 1111, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0
> K-value mismatch
> 
> I verified the configurations of both routers and assured there is no
> mismatch
> of k-values,this is the output of 'show ip protocols" 
> 
> router A>
> Routing Protocol is "eigrp 1111"
>   EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
> 
> router B>
> Routing Protocol is "eigrp 1111"
>   EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
> 
> 
> I also noticed that they'r 13 update messages which are constantly
> pending
> in the queue.
> 
> 
> "show ip eigrp neigh" 
> 
> H   Address                 Interface       Hold Uptime   SRTT   RTO  Q
> Seq
>                                                             (sec)
> (ms)               Cnt Num
> 8   1.1.1.1          Tu3               11 00:00:50  150  5000 13  4695
> 
> 
> Has anyone experienced similar problem?
> 
> 
> 
> 
> Best Regards,
> Nikolay Abromov
> network administrator
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 

-- 
David Madland
CCIE# 2016
Sr. Network Engineer
Qwest Communications
612-664-3367

"Emotion should reflect reason not guide it"
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


This message, including any attachments, contains confidential information intended for a specific
individual and purpose and is protected by law. If you are not the intended recipient, please contact
sender immediately by reply e-mail and destroy all copies. 
You are hereby notified that any disclosure, copying, or distribution of this message, or the taking 
of any action based on it, is strictly prohibited.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email
and any attachments for the presence of viruses. The sender accepts no liability for any damage 
caused by any virus transmitted by this email. E-mail transmission cannot be guaranteed 
to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive 
late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors 
or omissions in the contents of this message, which arise as a result of e-mail transmission.