From: Johnson, Charles (Charles.Johnson@xxxxxxxxxx)
Date: Sun Dec 31 2000 - 16:29:48 GMT-3
Justin,
I've done a little more research and testing. It makes sense to watch the loop
back network of the router at the other end of the link you want to back up. I
n that case you would have route in the watch-list and one dialer map for the w
atch feature. I found examples of that:
http://www.cisco.com/warp/public/793/access_dial/backupwatch.html
or
http://www.groupstudy.com/archives/ccielab/200007/msg00660.html
However, if you can't use a loopback or have a more complex topology (e.g. dial
is a backup to your backup), you might want a list of routes to watch. If you
use this feature that way (in 12.0), your router will dial when it sees the la
st of your listed routes go away. You must have one of the routes from your wa
tch-list in a dialer map. I can't find that it matters which one. It still wo
rks if you have more than one of the routes used in a dialer map, but I don't t
hink the extra dialer map does anything. I only tested 12.0 mainline.
The example on the CD has one dialer map for the router to be dialed and one di
aler map for a network in the watch-list. The watch-list has three entries, th
ough it is not clear where those routes originate.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/dial_c/d
cdbakdw.htm
HTH - somebody correct me if I've missed something.
Charles
-----Original Message-----
From: Justin Menga [mailto:Justin.Menga@computerland.co.nz]
Sent: Sunday, December 31, 2000 7:48 AM
To: Johnson, Charles; ccielab@groupstudy.com
Subject: RE: dialer watch idle time out
What routes are you watching?
Why do you have 156.43.41.0/24 in your watch-list, but no dialer map for
this network?
Regards,
Justin Menga CCIE #6640 MCSE+I CCSE
WAN Specialist
Computerland New Zealand
PO Box 3631, Auckland
DDI: (+64) 9 360 4864 Mobile: (+64) 25 349 599
mailto: justin.menga@computerland.co.nz
-----Original Message-----
From: Johnson, Charles [mailto:Charles.Johnson@turner.com]
Sent: Tuesday, 26 December 2000 10:03 a.m.
To: ccielab@groupstudy.com
Subject: dialer watch idle time out
Anyone used dialer watch much?
I got it to work with OSPF & EIGRP with 2500s running 12.0(9). It looks
like it has an idle timeout of 90 seconds. At the end of the 90 seconds, it
does something. If the primary link comes up during the 90 seconds and
stays up, the dial session will drop at the end of the 90 seconds.
If the primary is down at the 90 second mark, the dial session still drops,
but redials immediately. Is this the common/expected behavior?
Here is debug dialer from the router with dialer watch:
Dec 25 14:14:49.862: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from
827
99 r4, call lasted 89 seconds
Dec 25 14:14:49.866: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
Dec 25 14:14:49.902: BR0:1 DDR: Dialer Watch: resetting call in progress
Dec 25 14:14:49.902: DDR: Dialer Watch: watch-group = 2
Dec 25 14:14:49.902: DDR: network 156.43.41.0/255.255.255.0 DOWN,
Dec 25 14:14:49.906: DDR: network 156.43.201.0/255.255.255.0 UP,
Dec 25 14:14:49.910: DDR: primary DOWN
Dec 25 14:14:49.910: DDR: Dialer Watch: Dial Reason: Secondary of group 2
DOWN
Dec 25 14:14:49.914: DDR: Dialer Watch: watch-group = 2,
Dec 25 14:14:49.914: DDR: dialing secondary by dialer map
156.43.201.0 o
n BR0
Dec 25 14:14:49.918: BR0 DDR: Attempting to dial 82799
Dec 25 14:14:49.922: BR0:1 DDR: disconnecting call
Dec 25 14:14:50.866: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1,
cha
nged state to down
Dec 25 14:14:53.290: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
Dec 25 14:14:53.322: BR0:1 DDR: Dialer Watch: resetting call in progress
Dec 25 14:14:53.330: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to
82799
Dec 25 14:14:53.386: BR0:1 DDR: dialer protocol up
Here is the config from the EIGRP attempt:
Current configuration:
!
! Last configuration change at 15:59:51 UTC Mon Dec 25 2000
! NVRAM config last updated at 14:01:31 UTC Mon Dec 25 2000
!
version 12.0
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname r6
!
!
ip subnet-zero
no ip domain-lookup
isdn switch-type basic-ni
!
!
!
interface Loopback0
ip address 156.43.43.5 255.255.255.0
no ip directed-broadcast
ip ospf interface-retry 0
!
interface Ethernet0
ip address 156.43.200.2 255.255.255.0
no ip directed-broadcast
ip ospf interface-retry 0
no keepalive
!
interface Serial0
ip address 156.43.42.6 255.255.255.0
no ip directed-broadcast
ip ospf interface-retry 0
no ip mroute-cache
no fair-queue
clockrate 250000
!
interface Serial1
no ip address
no ip directed-broadcast
!
interface Serial2
no ip address
no ip directed-broadcast
shutdown
!
interface Serial3
no ip address
no ip directed-broadcast
shutdown
!
interface BRI0
ip address 156.43.128.6 255.255.255.0
no ip directed-broadcast
encapsulation ppp
dialer idle-timeout 300
dialer map ip 156.43.128.4 name r4 broadcast 82799
dialer map ip 156.43.201.0 name r4 82799
dialer watch-group 2
dialer-group 1
isdn switch-type basic-ni
isdn spid1 404827297400 72974
isdn spid2 404827392601 73926
!
router eigrp 46
network 156.43.0.0
!
ip classless
!
access-list 100 deny eigrp any any
access-list 100 deny ip any host 224.0.0.5
access-list 100 permit ip any any
dialer watch-list 2 ip 156.43.41.0 255.255.255.0
dialer watch-list 2 ip 156.43.201.0 255.255.255.0
dialer-list 1 protocol ip list 100
!
line con 0
privilege level 15
transport input none
line aux 0
line vty 0 4
!
end
r6#
thanks,
Charles
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:14 GMT-3