From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Sat Oct 29 2005 - 21:07:52 GMT-3
Didn't we just cover this last week? The interface isn't configured for
PPP encapsulation so the command isn't needed ;-) Also the peer
neighbor route and OSPF demand-circuit by themselves will not cause a
problem.
HTH,
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
________________________________
From: Schulz, Dave [mailto:DSchulz@dpsciences.com]
Sent: Saturday, October 29, 2005 4:16 PM
To: Dave Temkin ; nobody@groupstudy.com; Brian Dennis
Cc: Leigh Harrison ; FORUM
Subject: RE: IP Ospf Demand-Circuit
It may be a good practice to add the no peer neighbor command, so the
ISDN addresses avoid changing the OSPF database. This would cause the
ospf demand to not play the game.
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: Brian Dennis
Cc: Leigh Harrison; FORUM
Sent: 10/29/2005 7:02 PM
Subject: RE: IP Ospf Demand-Circuit
True, but it's a good place to start...
-Dave
On Sat, 29 Oct 2005, Brian Dennis wrote:
> The routing table itself doesn't necessarily have to change.
>
> HTH,
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> bdennis@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Direct: 775-745-6404 (Outside the US and Canada)
>
>
> -----Original Message-----
> From: Dave Temkin [mailto:dave@ordinaryworld.com]
> Sent: Saturday, October 29, 2005 1:16 PM
> To: Brian Dennis
> Cc: Leigh Harrison; FORUM
> Subject: RE: IP Ospf Demand-Circuit
>
>
> using debug ip routing here would be helpful - he should be able to
see
> the changes to the table that are causing OSPF to dial..
>
> -Dave
>
> On Sat, 29 Oct 2005, Brian Dennis wrote:
>
> > Leigh,
> > I pasted your configurations into a rack and didn't notice any
> > problems. I was looking to see if the idle timeout was possibly set
> to
> > low but it wasn't.
> >
> > You should try to isolate the OSPF network across the ISDN to
> > see if there are any topology changes that may be keeping the ISDN
> line
> > up. You can do this by just running OSPF between R1 and R2 across
the
> > ISDN.
> >
> > HTH,
> >
> > Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> > bdennis@internetworkexpert.com
> >
> > Internetwork Expert, Inc.
> > http://www.InternetworkExpert.com
> > Toll Free: 877-224-8987
> > Direct: 775-745-6404 (Outside the US and Canada)
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Leigh Harrison
> > Sent: Saturday, October 29, 2005 3:38 AM
> > To: FORUM
> > Subject: IP Ospf Demand-Circuit
> >
> > All,
> >
> > I've got an ospf demand circuit configured up and it doesn't seem to
> be
> > playing the game.
> >
> > I've debug'd ip packet (on R1) and I see the ospf packet (224.0.0.5)
> > being sent to 2.2.2.1 and then it brings the line up, even though
I've
> > got demand circuit configured.
> >
> > Am I missing something obvious ?
> >
> > LH
> >
> > -----------------------
> >
> > I have:-
> > R1 --- frame --- R2
> > | --- ISDN --- |
> >
> > -----------------------
> >
> > R1
> >
> > int bri 0
> > ip add 2.2.2.1 255.255.255.252
> > ip ospf demand-circut
> > dialer idle-timeout 10
> > dialer map ip 2.2.2.2 broadcast 11
> > dialer-group 1
> > isdn switch-type basic-net3
> > no cdp enable
> >
> > dialer-list 1 protocol ip permit
> >
> > int s0
> > ip add 1.1.1.1 255.255.255.0
> > .
> > .
> >
> > router ospf 1
> > network 1.1.1.1 0.0.0.0 ar 0
> > network 2.2.2.1 0.0.0.0 ar 0
> >
> > -----------------------
> >
> > R2
> >
> > int bri 0
> > ip add 2.2.2.2 255.255.255.252
> > ip ospf demand-circut
> > dialer idle-timeout 10
> > dialer map ip 2.2.2.1 broadcast 21
> > dialer-group 1
> > isdn switch-type basic-net3
> > no cdp enable
> >
> > dialer-list 1 protocol ip permit
> >
> > int s0
> > ip add 1.1.1.2 255.255.255.0
> > .
> > .
> >
> > router ospf 1
> > network 1.1.1.2 0.0.0.0 ar 0
> > network 2.2.2.2 0.0.0.0 ar 0
> >
> >
>
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:55 GMT-3