Route Servers

There are two route servers per exchange, which use the routing daemon BIRD to reflect routes received from peers to other peers to form the multi-lateral peering environment.

By nature of reflecting routes, the IX peering ASN (7606) is removed from all sessions, so please ensure your router is configured to expect this (e.g. no bgp enforce-first-as).

All IX route servers are configured with passive BFD, and all BGP sessions have BFD enabled by default. The use of BFD on your route server BGP sessions is optional. If you require BFD for your route server BGP sessions, please refer to your vendor documentation for configuration guidance.

AS-Sets

To define your peering session policy, we require an AS-Set that includes your ASN as well as any other ASNs you are announcing. This is supplied when you order your Peering Service, and can be changed later by editing your Peering Service.

If you need assistance creating an AS-Set, please refer to APNIC's guide for the AS-Set object type or contact us.

Configuration Deployment

Configuration changes to the route servers across all IXes are deployed via two methods:

Method 1: Automated provisioning. From the Member Portal, any new peering order or modification will instantly deploy to the route servers and reflect the progress back to you. See Change Requests for more information.

Method 2: Set schedule. The route servers also redeploy their configuration daily at the following times (Sydney local time):

Route Server 1 at 8am
Route Server 2 at 1pm

Communities

We have made available BGP communities that are universal across all exchanges. These communities allow peers to set specific policies for their sessions. If you require assistance, please contact us.