Showing results for 
Search instead for 
Did you mean: 

Cisco IOS DDR Dialer Watch-List (VRF) issues

Level 4
Level 4

Hi Guys,

We have a Dial Backup ISDN (DDR) configured on all our WAN Sites, with a Watch-List, in case of our WAN service Failure.

This has been working perfectly until recently when we upgraded our IOS :

From - c3845-advipservicesk9-mz.124-9.T5.bin

To - c3845-advipservicesk9-mz.124-24.t2.bin

Since this upgrade, the Watch-list command no longer works with VRF, so it is continually dialing up, even though the "Watched Route" is in the VRF Routing table.

We have proved this by watching a Route in the "Default" VRF, and it works fine.

So in Short, 124-24.t2 is bugged and does not work for the following command anymore :

dialer watch-list 1 ip vrf DITR-DATA

Is there any extra config we need to enter for this to work on the new IOS?

Please see config & also the current "Wathced Route in the Routing table"

interface BRI0/1/0
description OnRamp2 Line Number XXXOmitted
no ip address
encapsulation ppp
no ip route-cache cef
no ip route-cache
no ip mroute-cache
load-interval 30
dialer pool-member 1
isdn switch-type basic-net3
isdn point-to-point-setup
no keepalive
no fair-queue
no cdp enable
ppp authentication chap

interface Dialer1
ip vrf forwarding DITR-DATA
ip address
encapsulation ppp
dialer pool 1
dialer remote-name AC01WRT01
dialer idle-timeout 600
dialer string XXXOMITTED

dialer load-threshold 2 either
dialer watch-group 1
dialer-group 1
ppp authentication chap
ppp multilink

access-list 101 deny   ospf any any
access-list 101 permit ip any any
dialer watch-list 1 ip vrf DITR-DATA
dialer-list 1 protocol ip list 101

ITRWART1-New#  sh ip route vrf DITR-DATA
Routing entry for
  Known via "ospf 10", distance 110, metric 51, type intra area
  Last update from on Tunnel0, 1w2d ago
  Routing Descriptor Blocks:
  *, from, 1w2d ago, via Tunnel0
      Route metric is 51, traffic share count is 1



1 Reply 1

Ralph Rye
Level 1
Level 1


I am experiencing the same thing, did you ever figure out a work around or a release that doesn't have this bug?


Review Cisco Networking for a $25 gift card