From: Mas Kato (tealp729@xxxxxxxx)
Date: Mon Apr 23 2001 - 01:27:36 GMT-3
I gnash my teeth over stuff like this on CCO all the time. Some of the
stuff, especially articles that are not "TAC Certified," should be taken
with a grain of salt.
Tom, you are absolutely right. Dialer watch aside, in their example, if
the route learned via EIGRP were to go away, the floating static would
kick in and initiate the dial. But this particular example they give is
a mis-mash of dialer watch *and* one of the very situations dialer watch
is supposed to be superior to!! (see the second bullet in the
introduction) Not one of their finer examples.
Dialer watch does not need the floating static, --in fact, because the
route would never really disappears from the routing table, dialer watch
wouldn't really be the reason for the dial--interesting traffic destined
for that network would be.
Without the floating static, when the route disappears from the routing
table, dialer watch will use the dialer map to the watched network you
see under the BRI0 interface.
For what it's worth, the config guide has a better example (watch for
wrap):
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/d
ial_c/dcdbakdw.htm
Regards,
Mas Kato
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Tom Daniel
Sent: Sunday, April 22, 2001 8:02 PM
To: Mas Kato; 'ccielab'
Subject: RE: ISDN backup
I guess I am having a hard time understanding the purpose. The following
example shows that the dialer watch requires a floating static route. If
the
route is learned by eigrp with a lower admin distance. Wouldn't the
floating
route activate the backup regardless of the dialer watch commands.
http://www.cisco.com/warp/customer/793/access_dial/backupwatch.html
-----Original Message-----
From: Mas Kato [mailto:tealp729@home.com]
Sent: Sunday, April 22, 2001 9:43 PM
To: 'Tom Daniel'; 'ccielab'
Subject: RE: ISDN backup
Tom,
The demand circuit does need to come up once to form the neighbor
relationship and negotiate the fact that it is a demand circuit, but if
your demand circuit never quiets down, it's probably due to chronic
underlying link-state changes, for example, flapping because of feedback
from mutual route redistribution. If you make OSPF non-interesting,
depending on when you do it, the neighbor relationship may never form or
the LSDBs will become unsynchronized.
Dialer watch just monitors watched networks in the routing table to
ensure that they are reachable via anything besides the backup interface
it is configured on. If dialer watch triggers the dial, 'show dialer'
will indicate that the dial reason was 'watched route loss,' or
something like that.
Have you tried debugging ip routing to see if routes are constantly
being installed and withdrawn, etc.?
There's also plenty more experience captured in the archives...
Regards,
Mas Kato
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Tom Daniel
Sent: Sunday, April 22, 2001 6:25 PM
To: ccielab
Subject: ISDN backup
Is it possible to use the the ip ospf demand-circuit with the dialer
watch
command. I have tried it but it looks the the 224.0.0.5 brings the
circuit
up. I think I will have to filter this with my dialer-list access list.
any
thoughts?
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:53 GMT-3