[alcatel-nsp] RES: Filtering BGP routes using Extended communities

[Kevin Billings]

All

Thanks for the input.  Using the & did the trick and I can now filter entended communities using reg-ex...

Thanks....

From: JOHNSON, ALASTAIR (ALASTAIR) [mailto:alastair.johnson at alcatel-lucent.com]
Sent: Thursday, October 23, 2014 4:44 PM
To: Pena, Hugo Roger Bernaola (Hugo Roger Bernaola); Kevin Billings; alcatel-nsp at puck.nether.net
Subject: RE: [alcatel-nsp] RES: Filtering BGP routes using Extended communities

Indeed, regexp for extended communities use the ampersand (&) character to separate the global administrator and local administrator fields.

e.g.

community "CUST-EXPORT" members target:ASN&." # matches the ASN and locally administered field

This is noted on pg 853, table 19 of the SR OS Routing Protocols Guide 12.0.R4<https://infoproducts.alcatel-lucent.com/aces/cgi-bin/dbaccessfilename.cgi/9300741102_V1_7750%20SR%20OS%20Routing%20Protocols%20Guide%2012.0.R4.pdf> which documents the routing policy implementation.

AJ

From: alcatel-nsp [mailto:alcatel-nsp-bounces at puck.nether.net] On Behalf Of Pena, Hugo Roger Bernaola (Hugo Roger Bernaola)
Sent: Thursday, October 23, 2014 12:56 PM
To: Kevin Billings; alcatel-nsp at puck.nether.net<mailto:alcatel-nsp at puck.nether.net>
Subject: [alcatel-nsp] RES: Filtering BGP routes using Extended communities

Kevin,

This example:

*A:T>config>router>policy-options# community "PE1_CE" members "target:65002|65003&."
*A:T>config>router>policy-options#

Cheers,
[cid:image001.jpg at 01CFEEFE.C3ADB9C0]
Hugo Roger Bernaola Pena
ALCATEL-LUCENT
CALA RBC - IPCC Consulting Engineer
AV. MARGINAL DIREITA ANCHIETA 400
Tel. : 55 11 2947-8956
Cel. : 55 11 98181-0358
hugo_roger_bernaola.pena at alcatel-lucent.com<mailto:hugo_roger_bernaola.pena at alcatel-lucent.com>

De: alcatel-nsp [mailto:alcatel-nsp-bounces at puck.nether.net] Em nome de Kevin Billings
Enviada em: quinta-feira, 23 de outubro de 2014 17:31
Para: alcatel-nsp at puck.nether.net<mailto:alcatel-nsp at puck.nether.net>
Assunto: [alcatel-nsp] Filtering BGP routes using Extended communities

Hi all,

I have a community set for a customer that is in the format target:ASN:x x being a range from 1-151.  I need to setup a BGP export filter that will match all of the communities and only export these routes.  If I use standard communities ASN:x then I can use this format and it works:

community "CUST-EXPORT" members "^ASN:(.*)$"

This does not work for extended communities.

Does anyone know how to make this work for extended communities?  Reading the ALU docs I should be able to reg-ex for these types of communities, but have not been successful.

I have tried these formats but I get invalid format:
community "CUST-EXPORT" members target:"^ASN:(.*)$"
community "CUST-EXPORT" members target:"ASN:*"
community "CUST-EXPORT" members "target:ASN:*"


Thanks


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20141024/3b3e9145/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 5715 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20141024/3b3e9145/attachment-0001.jpg>