home | Technology & Services | Route Servers
last change: September 10, 2019

Route Servers

The Vienna Internet Exchange offers a redundant set of route servers, which eases peering configuration. The route servers just provide routing information, the actual traffic flows directly between the participants. After establishing the BGP sessions to both route servers and activating them in the web portal, participants can configure default settings and exceptions (per peer) in a web interface.

If all your desired participants peer with the route servers it would be enough to establish two BGP sessions. Furthermore - if configured accordingly - there is no action needed if a new participant activates his route server in order to exchange routes and data with the new participant. There is a web interface for IPv4 and one for IPv6; both offer the same features.


Activation

To activate the route servers, you need a portal account - and also the authorization in the web portal to administer the route servers. If you already have a portal account, please send us your updated portal account request (you can of course keep your existing username) to noc(at)vix.at. After your administrative contact has confirmed that you should be granted the permission to administer the route servers, we will assign it to you.


How it works

Configuration Interface
Configuration Interface Route Servers

For each participant router, there is a BGP process on both route servers. The route servers receive announcements from the VIX peers and mark prefixes which are missing in the RIPE Database with a special BGP community. A rule set based on the decisions of the participants in the web interface decides, which prefix information will be exchanged between the routing processes. A peering is solely established if both partners agree on the peering relation. By doing so, we make sure that peerings are bidirectional only.

Each participant can decide whether he wants to receive the prefixes found in the RIPE Database only, or whether all prefixes are accepted (also those not to be found in the RIPE Database). Prefixes not to be found in the RIPE Database are marked with the BGP community 1121:1.

Furthermore, each participant has the possibility to setup "BGP as-path prepends" per peer. These settings refer to the own announcements into the direction of the chosen peer.

We recommend to not set a "max-prefix" limit towards the route servers, as due to heavy growth this limit could be reached very soon and the entire "route server cloud" could be inaccessible for you. The route servers have a "max-prefix" limit of 15.000 prefixes (IPv4) resp. 900 prefixes (IPv6) per peer themselves.

If you have any further questions, please don't hesitate to ask admin(at)vix.at.