From: Chad Hintz (ccie_2b2004@yahoo.com)
Date: Fri Jun 03 2005 - 12:05:05 GMT-3
With dialer watch a dialer idle timeout of zero is not really needed on the remote side, since it will not be the one "watching" and will not bring up the call. For the ease of configuration for dialer watch I always put the least amount if configuration on the remote side( ie ppp multilink(if needed), dialer load-threshold, encap ppp, ppp authe pap or chap, and the username and password) The only reason for a dialer group on the remote side and the dialer idle-timeout to be set to zero would be if you were doing ppp callback w/dialer watch, then it would make sure that the remote end would not disconnect the call based on the idle-timeout.
HTH,
Chad
gladston@br.ibm.com wrote:
Hi,
Cisco Doc UniverCD and Solie's book brings examples using Dialer Watch with dialer-group.
But the same Cisco Doc says:
"Once the secondary link is up, at the expiration of each idle timeout,
the primary link is rechecked"
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_2/dwatch.htm#xtocid1516510
Tests shows it is not necessary to use dialer-group.
Is there another reason to use diaeler-group in this case?
I am using dialer idle-timeout 0 on the remote router.
idle-timeout on local router is reset while the primary link is down by Dialer Watch.
r5#sh run int di 25
Building configuration...
Current configuration : 310 bytes
!
interface Dialer25
ip address 172.16.25.5 255.255.255.0
encapsulation ppp
dialer pool 25
dialer remote-name r2
dialer idle-timeout 60
dialer string 8358663
dialer string 8358661
dialer load-threshold 1 outbound
dialer watch-group 5
ppp callback request
ppp authentication chap
ppp multilink
end
r5(config)#int di 25
r5(config-if)#no dialer-group 1
r5(config-if)#
r7(config-if)#int e 0/1
r7(config-if)#sh
*Mar 1 02:41:31.871: destroy peer: 172.16.57.7
*Mar 1 02:41:31.879: DDR: Dialer Watch: watch-group = 5
*Mar 1 02:41:31.879: DDR: network 172.16.77.0/255.255.255.0 DOWN,
*Mar 1 02:41:31.879: DDR: network 172.16.2.1/255.255.255.255 DOWN,
*Mar 1 02:41:31.879: DDR: primary DOWN
*Mar 1 02:41:31.883: DDR: Dialer Watch: Dial Reason: Primary of group 5 DOWN
*Mar 1 02:41:31.883: DDR: Dialer Watch: watch-group = 5,
*Mar 1 02:41:31.883: BR0/0 DDR: rotor dialout [best] least recent failure is also most
recent failure
*Mar 1 02:41:31.883: BR0/0 DDR: rotor dialout [best] trying untried dialout
*Mar 1 02:41:31.883: BR0/0 DDR: rotor dialout [best] also has most recent failure
*Mar 1 02:41:31.883: BR0/0 DDR: rotor dialout [best]
*Mar 1 02:41:31.883: DDR: dialing secondary by dialer string 8358663 on Di25
*Mar 1 02:41:31.883: BR0/0 DDR: Attem
r5#pting to dial 8358663
*Mar 1 02:41:31.887: DDR: Dialer Watch: watch-group = 5
*Mar 1 02:41:31.887: DDR: network 172.16.77.0/255.255.255.0 DOWN,
*Mar 1 02:41:31.887: DDR: network 172.16.2.1/255.255.255.255 DOWN,
*Mar 1 02:41:31.887: DDR: primary DOWN
*Mar 1 02:41:31.887: DDR: Dialer Watch: Dial Reason: Primary of group 5 DOWN
*Mar 1 02:41:31.891: DDR: Dialer Watch: watch-group = 5,
*Mar 1 02:41:31.891: DDR: Dialer Watch: watch-group = 5
*Mar 1 02:41:31.891: DDR: network 172.16.77.0/255.255.255.0 DOWN,
*Mar 1 02:41:31.891: DDR: network 172.16.2.1/255.255.255.255 DOWN,
*Mar 1 02:41:31.891: DDR: primary DOWN
*Mar 1 02:41:31.891: DDR: Dialer Watch: Dial Reason: Primary of group 5 DOWN
*Mar 1 02:41:31.891: DDR: Dialer Watch: watch-group = 5,
*Mar 1 02:41:31.895: DDR: Dialer Watch: watch-group = 5
*Mar 1 02:41:31.895: DDR: network 172.16.77.0/255.255.255.0 DOWN,
*Mar 1 02:41:31.895: DDR: network 172.16.2.1/255.255.255.255 DOWN,
*Mar 1 02:41:31.895: DDR: primary DOWN
*Mar 1 02:41:31.895: DDR: Dialer Watch: Dial Reason: Primary of group 5 DOWN
*Mar 1 02:41:31.895: DDR: Dialer Watch: watch-group = 5,
*Mar 1 02:41:32.228: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up
*Mar 1 02:41:32.232: BR0/0:1 DDR: Dialer Watch: resetting call in progress
*Mar 1 02:41:32.232: BR0/0:1: interface must be fifo queue, force fifo
*Mar 1 02:41:32.236: %DIALER-6-BIND: Interface BR0/0:1 bound to profile Di25
*Mar 1 02:41:32.304: BR0/0:1 DDR: Remote name for r2
*Mar 1 02:41:32.308: BR0/0:1 DDR: Callback negotiated - Disconnecting
*Mar 1 02:41:32.308: DDR: Callback client for r2 8358663 created
*Mar 1 02:41:33.309: BR0/0:1 DDR: disconnecting call
*Mar 1 02:41:33.309: BR0/0:1 DDR: Dialer Watch: resetting call in progress
*Mar 1 02:41:33.309: DDR: Dialer Watch: watch-group = 5
*Mar 1 02:41:33.309: DDR: network 172.16.77.0/255.255.255.0 DOWN,
*Mar 1 02:41:33.309: DDR: network 172.16.2.1/255.255.255.255 DOWN,
*Mar 1 02:41:33.309: DDR: primary DOWN
*Mar 1 02:41:33.309: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed
state to up
*Mar 1 02:41:33.313: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 8358663 r
2
*Mar 1 02:41:33.317: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from 8358663
r2, call lasted 1 seconds
*Mar 1 02:41:33.410: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down
*Mar 1 02:41:33.414: BR0/0 DDR: has total 0 call(s), dial_out 0, dial_in 0
*Mar 1 02:41:33.414: %DIALER-6-UNBIND: Interface BR0/0:1 unbound from profile Di25
*Mar 1 02:41:33.422: BR0/0:1 DDR: disconnecting call
*Mar 1 02:41:34.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed
state to down
r5#sh is ac
--------------------------------------------------------------------------------
ISDN ACTIVE CALLS
--------------------------------------------------------------------------------
Call Calling Called Remote Seconds Seconds Seconds Charges
Type Number Number Name Used Left Idle Units/Currency
--------------------------------------------------------------------------------
In 8358663 8358662 r2 22 Unavail -
--------------------------------------------------------------------------------
r5#
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:40 GMT-3