Re: route-map logic -- Solution

From: Przemyslaw Karwasiecki (karwas@xxxxxxxxxxx)
Date: Thu Feb 14 2002 - 00:39:55 GMT-3


   
All,

Thank you very much for your feedback and help.

In my particular case I reverted route map logic
(old, good deMorgan Laws) to something like this:

route-map eBGP-OUT deny 10
 match community NEITHER_US_NOR_CUSTOMERS
route map eBGP-OUT permit 20
 match community PREPEND_1
 set as_prepend 18747
route map eBGP-OUT permit 22
 match community PREPEND_2
 set as_prepend 18747 18747
(...)
route map eBGP-OUT permit 99

ip comunity-list standart NEITHER_US_NOR_CUSTOMERS deny 18747:610
ip comunity-list standart NEITHER_US_NOR_CUSTOMERS deny 18747:620
ip comunity-list standart NEITHER_US_NOR_CUSTOMERS permit

Thanks again,

Przemek

PS. this is actually mentioned on page 356 in Parkhust,
    but I somehow overlooked it.

On Wed, 2002-02-13 at 10:53, Przemyslaw Karwasiecki wrote:
> All,
>
> I am confused with Parkhust Appendix C (route-maps)
>
> Is it possible to build route-map which will do following:
>
> Select only routes matching certain communities, then
> (only for those routes)
> based on another comunity, do some route modifications?
>
>
> In other words, how to reject all routes not matching
> some community, and continue execution of route map
> for only those routes which hasn't been rejected.
>
> Something like:
>
>
> route-map eBGP_PROVIDER_X-OUT permit 10
> description Prefixes from customers
> match community CUSTOMERS_OR_OURS
> continue with route map
>
> route-map eBGP_PROVIDER_X-OUT permit 20
> description Do AS_PREPEND based on community
> match communnity PROVIDER_X_1
> set as-path prepend 65000
>
> route-map eBGP_PROVIDER_X-OUT permit 30
> description Do AS_PREPEND based on community
> match communnity PROVIDER_X_2
> set as-path prepend 65000 65000
>
> ...
>
> Of course there is no "continue with route map" statement in IOS,
> at least I don't know any statement like this.
>
> Any suggestions?
> Am I totally spoiled with JunOS?
>
> Thanks,
>
> Przemek
>
> Sorry for crossposting, but I belive this problem is in scope
> of both lists



This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:22 GMT-3