From: Tim Fletcher (tim@fletchmail.net)
Date: Thu Jan 02 2003 - 18:37:58 GMT-3
Stefan,
You're absolutely correct. The problem is that only one side is configured
for dialer watch. Since the other side is not configured for dialer watch
it will time out and disconnect. The dialer watch side will then dialup the
connection again, leading to the bouncing scenario described in the
original post.
-Tim Fletcher
At 09:51 PM 1/2/2003 +0100, stefan vogt wrote:
>Hi all,
>
>I would say that it's not normal with dialer watch that the expiration of
>the dialer idle-timeout timer brings down the circuit (if the primary is
>down). For my understanding with dialer watch every time the dialer
>idle-timeout timer expires it is checked whether the primary link is up.
>
>See at
>http://www.cisco.com/en/US/tech/tk801/tk133/technologies_tech_note09186a008009457d.shtml#dw_operation
>in section Dialer Watch Operation:
>---snip---
>Since the router uses the interesting traffic definition ONLY to check
>whether the primary link is active, consider making all IP traffic
>uninteresting using the command dialer-list number protocol ip deny. With
>this interesting traffic definition, the idle timeout will never be reset,
>and the router will check the status of the primary link at the specified
>interval.
>---snap---
>
>Other behavior I think is a bug.
>In the same document:
>---snip---
>Note: It is recommenced that you use Cisco IOS Software Release12.1(7) or
>higher, which includes fixes for IOS bugs that affect dialer watch.
>---snap---
>
>Best regards,
>Stefan
>
>"Brian T. Albert" <brian.albert@worldnet.att.net> schrieb am 02.01.03
>18:27:19:
> > The dialer idle-timeout will bring down the circuit, this is normal. You
> > have to crank it way up to prevent this from happening and let the
> > re-appearance of the route bring it down.
> >
> > Brian T. Albert
> > CCIE #9682
> > brian.albert@worldnet.att.net
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Evgeny Tantsura
> > Sent: Thursday, January 02, 2003 9:04 AM
> > To: ccielab@groupstudy.com
> > Subject: ISDN Backup With Dialer Watch
> >
> >
> > Hi,
> >
> > My ISDN interface with Dialer Watch on it
> > is going down every idle-timeout and then dialing again.
> >
> > interface Dialer1
> > ip address 1.1.1.2 255.255.255.0
> > encapsulation ppp
> > ip ospf demand-circuit
> > dialer pool 1
> > dialer idle-timeout 180
> > dialer string 0496406937
> > dialer load-threshold 127 either
> > dialer watch-group 1
> > dialer-group 1
> > pulse-time 0
> > no cdp enable
> > ppp authentication chap
> > ppp multilink
> > end
> >
> > access-list 170 deny ospf any any
> > access-list 170 permit ip any any
> > dialer watch-list 1 ip 192.168.5.1 255.255.255.255
> > dialer-list 1 protocol ip list 170
> > ----------------------------------------------------
> >
> > interface Dialer1
> > ip address 1.1.1.1 255.255.255.0
> > encapsulation ppp
> > dialer pool 1
> > dialer idle-timeout 180
> > dialer load-threshold 50 either
> > dialer-group 1
> > no cdp enable
> > ppp authentication chap
> >
> > dialer-list 1 protocol ip permit
> >
> >
> > According to CCO it should stay connected until the router gets the
> > route via primery interface.
> >
> > Any idea's ?
> >
> > With kind regards/ met vriendelijke groeten,
> > ------------------------------------------------
> > E. Tantsura
> > Network Developer
> > Essent Kabelcom N.V.
> > Dr.van Deenweg 84
> > 8025BN Zwolle, The Netherlands
> > Tel: +31-(0)38-850-7642
> > Fax: +31-(0)38-850-7410
> > Mob: +31-(0)6-290-80458
> > ------------------------------------------------
> > .
> > .
>______________________________________________________________________________
>PREMIERE: Der Countdown laeuft! 3 Monate gratis + d-box 1 ab 1 Euro
>nur noch wenige Tage zu haben! http://premiere.web.de/?mc=999927&lp=2
>.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:39 GMT-3