From: Joe (groupstudy@comcast.net)
Date: Tue Jan 07 2003 - 23:03:06 GMT-3
You gotta make the idle-timeout some rediculously high value that's all.
I don't have the exact link, but it is documented this way on CCO in at
least one link.
Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Boehmler, John
Sent: Thursday, January 02, 2003 12:31 PM
To: ccielab@groupstudy.com
Subject: Re: ISDN Backup With Dialer Watch
From my experiments, the dialer watch will hang up at the dialer idle
timeout and nothing seems to change this. An interesting scenario I've
tried is to use dialer watch but ensure that my routing protocol is
denied
as interesting traffic with all else permitted. In this case, when the
primary interface goes down, dialer watch brings up the BRI interface.
The
routing protocol (OSPF in my case) then established an neighbor
adjacency
across the BRI. If I recall correctly, when the BRI hung up, OSPF
appeared
to start to spoof and the routing table still showed the BRI as the next
hop. Note also that in this scenario the hellos did not bring up the
interface (not interesting traffic) but the adjacency remained
intact. However, if you then ping or telnet, the BRI would dial (is
interesting traffic) and all would work fine.
John
At 05:54 PM 1/2/2003 +0100, Evgeny Tantsura wrote:
>Tim,
>
>I've on both routers idle-timeout of 180 sec
>By removing it I'll get the default value = 120 sec
>Is that what you mean ?
>
>I've tried...The only difference is that the call is disconnected every
>120 sec.
>
> > This is usually caused by the idle-timeout on the far end (the end
> > without the dialer-watch). Try removing it and see what happens.
> >
> > -Tim Fletcher
> >
> > At 04:03 PM 1/2/2003 +0100, Evgeny Tantsura wrote:
> > >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
> > >------------------------------------------------
> > >.
>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
>------------------------------------------------
>.
John Boehmler
Cisco Systems
System Engineer - Delaware Valley Named
301 Lindenwood Dr., Suite 210
Malvern, PA 19355
Cell: 610.348.8774
Phone: 610.695.2943
Fax: 610.768.0708
mailto: jboehmler@cisco.com
http: www.cisco.com
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:45 GMT-3