VSIX offers to the networks connected to the Peering LAN the opportunity to peer via its route servers.
We operate two route servers based on BIRD.
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.
RPKI Filters
Route Server support RPKI for prefix validation. It will not be necessary for you to activate RPKI in your router, but if you do not already have it done, to fully use the service you will have to create the ROA associated with your networks within the reserved area of your IRR
IRR Filters
There are also IRR filters, that accept only prefixes that match with the Route Objects defined at the IRR
Route Server details
AS Number: 35836
Network IPv4: 185.1.115.0/24
Network IPv6: 2001:7f8:5f:ffff::/64
Route Server 1 IPv4: 185.1.115.251
Route Server 1 IPv6: 2001:7f8:5f:ffff:fff1
Route Server 2 IPv4: 185.1.115.252
Route Server 2 IPv6: 2001:7f8:5f:ffff:fff2
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.
BGP Communities
Route Servers support Satndard and Large BGP Communities
Communities that can be used in route servers to manage traffic::
Table with communities applied by route servers and related actions::
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: