From: Raphael Gallegos (raphaeljg@xxxxxxxxxxx)
Date: Mon Oct 01 2001 - 23:16:26 GMT-3
do your "debug dialer packets" to find out what is causing the dialing, then
you may find that OSPF is sending lsa's becasue of route changes, easiest
way to fix this is to create the dialer-list that prevents ospf from kicking
up the line.
>From: Tim Fletcher <tim@fletchmail.net>
>Reply-To: Tim Fletcher <tim@fletchmail.net>
>To: ccielab@groupstudy.com
>Subject: OSPF demand-circuit w/Dialer profiles
>Date: Mon, 01 Oct 2001 17:32:20 -0400
>
>Hi all,
>
>I can't get OSPF demand-circuit to work right with dialer profiles. With a
>legacy DDR config it works fine. When I try to change it to dialer
>profiles, the link keeps coming back up immediately after it goes down.
>
>Any ideas what I'm doing wrong? Configs are below.
>
>-Tim
>
>Legacy DDR config (works):
>
>interface Serial0/1:23
> ip address 192.168.0.1 255.255.255.0
> encapsulation ppp
> ip ospf demand-circuit
> dialer map ip 192.168.0.2 name R8 broadcast 5512101
> dialer-group 1
> isdn switch-type primary-ni
> ppp authentication chap
> ppp multilink
>!
>router ospf 1
> log-adjacency-changes
> network 192.168.0.0 0.0.0.255 area 0
>!
>dialer-list 1 protocol ip permit
>
>
>Dialer profiles config (keeps circuit up):
>
>interface Serial0/1:23
> no ip address
> encapsulation ppp
> dialer pool-member 1
> isdn switch-type primary-ni
> ppp authentication chap
> ppp multilink
>!
>interface Dialer1
> ip address 192.168.0.1 255.255.255.0
> encapsulation ppp
> ip ospf demand-circuit
> dialer pool 1
> dialer remote-name R8
> dialer string 5512101
> dialer-group 1
> no peer neighbor-route
> ppp multilink
>!
>router ospf 1
> log-adjacency-changes
> network 192.168.0.0 0.0.0.255 area 0
>!
>dialer-list 1 protocol ip permit
>**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:11 GMT-3