[c-nsp] Route-maps & multiple match conditions

[Kevin Graham]

Within a given route-map sequence, match conditions are always logical
and's. If you want to match on multiple conditions, do that with what
you're matching...

Create a community-list FOO that permits both X and Y, then in your
route-map, match community FOO. Otherwise you'll have to use multiple
route-map sequences.


On Tue, 17 Aug 2004 20:45:14 -0400, Terry Baranski <tbaranski at mail.com> wrote:
> Ran into an issue on a 6509 today that has me confused.  I was trying to
> adjust the MEDs of outbound routes to a BGP peer based on communities,
> like so: if a route has community A and community B, do this; if it has
> communities X and Y, do this; etc.
> 
> But I ran into trouble getting the 'logical AND' to work.  My
> understanding (based on the route-map section of
> http://www.ciscopress.com/articles/article.asp?p=174107&seqNum=5) is
> that multiple match conditions in a single match statement are treated
> as a logical OR, while multiple match statements (in a single route-map
> statement) are treated as a logical AND.  However, when I entered
> separate match statements for each community, they were converted in the
> running config to a single statement, and the behavior seemed to be that
> of a logical OR.  So:
> 
>         match community X
>         match community Y
> 
> Turned into:
> 
>         match community X Y
> 
> Anyone know if this is correct behavior, and/or if there's another way
> to accomplish the above? (I don't have the IOS version handy.)
> 
> Thanks,
> Terry
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>