From: David Terry (ETL) (David.Terry@etl.ericsson.se)
Date: Sun Jan 12 2003 - 07:39:27 GMT-3
Hello Sage,
I had problems like this in a similar scenario.
From what I've seen you need a dialer map statement for the same network that you are watching with the dialer watch-list. The thing that is key is that the network in your routing table must match exactly the dialer map and dialer watch-list.
I ended up having to take the config out and put it back in for mine to work !!!
HTH
David
-----Original Message-----
From: Sage Vadi [mailto:sagevadi@yahoo.co.uk]
Sent: 12 January 2003 07:30
To: ccielab@groupstudy.com
Subject: ISDN: dialer-watch
Hi all,
interface BRI0
~cut~
dialer map ip 155.100.2.1 name R1 broadcast 99065143
dialer map ip 155.100.5.0 name R1 broadcast 99065143*
dialer watch-group 243
~more~
dialer watch-list 243 ip 155.100.5.0 255.255.255.0
Q) When the 155.100.5.0 route gets taken away from the
route-table the dialer-watch fails to get activated.
Debugs -
DDR: Dialer Watch: watch-group = 243
DDR: network 155.100.5.0/255.255.255.0 DOWN,
DDR: primary DOWN
DDR: Dialer Watch: Dial Reason: Primary of group 243
DOWN
DDR: Dialer Watch: watch-group = 243,
The only reason why I put the config line marked * was
because without that line the dialer-watch fails to
activate.
The ISDN line is fine, I can get this line. It is not
a ISDN issue. It is something wrong with dialer-watch,
either config or a bug.
Q) Does everyone agree that we shouldn't need to put a
dialer map statement for the failed network in the
bri0 interface? I would not normally put it there, but
debugs indicated I had to.
Thoughts appreciated.
Cheers,
Sage
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3