From: Niksa Tomulic (ccie@otokrab.net)
Date: Sat Apr 26 2003 - 15:31:35 GMT-3
Some stuff I've leaned via this group and trying out later (thanks,
group :))
1) You don't need dialer list at all while using dialer-watch
Dialer-watch itself defines interesting traffic - so no concern about
filtering routing updates
TRY
2) it also works with IS-IS, perfectly. If because of some reason you
still need to use dialer-list, you don't have to filter it in dialer
list, at all - because it's CLNS, not IP
So, if you have dialer-list 1 permit any any - ISIS won't bring link up.
Why don't you try with RIP on your own, and let us all know? It's even
faster then posting the message to the list, and we could all learn
something
Thanks
niksa
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Mike Williams
Sent: Saturday, April 26, 2003 7:00 PM
To: CCIELab@Groupstudy.com
Subject:
I'm working on a scenario that is telling me to use dialer-watch. When
I checked the "answer", the config had defined interesting traffic as
all IP traffic except OSPF, presumably so Hellos don't keep the link
alive. That makes perfect sense.
So I'm reading in the Dialer-Watch Configuration Guide (see URL below),
and it also uses OSPF for the example and part of the config sample
says:
access-list 101 remark Define Interesting Traffic
access-list 101 deny ospf any any
access-list 101 permit ip any any
!Mark OSPF as uninteresting.
!This will prevent OSPF hellos from keeping the link up.
What if you're using a different routing protocols? I'm assuming that
you would make whatever routing protocol you're using appear
"uninteresting" so that it doesn't keep the link up with keep-alives,
correct?
The document (config guide) says:
"Routing protocol independent-Static routes or dynamic routing
protocols, such as Interior Gateway Routing Protocol (IGRP), Enhanced
IGRP (EIGRP) or Open Shortest Path First (OSPF) can be used."
If this feature is routing protocol independent, should I assume that
means it also works with RIP and BGP (which aren't mentioned anywhere in
the document)? What if you're using a multicast routing protocol?!?!
Here's the link to the config guide that I've been talking about:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fdial_c/fnsprt6/dcdbakdw.htm
TIA,
Mike W.
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:36:07 GMT-3