From: Brian Edwards (bedwards@xxxxxxxxxxx)
Date: Thu Jul 13 2000 - 02:24:35 GMT-3
Try this out...
access-list 125 deny ospf any any
access-list 125 permit ip any any
dialer-list 1 protocol ip list 125
> -----Original Message-----
> From: Vijay Venkatesh [mailto:vijay.venkatesh@usa.net]
> Sent: Wednesday, July 12, 2000 10:19 PM
> To: Brian Edwards
> Subject: Re: Painful OSPF demand circuit
>
>
> Hi Brian,
> Thank you for the quick response. Waht would the dialer list 1
> statement look like. ALso would you happen to have a working config
> that
> I can take quick look at ? Thank you.
>
> Regards,
> Vijay.
>
> Brian Edwards wrote:
> >
> > OSPF LSA's will be exchanged over the primary link. The
> ISDN link will be
> > included in the LSA's b/c of the "demand-circuit". When the
> primary link
> > fails LSA's will flow across the ISDN (brought up by
> "backup interface" or a
> > floating static).
> >
> > > -----Original Message-----
> > > From: Vijay Venkatesh [mailto:vijay.venkatesh@usa.net]
> > > Sent: Wednesday, July 12, 2000 9:54 PM
> > > To: Brian Edwards; ccielab@groupstudy.com
> > > Subject: Re: Painful OSPF demand circuit
> > >
> > >
> > > If I make ospf uninteresting and if I add new networks
> behind these
> > > routers ospf LSAs will not be communicated and
> essentially ospf will
> > > not
> > > bring up the bri0. I need ospf to talk to the isdn line
> without user
> > > intervention. Both routers have distinct router ids
> > >
> > > Vijay
> > >
> > > Brian Edwards wrote:
> > > >
> > > > Make OSPF uninteresting.
> > > >
> > > > > running both routers with the same ospf router id
> > > > The routers need to have distinct router ID's
> > > >
> > > > > -----Original Message-----
> > > > > From: Vijay Venkatesh [mailto:vijay.venkatesh@usa.net]
> > > > > Sent: Wednesday, July 12, 2000 9:09 PM
> > > > > To: Earl Aboytes
> > > > > Cc: Stephens, Paul [Prof.Serv]; ccielab@groupstudy.com
> > > > > Subject: Painful OSPF demand circuit
> > > > >
> > > > >
> > > > > Hello,
> > > > > I am beating my head against a brick wall trying to get
> > > > > the ospf
> > > > > demand circuit working. I am posting this in the hope
> someone will
> > > > > look
> > > > > at it from a different perspective. This is my situation -
> > > > >
> > > > > R1 is connected to R2 via a BRI interface. The Bris are on one
> > > > > subnet and are configured with spids for both channels
> > > and do not have
> > > > > dialer profiles. However, they have dialer map
> > > statements. This is a
> > > > > point to point bri. Nothing hangs of R1 and nothing hangs
> > > off R2. I am
> > > > > running both routers with the same ospf router id and
> > > both are in area
> > > > > 0. Now, when I bring up the bri and configure 'ip ospf
> > > demand-circuit'
> > > > > on side (either R1 or R2) the bri line comes and
> > > exchanges ospf info
> > > > > across the isdn line. Then it hangs up after the
> idle-timer of 60
> > > > > seconds. Either R1 or R2 keep redialing and keep the BRI
> > > up. Please
> > > > > not there are no topological changes that are causing
> > > this to happen.
> > > > > When I do a 'sh dialer' it keeps saying that one of
> the routers
> > > > > initiated the dial because it had to communicate to
> > > 224.0.0.5 which
> > > > > is the ospf multicast address. What do I do to make
> sure that the
> > > > > line stays down using nothing but the 'ip ospf demand-circuit'
> > > > > statement. My dialer list is protocol ip permit. The
> dialer maps
> > > > > are configured with the broadcast option. The version
> of code I am
> > > > > running is 11.2(19a) on both routers. Any suggestions
> are invited.
> > > > > Thank you for your insights and time.
> > > > >
> > > > > Regards,
> > > > > Vijay.
> > > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:53 GMT-3