Re: ISDN Problem

From: Kevin Baumgartner (kbaumgar@xxxxxxxxx)
Date: Wed Sep 20 2000 - 21:48:45 GMT-3


   
Well I am not exactly sure what is going on here but thing it might
have something to do with the virtual links. Try removing them on sleepy
and grumpy and see if this keeps the isdn line down.

  Then if this fixes the problem (or even if it doesn't) try
doing debug ip ospf adj
          debug dialer
This may give some clues as to why the ISDN is being called.

  Kevin

At 05:26 PM 9/20/00 -0700, you wrote:
>That's correct. It is very close to a real lab
>scenario according to some romours I heard.
>
>An the thing is, I had it working once. This time it
>doesn't work.
>
>Sam
>--- Daniel Keller <DMKeller@comdisco.com> wrote:
> > The problem is that area 2 is a virtual link.
> > Because of this, LS updates will always keep the
> > line dialing. Can you place the bri connections
> > into a different area? If not you will need to find
> > an alternative, such as using backup interface. Is
> > this from a lab that you have?
> >
> > Dan Keller
> >
> > >>> Sam Munzani <smunzani@yahoo.com> 09/20/00
> > 05:50PM >>>
> > Hi Group,
> >
> > I have attached my configs with e-mail. Tell me what
> > am I doing wrong? ISDN keeps flapping. Scenario is
> > as
> > below.
> >
> > Grumpy--(Bri 0) ------ (Bri 0 )-- Sleepy
> >
> > The BRI link is in OSPF area 2. I used OSPF demmand
> > circuit and also used no peer neighbor route.
> > Bandwidth is not specified on serial link so it will
> > be default T1 for frame link.
> >
> > I have also attached "ip ospf data" results on each
> > router. I had it working some time ago but this time
> > it doesn't work.
> >
> > Rather than throwing some hints please justify
> > proper
> > methodology for this configuration. I am sure
> > everybody will get hit by this scenario in some
> > flavor
> > so it is important.
> >
> > Sam
> >
> >
> > --- Daniel Keller <DMKeller@comdisco.com> wrote:
> > > Because the BRI's are in area 0, OSPF updates will
> > > constantly be triggering the ISDN line. How do
> > you
> > > keep this line from always coming up?
> > >
> > > >>> Kevin Baumgartner <kbaumgar@cisco.com>
> > 09/19/00
> > > 09:42PM >>>
> > > Why do say that OSPF demand circuit won't cut it?
> > > The key to using demand circuit is
> > >
> > > 1. Define the bandwidth on the BRI interface to
> > be
> > > less that serial interface
> > > 2. If doing any redistribution on either of the
> > BRI
> > > routers
> > > filter such that IP subnet between the two BRI
> > > router
> > > interfaces doesn't get redistributed. If you
> > let
> > > this route
> > > through the BRI interface will flap because of
> > > routing updates.
> > > 3. Define OSPF demand circuit on only one router
> > > (optional).
> > >
> > > The other two methods to do this is like you said
> > > dialer watch-list
> > > and backup interface.
> > >
> > > Kevin
> > >
> > >
> > > >
> > > > Hey bud, got a good config for the following ?
> > > >
> > > > s0 & bri0 are in the same area 0 of OSPF
> > > >
> > > > what's a good dial backup config for this for
> > when
> > > s0 goes down without bri0
> > > > flapping? demand circuit doesn't seem to cut
> > it,
> > > floating statics are out of
> > > > the question, leaving only dialer watch-list
> > (IOS
> > > 12.3 & higher) or backup
> > > > interface - but what other way is there if any
> > !?
> > > >
> > > >
> > > > Mike L. Chase
> > > > Sr. Network Architect
> > > > ISG: Information Services Group
> > > > Broadcom Corporation World Headquarters, BLDG
> > > A-1050
> > > > 16215 Alton Parkway, Irvine, California
> > > 92618-3616
> > > >
> > >
> >
>OFFICE:949-585-6057|CELL:949-283-4254|FAX:949-585-6227
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com
> > > [mailto:nobody@groupstudy.com]On Behalf Of
> > > > Kevin Baumgartner
> > > > Sent: Tuesday, September 19, 2000 7:10 PM
> > > > To: Steve McNutt
> > > > Cc: ccielab@groupstudy.com
> > > > Subject: Re: Hello, new on list
> > > >
> > > >
> > > > Yes in theory ISDN is simple but I would be
> > able
> > > to do the following
> > > > and have practiced the following on routers.
> > > >
> > > > 1. OSPF on demand circuit
> > > > 2. Dial backup
> > > > 3. Appletalk over ISDN (and how to filter so
> > ISDN
> > > is not up all the time)
> > > > 4. IPX over ISDN (also how to filter so ISDN is
> > > not up all the time)
> > > > 5. Dialer watch
> > > > 6. PPP Multilink
> > > > 7. PPP CHAP/PAP
> > > > 8. PPP Callback
> > > > 9. Snapshot routing
> > > >
> > > > Kevin
> > > >
> > > > >
> > > > > practice ISDN? ISDN is pretty simple to
> > > configure and troubleshoot. DOD
> > > > > routing using rotary groups and dialer
> > profiles
> > > gives me fits though hehe.
> > > > > If you don't build your configs in the correct
> > > order the dialer interfaces
> > > > > never seem to work right.
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: nobody@groupstudy.com
> > > [mailto:nobody@groupstudy.com]On Behalf Of
> > > > > Kevin Baumgartner
> > > > > Sent: Tuesday, September 19, 2000 9:30 PM
> > > > > To: jix@netrue.com
> > > > > Cc: ccielab@groupstudy.com
> > > > > Subject: Re: Hello, new on list
> > > > >
> > > > >
> > > > > If you don't practice ISDN, ATM or FR you
> > have
> > > no chance of passing.
> > > > > They have to be part of your practice lab.
> > > > >
> > > > > Kevin
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> >



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:59 GMT-3