From: Ouellette, Tim (tim.ouellette@eds.com)
Date: Mon Jan 13 2003 - 22:40:52 GMT-3
You should note that this is for LEGACY DDR. Dialer profiles don't need the
maps. Heck I don't even think the "dialer map ip" works on Dialer profiles
due to their Point-to-point nature.
TIm
-----Original Message-----
From: Stong, Ian C [GMG] [mailto:Ian.C.Stong@mail.sprint.com]
Sent: Monday, January 13, 2003 10:03 AM
To: Sage Vadi; ccielab@groupstudy.com
Subject: RE: ISDN: dialer-watch
With dialer watch you do need to put in dialer map statements for each of
the routes you are watching.
Hope that helps.
Ian
www.ccie4u.com Rack Rentals and Lab Scenarios
-----Original Message-----
From: Sage Vadi [mailto:sagevadi@yahoo.co.uk]
Sent: Sunday, January 12, 2003 2:30 AM
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:48 GMT-3