Action BGP Communities

Action BGP Communities can be used to control various functions of the route server. With these communities, you can: 

• control the redistribution of advertised prefixes, based on an ASN or on geolocation
• prepend your own ASN up to three times
• trigger the calculation of a new alternate path (if available) for your advertised prefixes before you start commencing a maintenance

Please note that if the $PEER-AS is a four byte AS number you have to use the BGP Large Communities. 

Control of prefix redistribution 

You can control which BGP announcements you send to the route servers are redistributed to other peers. This can be done based on the following criteria: 

• ASN
• Edge node

Redistribution can be controlled with BGP Communities and BGP Large Communities. 

Please note: The following table gives an overview of available options and their corresponding BGP Communities. The according values for $SWITCH, $METRO, $COUNTRY, $CONTINENT are available here.

In case two or more BGP (large) Communities are contradicting the community with the lowest evaluation order is processed.

* Only useful in combination with one or more "do not announce" BGP Communities with lower priority that will allow an override (e.g. 37793:$PEER-AS can provide a selective override for 65222:$METRO) 

The route servers remove the aforementioned BGP Communities and BGP Large Communities from a BGP announcement before re-distributing it. 

The well-known BGP Communities NO_EXPORT (65535:65281) and NO_ADVERTISE (65535:65282) are also honored meaning that a BGP announcement marked by one of these communities is not re-distributed to any peer. If you want the route server system to add a NO_EXPORT or NO_ADVERTISE community for a given BGP announcement before re-distributing, you have to add the community (37793:65281) or (37793:65282) respectively. This is also possible on a per-peer basis using BGP Large Communities:

• (37793:901:$PEER-AS) for selective NO_EXPORT and
• (37793:902:$PEER-AS) for selective NO-ADVERTISE

More than one of the aforementioned BGP Communities and BGP Large Communities can be added to a single BGP announcement. DE-CIX recommends not to add more than 50 of these communities as it makes handling complex and error-prone. If you need to do this, please contact Customer Service. 

All BGP Communities and BGP Large Communities that are not listed above are not touched by the route servers and transparently re-distributed. For backwards compatibility, routes with no community at all are distributed to all peers as well. 

You can check this in the AF-CIX Looking Glass. If you type your ASN into the global search field, you will find all matching prefixes from all AF-CIX route servers. By clicking on a prefix, you get the prefix information dialogue with details (BGP Comunities etc.). You can apply further filters, e.g. filter for a specific route server or IX.

How the different communities can be used 

Please note: In the following examples we only make use of BGP Large Communities when it becomes necessary. 

BGP announcements marked with the following communities are only re-distributed to AS64501 and AS64502 (both 2 Byte ASNs):

• (0:37793)
• (37793:64501)
• (37793:64502)
   

BGP announcements marked with the following communities are re-distributed to all peers/ASNs except AS64501 and AS64502:

• (0:64501)
• (0:64502)
• (37793:37793)

BGP announcements tagged with the following communities are only re-distributed to AS65550 (4 Byte ASN) and AS64501 (2 Byte ASN):

• (0:37793)
• (37793:1:65550)
• (37793:64501)

AS Path Prepending 

You can use BGP communities to prepend your own ASN up to three times. This can be done to all other peers or selective to only certain peers.