Route Server Manual

Traditionally, at an Internet exchange point, network operators manually configure and maintain BGP sessions with every other network they wish to peer with. However, this process can be quite laborious, especially as more networks join the exchange and the number of required BGP sessions grows. As an alternative, we offer a Route Server service which automates this process. Networks that establish BGP sessions with our Route Servers will automatically peer with all other networks that use the Route Servers. This simplifies the process of peering and significantly reduces network management overhead related to the IXP.

Note that this service is optional and we do not require our members to use it. Network operators are free to establish bilateral BGP sessions with any or all other networks if they wish.

Technical Data
We currently operate two BIRD route servers hosted on separate physical hardware:

Route Server #1

  • ASN: 37386
  • IPv4:
  • IPv6: 2001:43F8:0130::11

Route Server #2

  • ASN: 37386
  • IPv4:
  • IPv6: 2001:43F8:0130::12

Large BGP Communities
Our Route Servers allow network operators to enforce selective peering policies by way of Large BGP Communities. See here for more information:

Important Notes

  • Prefixes announced to the Route Servers must be at least /24 or larger.
  • Route Servers only relay prefix announcements, and do not carry or forward any traffic between networks. They do not join the AS-PATH.

Example Cisco Router Client Configuration
Below is an example configuration for an exchange participant with a Cisco router who wishes to use our Route Servers.

router bgp <your-asn>
no bgp enforce-first-as (take special note of this line)
no synchronization
bgp log-neighbor-changes
redistribute connected

neighbor UIXP-Peers peer-group
neighbor UIXP-Peers remote-as 37386
neighbor UIXP-Peers version 4

neighbor UIXP-RS-Peers peer-group
neighbor UIXP-RS-Peers remote-as 37386
neighbor UIXP-RS-Peers version 4

neighbor UIXP-RS-6 peer-group
neighbor UIXP-RS-6 remote-as 37386
neighbor UIXP-RS-6 version 4

neighbor 2001:43f8:0130::0011 peer-group UIXP-RS-6
neighbor 2001:43f8:0130::0011 description eBGP with UIXP V6 route-server 1
neighbor 2001:43f8:0130::0011 prefix-list <your-prefix-list>
neighbor 2001:43f8:0130::0011 activate

neighbor 2001:43f8:0130::0012 peer-group UIXP-RS-6
neighbor 2001:43f8:0130::0012 description eBGP with UIXP V6 route-server 2
neighbor 2001:43f8:0130::0012 prefix-list <your-prefix-list>
neighbor 2001:43f8:0130::0012 activate

neighbor peer-group UIXP-RS-Peers
neighbor description eBGP with UIXP V4 route-server 1
neighbor prefix-list <some-bogons-list> in
neighbor soft-reconfiguration inbound
neighbor prefix-list <your-prefix-list> out

neighbor peer-group UIXP-RS-Peers
neighbor description eBGP with UIXP V4 route-server 2
neighbor prefix-list <some-bogons-list> in
neighbor soft-reconfiguration inbound
neighbor prefix-list <your-prefix-list> out
no auto-summary

address-family ipv4
redistribute connected

neighbor UIXP-Peers route-server-client
neighbor UIXP-Peers send-community
neighbor UIXP-Peers soft-reconfiguration inbound
neighbor UIXP-Peers distribute-list 150 in
neighbor UIXP-Peers distribute-list 150 out
neighbor UIXP-Peers maximum-prefix 1000 50

neighbor UIXP-RS-Peers soft-reconfiguration inbound
neighbor UIXP-RS-Peers distribute-list 150 in
neighbor UIXP-RS-Peers distribute-list 150 out
neighbor UIXP-RS-Peers maximum-prefix 1000 50

no auto-summary
no synchronization

address-family ipv6

neighbor UIXP-RS-6 soft-reconfiguration inbound
neighbor UIXP-RS-6 distribute-list 150 in
neighbor UIXP-RS-6 distribute-list 150 out
neighbor UIXP-RS-6 maximum-prefix 1000 50

We also host a Looking Glass system in order to help network operators diagnose technical issues related to the route servers. It will show BGP session information, prefix announcements, and other data for all networks who peer with it. The Looking Glass can be accessed via the following link: