GAIA BGP support for domain-id: or target: communties

[Boris_Karnaukh]

I have a POC where I have BGP peering with Juniper SD-WAN.

Juniper SD-WAN tags BGP announcements with BGP communities domain-id: and target: This feature is very convenient for BGP peerings since you can easiky distinguish between different SD-WAN participants. Below you can see a BGP announcement example:

172.27.2.16/28 (2 entries, 1 announced)
Accepted
Nexthop: 172.19.#.#
AS path: 65000 64512 I
Aggregator: 65000 172.19.#.#
Communities: 64512:64512 target:64512:#### origin:64512:2 domain-id:64512:##### target:10.187.0.2:1

Is it possible to refer to domain-id: communities in BGP route export- and import-maps? The routemap parameter community allows simple community match (64512:64512) in this case, but does not provide syntax for more complex cases.

As I can see, routemap parameter community-regex supports free syntax. My question is simple:

• anyone tried using community-regex to filter domain-id: communities?
• how much use of community-regex will affect routed performance?

[PhoneBoy · Accepted solution]

Officially, this is an RFE and recommend working with your local Check Point office around the requirement.