From: Hunt Lee (huntl@webcentral.com.au)
Date: Thu Feb 13 2003 - 04:31:11 GMT-3
Donny,
Option 1 - exactly my thinking, but then I found that ISIS doesn't have
"distribute-list" command, or at least on the IOS I'm using anyway... anyone
can confirm this?
Option 2 - if there is no "distribute-list" command available on ISIS, how
do I filter R1's advertisement at R2??
Regards,
Hunt
-----Original Message-----
From: Donny MATEO [mailto:donny.mateo@sg.ca-indosuez.com]
Sent: Wednesday, 12 February 2003 8:12 PM
To: Hunt Lee
Cc: 'ccielab@groupstudy.com'; nobody@groupstudy.com
Subject: Re: ISIS help!!!
why not try to use distribute-list to filter the unwanted route feedback ?
u can use it on 2 places, 1 is on R1 distribute-list out to R2 or another
alternative is on R2 filtering advertisement received from R1 (deny host
172.18.3.3)
Donny
Hunt Lee
<huntl@webcentral To:
"'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
.com.au> cc:
Sent by: Subject: ISIS help!!!
nobody@groupstudy
.com
12-02-2003 15:36
Please respond to
Hunt Lee
Hello group,
Since IS-IS doesn't have "distribute-list" command, is there any other
commands /
ways that I could use to block / filter routes from coming into an ISIS
router?
The lab scenario that stir up my thinking was:-
R1 --------- R2 ---------- R3 -------- 172.18.3.3/32 (lo0)
ISIS RIPv1
I need to get this Loopback route to R1.
To do this, I redistribute the RIP route into ISIS at R2. Now an issue
arises,
since ISIS has a lower admin dist than RIP, R2 now has a routing loop for
172.18.3.3/32. This minute it gets the route from R3 (thru RIP), & the next
minute
it gets the same route from R1 (thru ISIS).
Feb 11 22:50:49.547 UTC: RT: add 172.18.0.0/16 via 172.17.23.2, rip metric
[120/1]
Feb 11 22:50:57.563 UTC: RT: closer admin distance for 172.18.0.0, flushing
1 routes
Feb 11 22:50:57.563 UTC: RT: add 172.18.0.0/16 via 172.16.12.1, isis metric
[115/73]
Feb 11 22:51:07.563 UTC: RT: delete route to 172.18.0.0 via 172.16.12.1,
isis metric
[115/73]
Feb 11 22:51:07.563 UTC: RT: no routes to 172.18.0.0
Feb 11 22:51:07.563 UTC: RT: delete network route to 172.18.0.0
Feb 11 22:51:16.603 UTC: RT: add 172.18.0.0/16 via 172.17.23.2, rip metric
[120/1]
Feb 11 22:51:24.615 UTC: RT: closer admin distance for 172.18.0.0, flushing
1 routes
Feb 11 22:51:24.615 UTC: RT: add 172.18.0.0/16 via 172.16.12.1, isis metric
[115/73]
Feb 11 22:51:34.615 UTC: RT: delete route to 172.18.0.0 via 172.16.12.1,
isis metric
[115/73]
Feb 11 22:51:34.615 UTC: RT: no routes to 172.18.0.0
Feb 11 22:51:34.615 UTC: RT: delete network route to 172.18.0.0
The only way I found so far is to lower the admin dist for that particular
route
coming from R3.
router rip
network 172.17.0.0
network 172.19.0.0
distance 110 172.17.23.2 0.0.0.0 block
ip access-list standard block
permit 172.18.0.0 0.0.255.255
deny any
Is there any other way I could do this? An alternative is to higher the
admin dist
of ISIS routes from R1... but I found that ISIS doesn't allow me to change
Admin
Dist per prefix, which makes this option very un-attractive.
Hunt
.
-- WebCentral Pty Ltd Australia's #1 Internet Web Hosting Company Level 1, 96 Lytton Road. Network Operations - Systems Engineer PO Box 4169, East Brisbane. email: huntl@webcentral.com.au Queensland, Australia. phone: +61 7 3249 2553 . This message is for information purposes only and its content should not be construed as an offer, or solicitation of an offer, to buy or sell any banking or financial instruments or services and no representation or warranty is given in respect of its accuracy, completeness or fairness. The material is subject to change without notice. You should take your own independent tax, legal and other professional advice in respect of the content of this message. This message may contain confidential or legally privileged material and may not be copied, redistributed or published (in whole or in part) without our prior written consent. This email may have been intercepted, partially destroyed, arrive late, incomplete or contain viruses and no liability is accepted by any member of the Credit Agricole Indosuez group as a result. If you are not the intended recipient of this message, please immediately notify the sender and delete this message from your computer. .
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:21 GMT-3