From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Mon Mar 14 2005 - 20:22:52 GMT-3
Can you post your configuration from R4 and R5?
Also the link should not idle timeout unless you do not have the dialer
idle-timeout set to 0 on the side without the dialer watch
configuration.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: simon hart [mailto:simon.hart@btinternet.com]
Sent: Monday, March 14, 2005 2:44 PM
To: Brian Dennis; Group Study
Subject: RE: Dialer Watch
Hi Brian,
Thanks for pointing this out, however I have tried this command with
little
joy.
It seems that if I have the no peer neighbor-route then R4 will is
never
able to re-establish a virtual link to area 0 (I am assuming you are
familiar with the Lab scenario) as does not know how to get to R3, and
thus
does not have reachability to the rest of the network as a result of the
failure.
If I have a peer neighbor-route then R4 does re-establish the virtual
link
to R3, but als installs a 150.1.3.3 as a directly connected route which
is
now far more favourable than the previously installed route via OSPF.
This
then results in the link flapping
I am pulling my hair out on this one (perhaps it is time to move on)
-----Original Message-----
From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
Sent: 14 March 2005 22:28
To: simon hart; Group Study
Subject: RE: Dialer Watch
Try using the "no peer neighbor-route" command.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
simon hart
Sent: Monday, March 14, 2005 2:14 PM
To: Group Study
Subject: Dialer Watch
Hi Group,
I am going over IE lab 11 (again), and am confused with the Dialer watch
setup.
Within this lab there is a requirement to watch a a number of routes
(150.1.3.3 being one of them) and bring up the ISDN if the routes are
lost.
So far so good, however there is a dialer map statement i.e
dialer map ip 187.1.45.5 name Rack1R5 broadcast xxxxxx
.............(normal
map statement)
dialer map ip 150.1.3.3 name Rack1R5 broadcast
xxxxxx................(additional map statment for dialer watch)
Why is this needed? Does this not cause more problems.
I have found that once the dialer watch is invoked because of the lost
route
the ISDN link starts to flap.
After doing a an ip route debug it appears that the routing table will
install the 150.1.3.3 route as directly connected route because of the
dialer map statement. When the old route comes back on line, it is not
prefered because it is a route known via a routing protocol, however the
link will idle timeout after a set period, but will immediately come up
again because of the loss of the now directly connected route.
Any pointers appreciated
Simon
Simon
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.7.2 - Release Date: 11/03/2005
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:45 GMT-3