[c-nsp] route-map not matching community

[Stephen J. Wilcox]

permit 30 has no match statement which means it will match everything, so you 
will never get to the permit 40.

move the 30 to the end and it will work 

Steve

On Thu, 7 Jul 2005, matthew zeier wrote:

> 
> I'm sure I'm overlooking something simple.  This route-map isn't matching what 
> I think it should.  What'd I miss?
> 
> route-map customer-routes permit 10
>   match community 80
>   set local-preference 80
>   set community 5693:5001 additive
> !
> route-map customer-routes permit 20
>   match community 120
>   set local-preference 120
>   set community 5693:5001 additive
> !
> route-map customer-routes permit 30
>   set community 5693:5001 additive
> !
> route-map customer-routes permit 40
>   description Null Route Community
>   match community 66
>   set ip next-hop 192.168.1.1
> 
>   neighbor 207.xx.xxx.xx remote-as 65000
>   neighbor 207.xx.xxx.xx send-community
>   neighbor 207.xx.xxx.xx default-originate
>   neighbor 207.xx.xxx.xx prefix-list customer65000 in
>   neighbor 207.xx.xxx.xx prefix-list default-only out
>   neighbor 207.xx.xxx.xx route-map customer-routes in
> 
> ip prefix-list customer65000 seq 5 permit 209.80.8.128/25 le 32
> 
> 
> core1#sh ip bgp community 5693:6666
> BGP table version is 8621863, local router ID is 216.23.160.134
> Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
> Origin codes: i - IGP, e - EGP, ? - incomplete
> 
>     Network          Next Hop            Metric LocPrf Weight Path
> *> 209.80.8.160/32  207.xx.xxx.xx            0             0 65000 i
> 
> --
> matthew zeier, Sr. Network Engineer  | "Nothing in life is to be feared.
> InteleNet Communications, Inc.       |  It is only to be understood."
> (949) 784-7904                       |       - Marie Curie
> _______________________________________________
> 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/
>