From: tom cheung (tkc9789@xxxxxxxxxxx)
Date: Sun Apr 07 2002 - 20:50:44 GMT-3
I saw two things wrong with the config:
1. In addition to the dialer map for the watched route, you need another
dial map for your peer router. This is the dialer map you would normally
configure.
2. dialer watch list uses mask not wildcard. And you may want to consider
changing ACL 1 to deny routing protocol and permit everything else.
Regards,
Tom
>From: Richard Furda <riso@furda.net>
>Reply-To: Richard Furda <riso@furda.net>
>To: ccielab@groupstudy.com
>Subject: dialer watch
>Date: Sun, 7 Apr 2002 14:34:02 +0000 (GMT)
>
>Hello,
>
>I've been reviewing and playing with every possible ISDN/DDR know there
>is. Dialer watch seems to stumble me a bit. If I have a configuration
>such:
>
>interface BRI0
> ip address 10.10.10.5 255.255.255.0
> encapsulation ppp
> dialer watch-disable 15
> dialer map ip 10.20.30.0 name R3 broadcast 44642773
> dialer watch-group 2
> dialer-group 1
> isdn switch-type basic-net3
> isdn answer1 44642771
> no cdp enable
> ppp authentication chap
>!
>access-list 1 permit 10.10.10.0 0.0.0.255
>dialer-list 1 protocol ip list 1
>dialer watch-list 2 ip 10.20.30.0 0.0.0.255
>! interface Ethernet0
> ip address 10.20.30.1 255.255.255.0
> no keepalive
>!
>
>
>Shutting down e0 should make dialer watch initiate a call? it doesn't.
>If I create a eigrp routing process and make 10.20.30/24 part of that
>network, dialer watch kicks in. Searching the mailing list archives
>and the cisco web, I've not found any specific reference of dialer watch
>working with dynamic routes ONLY. Please correct me if I am wrong.
>
>Thanks,
>Rich
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:59 GMT-3