From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Jul 09 2004 - 16:51:44 GMT-3
Dehong,
This is specific to dialer watch. The following document
outlines the configuration steps and outlines troubleshooting:
http://www.cisco.com/warp/public/129/bri-backup-map-watch.html
<cco>
Troubleshooting Dialer Watch
...
Problem: The router does not dial the backup link when the primary link
goes down.
...
Possible Solution #2: Verify there are two dialer map statements on the
backup interface.
There should be one map statement for the route/network specified by the
dialer watch-list command
There should be one map statement for the IP address of the remote
router's interface.
</cco>
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
> -----Original Message-----
> From: Wang Dehong-DWANG1 [mailto:Dehong.Wang@motorola.com]
> Sent: Friday, July 09, 2004 2:46 PM
> To: Brian McGahan; ccielab@groupstudy.com
> Subject: RE: dialer watch failed..
>
>
> thank you all for getting me back on this. Honestly speaking, I did
not
> see any document which states adding dialer map for watched route.. I
> spent more than two hours to figure out why it did not dial.
>
> Does this applied to any other scenarios as well or just to dialer
watch?
>
> thanks again.
>
> - Dehong
>
> -----Original Message-----
> From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
> Sent: Friday, July 09, 2004 2:34 PM
> To: Wang Dehong-DWANG1; ccielab@groupstudy.com
> Subject: RE: dialer watch failed..
>
>
> Wang,
>
> You also need to add a dialer map for the 172.16.124.0 network
> (the watched route) on the router that is doing the dialer watch. For
> dialer profile configurations this is not required.
>
> HTH,
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987 x 705
> Outside US: 775-826-4344 x 705
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Wang Dehong-DWANG1
> > Sent: Friday, July 09, 2004 12:12 PM
> > To: ccielab@groupstudy.com
> > Subject: dialer watch failed..
> >
> > Question for the ISDN experts.. I worked on a lab scenario to use
> dialer
> > watch, but for some reasons the dialer watch did not get the
> connections
> > up. I know the rule of dialer watch is to make sure watched route is
> in
> > the routing table.. Dailer watch did take some actions, but failed
> with
> > dialer map/string not present, but I do have dialer map string in
the
> bri.
> >
> > Any comments? thanks.
> >
> > - Dehong
> >
> > R2#sg
> > *Mar 1 01:56:25: DDR: Dialer Watch: watch-group = 1
> > *Mar 1 01:56:25: DDR: network 172.16.124.0/255.255.255.0 DOWN,
> > *Mar 1 01:56:25: DDR: primary DOWN
> > *Mar 1 01:56:25: DDR: Dialer Watch: Dial Reason: Primary of group 1
> DOWN
> > *Mar 1 01:56:25: DDR: Dialer Watch watch-group 1 -
> > dialer map/string not present on BR1
> > R2#
> > R2#
> >
> >
> >
> > R2
> > ======
> > username R1 password 0 cisco
> >
> > interface BRI1/0
> > ip address 172.16.12.2 255.255.255.0
> > encapsulation ppp
> > dialer map ip 172.16.12.1 name R1 broadcast 8358661
> > dialer map ip 172.16.12.1 name R1 broadcast 8358663
> > dialer watch-group 1
> > dialer-group 1
> > isdn switch-type basic-ni
> > isdn spid1 0835866201
> > isdn spid2 0835866401
> > no peer neighbor-route
> > ppp authentication chap
> >
> > access-list 107 deny eigrp any any
> > access-list 107 permit ip any any
> > dialer watch-list 1 ip 172.16.124.0 255.255.255.0
> > dialer-list 1 protocol ip list 107
> >
> > R1
> > ======
> >
> > username R2 password 0 cisco
> >
> > interface BRI0/0
> > ip address 172.16.12.1 255.255.255.0
> > encapsulation ppp
> > dialer map ip 172.16.12.2 name R2 broadcast 8358662
> > isdn switch-type basic-ni
> > isdn spid1 0835866101
> > isdn spid2 0835866301
> > no peer neighbor-route
> > ppp authentication chap
> > end
> >
> >
>
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:51 GMT-3