Route Server Information
DE-CIX operates so-called route server systems (see RFC7947 for a detailed description) to facilitate the exchange of BGP announcements between peers at DE-CIX. Each peer needs only to set up a BGP connection to the route server in order to receive the BGP announcements of all other peers having a BGP connection with the route server.
BGP Session Parameters
This section provides a brief overview of the BGP session parameters to connect to the route servers:
|RIR macro (AS-SET)|| IPv4: AS-DECIX-NYC|
|Recommended prefix limit rs1/rs2 (your side): ||IPv4: 200,000|
BGP Announcement Filtering
This section describes the filtering mechanism that can be used to filter BGP announcements.
You can safely accept any BGP announcements received via the route servers as DE-CIX filters all incoming BGP announcements from all peers. The filtering mechanism is described in the Section "DE-CIX Side".
If you additionally want to filter on your side based on AS-SETs, you can do so by using one or more of the following AS-SETs registered in the RIPE database:
|RIR macro (AS-SET)||Purpose|
|AS-DECIX-NYC||AS-SETs of all DE-CIX NYC customers (IPv4)|
|AS-DECIX-NYC-V6||AS-SETs of all DE-CIX NYC customers (IPv6)|
|AS-DECIX-NYC-CONNECTED ||ASNs of all DE-CIX NYC customers |
At DE-CIX, the route servers filter based on AS-path as well as IP prefixes. The BGP announcements that a route server receives from a peer are checked against the AS-SET the peer has provided. The AS-SET can be changed by contacting the DE-CIX customer service team.
Route Server Setup
The route server setup at DE-CIX New York consists of two machines. The software utilized to provide the route server service is BIRD. Of the two route servers only one is required. However, in order to use the route server service, every peer is requested to connect to both machines for redundancy purposes, so that if one machine is out of order (e.g. maintenance), the route server service can still be used.
If the route servers system receive a BGP announcement marked as a Blackhole, the NO-EXPORT community and the BLACKHOLE Community are added if these communities are not already present. This makes sure each BGP announcement marked as Blackhole can be easily filtered and does not spread widely in the Internet routing system.
Route Server Control
Operational BGP Communities can be used to control various functions of the route server. With this communities, you can:
- control the redistribution of advertised prefixes
- prepend your own AS up to three times
- trigger the calculation of a new alternate path (if available) for your advertised prefixes before you start commencing a maintenance
More information can be found here.
Route Server Prefix Information
Informational BGP Communities are used to signal various information about redistributed prefixes. The DE-CIX route servers tag all prefixes with certain BGP Communities to indicate their origin. You can use this information to determine where a certain prefix has been injected into the DE-CIX switching platform. This gives you the possibility to filter routes learned from the route servers based on geographical location.
More information can be found here.
Route Server Session Types
We offer two session types:
Standard/Public Session (default)
- We re-distribute all your announcements to other peers while honoring the BGP Communities which allow you to restrict your announcements
- We advertise all announcements from other peers to you while honoring the BGP Communities which allow others peers to restrict their announcements
From an operational point of view, it is advised to set up BGP sessions to both route servers, even if you do not want to peer with (i.e. advertise prefixes to) the route servers. This helps DE-CIX staff to quickly monitor the availability of each peer.
Please note that you are required to set up BGP sessions with (but don't need to advertise prefixes to) the DE-CIX route servers to be able to claim credits for the GlobePEER service. Otherwise DE-CIX may not be able to comply with its SLA (please see DE-CIX GlobePEER Technical Service Description - III. IP LAYER CONFIGURATION (ISO/OSI LAYER 3) - Interface configuration).
If your decision not to establish BGP sessions with the route servers was made due to your peering policy, please contact us for establishing a monitoring only session. You don’t have to advertise any prefixes and you won’t receive any prefixes from us on that session.
The following section contains configurations examples for different router operating systems: