Route server

VSIX offers to the networks connected to the Peering LAN the opportunity to peer via its route servers.

We operate two route servers: rs1.vs-ix.net and rs2.vs-ix.net (based on BIRD).

Both offer automatic network filtering based on their IRRdb entries and AS filtering based on community.

Therefore peering with the route servers does not eliminate the possibility of maintaining your peering policy.

Introduction

Normally, you need to maintain separate BGP sessions to each of your peers' routers. With a route server you can replace all or a subset of these sessions with one session towards each route server.

The goal of the route server project is to facilitate the implementation of peering arrangements, and to lower the barrier of entry for new participants on the peering platform.

The route servers do not partake in the forwarding path, so they do not forward any traffic. Also, peering with a route server does not mean that you must accept routes from all other route server participants.

Why would you use the route servers?

Let's make it easy
Simplify the setup to as many peers as possible on the VSIX network. With just two BGP sessions, you can connect to all the networks on the route servers. When a new party connects to the route servers, you can automatically exchange prefixes.

Manage only your most important peers, let the route server do the rest
You probably want to exchange as much traffic as possible through the exchange, but setting up a peering takes time and effort. So only set up peering sessions with your most important peers. Let the route server do the rest.

Send and receive routes from day one
Once you connect to the route servers you will start exchanging routes immediately. The route servers are a good way to get started on the exchange.

Use it as a backup
When your BGP session to a party becomes inactive, there is a possibility that you can still connect to them via the route servers. So the use of the route servers can lead to a more stable platform.

Route Server details

rs1.vs-ix.net
ASN: 2593
IPv4: 95.140.129.254
IPv6: 2001:7f8:5f:ffff::ffff

rs2.vs-ix.net
ASN: 2593
IPv4: 95.140.129.253
IPv6: 2001:7f8:5f:ffff::fffe

We encourage networks to peer with both route servers for resilience.
Write to staff@vsix.it to enable your BGP session and for any other details.

With the help of BGP Community the member may decide who he wants to “give” the traffic to.
The following BGP Community is maintained for every announced prefix:

BGP Community TIPS for RS
0:MEMBER-AS Do not announce to this member
2593:MEMBER-AS Announce to this member
0:2593 Do not announce to any member
2593:2593 Announce to all members

BGP Communities for 32-bit AS numbers

To use BGP communities with 32-bit AS numbers, set MEMBER-AS values as listed in the following table:

Member AS BGP Community (MEMBER-AS)
Digisat 198240 65000
Elsynet 196983 65001
3P System 199837 65002
Nexus 199947 65003
ZG Elettronica 200794 65004
Cesena.net 200043 65005
NETandWORK 201877 65006
VOIX 199547 65007
Pasubio Tecnologia 200480 65008
Yarix 206816 65009
Unica TLC 203223 65010
Progetto 8 198721 65011
Lepida2 205139 65012
Comune di Padova 204546 65013
Airgrid 201198 65014
Snapsystem 210224 65015
Hynet 199666 65016