BGP Communities
BGP Communities
Our locations :
Netaris Location | Code | Real Location |
PAR1 | 01 | DC2Scale PAR2 |
AMS1 | 02 | Nikhef Amsterdam |
PAR2 | 03 | Equinix PA5 – Netario infra |
Our BGP communities :
Our peering partners & transits :
For large communities format is as follows :
- peer-code→ 1XX(Transit), 2XX(Public peering), 3XX(Private Peering), 5XX(Netaris), 20XX(Customer)
- The X will represent different locations defined above
- peer-as → The ASN of the peer, no equivalent is possible for legacy communities for 32 bit ASN, so an alias is created below for each upstream or important peer
Legacy Community | Large Community | Upstream / Peering |
64615:1X0 | 211615:peer-code:peer-as | All peers |
64615:500 | 211615:5XX:211615 | Netaris |
64615:110 | 211615:101:212815 | PAR1 - Dyjix |
64615:120 | 211615:102:209768 | AMS1 - White2Net |
64615:130 | 211615:103:15830 | PAR2 - Equinix |
64615:2000 | 211615:20XX:peer-as | Customer |
Local preferences :
As a customer you can control the local preference of your prefixes on our network :
Community | Large Community | Value |
64615:5010 | 211615:5000:10 | 10 (Below everything-least preferred) |
64615:5100 | 211615:5000:100 | 100 (Below peers) |
64615:5150 | 211615:5000:150 | 150 (Below customer, above upstream) |
64615:5200 | 211615:5000:200 | 200 (Above customer default) |
Prepending :
As a customer you can control the prepending of your prefixes before we send them to upstream and peering :
Community | Large Community | Result |
64615:6001 | 211615:6001:0 | Prepend AS211615 1 time |
64615:6002 | 211615:6002:0 | Prepend AS211615 2 time |
64615:6003 | 211615:6003:0 | Prepend AS211615 3 time |
Partner-specific community :
With all of our partners, we have partner-specific communities, here is the format :
Legacy Community | Large Community | Effect |
N/A | 211615:6001:peer-as | Prepend 1x to peer-as |
N/A | 211615:6002:peer-as | Prepend 2x to peer-as |
N/A | 211615:6003:peer-as | Prepend 3x to peer-as |
N/A | 211615:6009:peer-as | Do not announce to peer-as |
The same applies for all of our peering partners defined above
The use of large community is mandatory for partner-specific communities.
Blackhole community :
We support the blackhole community and passes it to our peering partners when supported:
Legacy Community | Large Community | Effect |
64615:666 | 211615:666:0 | Nullroute /32 v4 and /128 v6 |
Graceful BGP shutdown :
We support the well-known community GRACEFUL_SHUTDOWN :
Legacy Community | Large Community | Effect |
65535:0 | 211615:5000:0 | Set local preference to 0 |
Our Routing Policies:
Our local preferences :
Route Source / Relationship | Transport / Variation | Local Pref Value | Comments / Policy Considerations |
Locally Originated | Local | 200 | |
Direct Customer | Direct | 199 | |
Direct Upstream | Direct | 120 | |
Direct Peer | Direct | 110 | |
Peer via IXP/PNI | IXP/PNI | 105 | |
Default | N/A | 100 | Routes that do not clearly fall in one of the above categories |
Distant Mesh Routes | Mesh between PoPs, exact local pref depends on the latency | 99-50 | These routes are used only when a direct link is not available. |