BGP Communities
BGP communities which you can use for traffic engineering.
BGP communities in general provide an in-band mechanism to provide additional information along with routes announced through BGP. This information can be used for administrative but also technical purposes, such as route-filtering, prepending and preferring.
Traffic Engineering
At AS215085 we provide communities to allow customers to manage their traffic, our communities use the following logic to influence routing.
- Do not export:
215085:0:0 - Do not export to downstream customers:
215085:0:1 - Do not export to Eranium:
215085:0:35133 - Do not export to Xyphen IT:
215085:0:211588 - Do not export to InterRacks:
215085:0:42093 - Do not export to ERA-IX:
215085:0:206221 - Do not export to ENS-IX:
215085:0:215549
For internet exchanges we use the route-server to refer to the entire internet exchange, more specifics are currently not available for direct peering sessions over internet exchanges. Route-server communities will be passed through to the exchange. So the internet exchanges’ communities can be used as well.
Direct peering sessions include but are not limited to: AS6939, AS24940, AS13335, AS32934, AS15169
the documenation for ERA-IX can be found here
We support pass-through of communities to our upstreams.
Upstreams
We currently use the following upstreams for our network.
- InterRacks - AS: 42093
- Xyphen IT - AS: 211588
- Eranium - AS: 35133
- ERA-IX - AS: 206221
- ENS-IX - AS: 215549
Tagged communities
All incoming routes are tagged with specific communities to indicate their source. This makes it easier to identify customer prefixes and apply appropriate routing policies.
- Customer prefixes:
215085:100:100 - Prefixes from Xyphen IT:
215085:400:211588 - Prefixes from InterRacks:
215085:400:42093 - Prefixes from Eranium:
215085:400:35133
- Prefixes from ERA-IX RS:
215085:200:206221 - Prefixes from ERA-IX direct peers:
215085:200:2 - Prefixes from ENS-IX RS:
215085:400:215549 - Prefixes from ENS-IX direct peers:
215085:400:2