CDP is disabled on both ends and we are in the same 'AS'. I've thought
about the timers because I was reading on CCO that the default hello timer
on a slower link like a BRI is 60 seconds. However, my side is sending
hellos every five seconds as I expected. I need to see if the other side
has default timer settings different from mine. As I mentioned, we are
running 12.1(5) and they have 12.0(5). There just might be a difference in
timer settings.
Thanks for the tip!
> John
>
> Just had a bout with ISDN myself. I would check the following things.
CDP
> on the interface? Same AS number? Timer setting the same on both? Lastly
> check to for adjency or in other words all numbers the same
>
> Hope it helps
> Bill Harrison
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> John Neiberger
> Sent: Wednesday, January 03, 2001 9:51 AM
> To: [EMAIL PROTECTED]
> Subject: I'm stumped! (was EIGRP over ISDN) LONG
>
>
> I'm reposting this in the hopes that someone who didn't see it before
might
> have some ideas about this. Heck, SWAGs, educated guesstimates, or
> telephone psychic impressions are also welcome. We are completely
stumped
> about how to resolve this. I've even posted this question on the CCO Q&A
> Forum but I don't think anyone has been answering questions on there
lately.
>
> Here is the problem: we have an ISDN BRI backup link between two sites,
and
> we want to run eigrp over the link when it's in use. The problem is that
> even though the line is not flapping, eigrp is behaving as if it were
> flapping. My side NEVER sees hellos from the other side, but it does
> receive updates. The other side receives my hellos, but it thinks the
link
> is bouncing and that my router is intermittently unavailable. My side
never
> establishes the other as a neighbor.
>
> I've used every debugging command I can find to no avail. Nothing is
giving
> me any information that I don't already know. We have no access lists
> configured, except for distribute lists but that shouldn't affect
neighbor
> relationships, should it?
>
> Here is sample debug output (debug eigrp neighbors and debug eigrp
packet):
>
> 3d01h: EIGRP: Sending HELLO on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
>
> 3d01h: EIGRP: Sending HELLO on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
>
> 3d01h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
>
> 3d01h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed
state
> to up
> 3d01h: EIGRP: Sending HELLO on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
>
> 3d01h: EIGRP: Received UPDATE on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x1, Seq 67/0 idbQ 0/0
>
> 3d01h: EIGRP: Neighbor(10.120.226.2) not yet found
>
> 3d01h: EIGRP: Received UPDATE on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x1, Seq 67/0 idbQ 0/0
>
> 3d01h: EIGRP: Neighbor(10.120.226.2) not yet found
>
> 3d01h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 303xxxxxx
> theirrouter
> 3d01h: EIGRP: Sending HELLO on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
>
> 3d01h: EIGRP: Received UPDATE on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x1, Seq 67/0 idbQ 0/0
>
> 3d01h: EIGRP: Neighbor(10.120.226.2) not yet found
>
> 3d01h: EIGRP: Received UPDATE on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x1, Seq 67/0 idbQ 0/0
>
> 3d01h: EIGRP: Neighbor(10.120.226.2) not yet found
>
> 3d01h: EIGRP: Sending HELLO on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
>
> 3d01h: EIGRP: Sending HELLO on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
>
> 3d01h: EIGRP: Received UPDATE on BRI0 nbr 10.120.226.2
>
> 3d01h: AS 2, Flags 0x1, Seq 67/0 idbQ 0/0
>
> 3d01h: EIGRP: Neighbor(10.120.226.2) not yet found
>
> Here is some info from the remote side:
>
> theirrouter#
> 1d02h: EIGRP: Retransmission retry limit exceeded
> 1d02h: EIGRP: Holdtime expired
> 1d02h: EIGRP: Neighbor 10.120.226.1 went down on BRI0/0
> 1d02h: EIGRP: New peer 10.120.226.1
>
> theirrouter#sho ip eigrp neighbors
> IP-EIGRP neighbors for process 2
> H Address Interface Hold Uptime SRTT RTO Q Seq
> (sec) (ms) Cnt Num
> 0 10.120.226.1 BR0/0 12 00:00:38 0 5000 1 0
>
> 1d02h: EIGRP: Retransmission retry limit exceeded
> 1d02h: EIGRP: Holdtime expired
> 1d02h: EIGRP: Neighbor 10.120.226.1 went down on BRI0/0
> 1d02h: EIGRP: New peer 10.120.226.1
>
> I'm not getting any errors on the line, and further debugging (isdn q921,
> isdn q931, ppp error, ppp auth, ppp neg, bri-interface) does not show any
> problems whatsoever. I've tried ping tests with different payloads and
they
> succeeded wonderfully.
>
> I've also made sure that we are in the same 'AS'. We are running 12.1(5)
on
> a 2520, they run 12.0(5) on a 2524. I've searched CCO for any
configuration
> hints or bug reports, and I've read through Doyle's Routing TCP/IP
section
> on eigrp and I can find no possible explanation for this behavior.
>
> Any takers? ideas? hints? tips? Do you know a good psychic or witch
> doctor? Perhaps a good psychiatrist, instead? :-)
>
> For anyone who has taken the time to read through all of this, I thank
you.
>
> Regards,
> John
>
>
>
>
>
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
>
>
> _________________________________
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
