From: Nick Shah (nshah@connect.com.au)
Date: Wed Sep 04 2002 - 23:33:11 GMT-3
Dmitry
> Nick what do You mean "global" ?
> I assume it is when nothing followed after "in" ou "out"
> I think when we use 'global' in - that means - filtering incoming routing
> updates via all interfaces. In - it's always about interfaces
>
>
http://127.0.0.1:8080/cc/td/doc/product/software/ios121/121cgcr/ip_r/iprprt2
> /1rdindep.htm#1017647
>
> in - Applies the access list to INCOMING routing updates.
>
> type (Optional) Interface type.
>
> number - (Optional) Interface number on which the access list should be
> applied to incoming updates. If no interface is specified, the access list
> will be applied to all incoming updates.
>
YEs, I mean the same. Global is basically applied to the 'local'
process/routign instance, and hence all teh interfaces.
> With exception of case when You are filtering LSA 7 to 5 conversion on
NSSA
> (see P.v.Oene answer to D.Mateo (09/01 10:38). In this case downstream
> routers will not get
> LSA 5.
Yes, thats true.
> So, again about 'global' (just 'out') -
> I just want to clarify: It's related to sending routes out ALL interfaces
> AND
> from ALL other routing protocols running on router and redistributed into
> this one.
>
yes, Correct.
>
> > I think you can only filter O/IA routes.
>
> Just tested it using "distr-list X in". Filters "O E2" and "O IA" (but the
> stay in DB),
> also filters "O" (the are not even in DB !!), all three types are
> still propagated to downstream routers. Even "O" which is not in DB.
> I even reload router for sure :)
hmm. Thats curly. I guess, I will have to lab thisone up.
rgds
Nick
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:44 GMT-3