From: Carlos G Mendioroz (tron@xxxxxxxxxxx)
Date: Wed Jul 03 2002 - 18:57:55 GMT-3
Jerry,
I don't follow your argument line. Sorry.
Yes, it is a backup circuit, may be for a remote branch via isdn.
In the central site, why wouldn't you use profiles for "profiling"
the interface config to the caller ? The same PRI could be used
for telecommuting and for backup...
Why can't you use ospf demand in that case ? What does this case have
that it makes it non real world ?
(Or else, where in a real world situation would you use ospf demand
circuits :-)
Jerry Haverkos wrote:
>
> I've heard the CCIE lab doesn't necessarily present real world situations.
> Why would you want a demand circuit defined with a dialer interface? It is
> basically a dedicated backup circuit isn't it?
>
> On the "Corporate/Host" side, I don't believe you'd want to define a dialer
> profile either. Comments?
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Carlos G Mendioroz
> Sent: Tuesday, July 02, 2002 8:39 PM
> To: xje
> Cc: lrlab; ccielab@groupstudy.com
> Subject: Re: OSPF Demand Circuit/PPP Multilink/Dialer Profile
>
> AFAIK, this configuration does not work.
> I would love to be wrong... anyone interested in labbing it out and post
> working configs ?
> Please ? :-)
>
> -Carlos
> P.S.
> -It is considered cheating to filter out OSPF from the ISDN link.
> -I've been told of a "workarround" solution that I'm sure the owner
> of the idea will share if no-one comes with a real working config...
>
> xje wrote:
> >
> > ----- Original Message -----
> > From: "lrlab" <lrlab@swbell.net>
> > To: <ccielab@groupstudy.com>
> > Sent: Tuesday, July 02, 2002 2:38 AM
> > Subject: OSPF Demand Circuit/PPP Multilink/Dialer Profile
> >
> > I think you must use bandwidth command below the interface dialer1
> >
> > > Group:
> > >
> > > Any idea why a OSPF deman circuit would work fine until I added ppp
> multi
> > and
> > > dialer load 1 at the dialer on both ends. Once I do that the link
> flaps.
> > > Removed the lines from both and it returns to a normal (working) state.
> > When
> > > I do the debug IP OSPF mon I see the lsa. I have added the no peer nei
> at
> > > both ends. here are the affested part of the configs from both without
> the
> > ppp
> > > multi and dialer load 1.
> > >
> > >
> > > r3#sh run
> > > hostname r3
> > >
> > > username r6 password 0 cisco
> > >
> > > interface BRI0
> > > no ip address
> > > encapsulation ppp
> > > dialer pool-member 1
> > > isdn switch-type basic-ni
> > > isdn spid1 0555100001
> > > isdn spid2 0555300001
> > > ppp authentication chap
> > > !
> > > interface Dialer1
> > > ip address 15.15.15.2 255.255.255.0
> > > encapsulation ppp
> > > ip ospf authentication message-digest
> > > ip ospf message-digest-key 1 md5 cisco
> > > dialer pool 1
> > > dialer remote-name r6
> > > dialer idle-timeout 45
> > > dialer string 5552000
> > > dialer-group 1
> > > no peer neighbor-route
> > > ppp authentication chap
> > > !
> > > router ospf 10
> > > router-id 3.3.3.3
> > > log-adjacency-changes
> > > area 1 stub no-summary
> > > network 15.15.15.2 0.0.0.0 area 1
> > > network 150.100.4.3 0.0.0.0 area 1
> > >
> > > !
> > > access-list 100 permit ip any any
> > > dialer-list 1 protocol ip list 100
> > >
> > >
> > >
> > > r6#sh run
> > > hostname r6
> > >
> > > username r3 password 0 cisco
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI0
> > > no ip address
> > > encapsulation ppp
> > > dialer pool-member 1
> > > isdn switch-type basic-ni
> > > isdn spid1 0555200001
> > > isdn spid2 0555400001
> > > ppp authentication chap
> > > !
> > > interface Dialer1
> > > ip address 15.15.15.1 255.255.255.0
> > > encapsulation ppp
> > > ip ospf authentication message-digest
> > > ip ospf message-digest-key 1 md5 cisco
> > > ip ospf demand-circuit
> > > dialer pool 1
> > > dialer remote-name r3
> > > dialer idle-timeout 45
> > > dialer string 5551000
> > > dialer-group 1
> > > no peer neighbor-route
> > > ppp authentication chap
> > > !
> > > router ospf 10
> > > router-id 6.6.6.6
> > > log-adjacency-changes
> > > area 0 authentication message-digest
> > > area 1 stub no-summary
> > > passive-interface Serial0
> > > network 15.15.15.1 0.0.0.0 area 1
> > > network 150.100.2.1 0.0.0.0 area 0
> > > network 150.100.4.1 0.0.0.0 area 1
> > > network 150.100.50.41 0.0.0.0 area 2
> > > !
> > > ip classless
> > > ip http server
> > > !
> > > access-list 100 permit ip any any
> > > dialer-list 1 protocol ip list 100
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:18 GMT-3