[rbak-nsp] route-map matching prefixes AND communities?

[Sebastian Podjasek]

On 20.07.2012 10:18, Voigt, Thomas wrote:
> Hi all,
>
> actual we are doing outbound route filtering to our upstream peers with an route-map like this:
>
> Now I'd like to make the number of prepended ASNs controlled by BGP communities.
> For example like this:
>
> community = 10 -> no announcement to this upstream
> community = 11 -> prepend <ASN>
> community = 12 -> prepend <ASN> <ASN>
> community = 13 -> prepend <ASN> <ASN> <ASN>
>
> and so on.
>
> In Cisco IOS there is an "continue" keyword to let the route map continue in an defined seq number after an successful match. So we can test first the prefixes and then (after the "continue" seq number) the communities.
> Can we configure similar in SEOS?
>
> How do you deal with BGP communities?
>

You probably mean something like this:

  route-map ebgp-ipv4-export-upstream1 deny 11000
   match ext-community-list <ASN>:1000
  route-map ebgp-ipv4-export-upstream1 permit 11001
   match ext-community-list <ASN>:1001
   set as-path prepend <ASN:ASN>
   continue
  route-map ebgp-ipv4-export-upstream1 permit 11002
   match ext-community-list <ASN>:1002
   set as-path prepend <ASN:ASN> <ASN:ASN>
   continue
  route-map ebgp-ipv4-export-upstream1 permit 11003
   match ext-community-list <ASN>:1003
   set as-path prepend <ASN:ASN> <ASN:ASN> <ASN:ASN>
   continue
  route-map ebgp-ipv4-export-upstream1 permit 11004
   match ext-community-list <ASN>:1004
   set as-path prepend <ASN:ASN> <ASN:ASN> <ASN:ASN> <ASN:ASN>
   continue



-- 
Sebastian Podjasek