The 'broadcast' keyword turned out to be the problem.  Thank you Kenny!  I
had it on my side, which is the dialing side, but I did not notice that it
was missing on the remote side.  I also didn't realize that the broadcast
keyword handles both broadcasts AND multicasts.  This is why my hellos were
making it to his side, but not vice versa.

Many, many thanks to all who contributed to this thread. I owe all of you
lunch sometime.  :-)  If you all are in Denver sometime, look me up!  heh
heh....  Just don't show up all at once, my wallet wouldn't survive.

John

>  Why don't you post the configs?  Also send them to me @
[EMAIL PROTECTED]
>  
>  It sounds like a config problem.  Are you using dialer-watch?  What does
>  your dialer-list look like?  Do you have the "broadcast" keyword on your
map
>  statements?  On both sides?
>  
>  Kenny
>  
>  ""Frank Wells"" <[EMAIL PROTECTED]> wrote in message
>  [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>  > You really need to downgrade both routers to be sure.
>  >
>  >
>  > >From: John Neiberger <[EMAIL PROTECTED]>
>  > >To: Frank Wells <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>  > >Subject: Re: I'm stumped! (was EIGRP over ISDN) LONG
>  > >Date: Wed, 3 Jan 2001 08:53:49 -0800 (PST)
>  > >
>  > >Yes, we've tried 11.2(19), 12.0(14) and 12.1(5) on this end.  The
remote
>  > >side has been on 12.0(5) the entire time and they are not able to
change
>  at
>  > >this time.  Since it appears to be an issue with the timers, we can
set
>  > >those with ios commands and hopefully alleviate the problem.
>  > >
>  > >Thanks,
>  > >John
>  > >
>  > > >  Have you tried downgrading IOS to a more experienced version, just
to
>  > >see
>  > >if
>  > > >  your problem goes away?
>  > > >
>  > > >
>  > > >  >From: John Neiberger <[EMAIL PROTECTED]>
>  > > >  >Reply-To: John Neiberger <[EMAIL PROTECTED]>
>  > > >  >To: [EMAIL PROTECTED]
>  > > >  >Subject: I'm stumped! (was EIGRP over ISDN) LONG
>  > > >  >Date: Wed, 3 Jan 2001 07:51:11 -0800 (PST)
>  > > >  >
>  > > >  >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]
>  > > >
>  > > >  _________________________________________________________________
>  > > >  Get your FREE download of MSN Explorer at http://explorer.msn.com
>  > > >
>  > > >  _________________________________
>  > > >  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/
>  > >
>  > >
>  >
>  > _________________________________________________________________
>  > Get your FREE download of MSN Explorer at http://explorer.msn.com
>  >
>  > _________________________________
>  > FAQ, list archives, and subscription info:
>  http://www.groupstudy.com/list/cisco.html
>  > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>  >
>  
>  
>  _________________________________
>  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]

Reply via email to