Normally on a peering exchange, all connected parties will establish bilateral peering relationships with each other member connected to the exchange. As the number of connected parties increases, it becomes increasingly more difficult to manage peering relationships with members of the exchange. However, by using a route servers for peering relationships, the number of BGP sessions per router stays at two: one for each route server (assuming a resilient set up). Clearly this is a more sustainable way of maintaining IXP peering relationships with a large number of participants.
NCL-IX uses the secure-by-default templates from IXP Manager to generate our route server configurations. This includes mandatory prefix filtering using IRRDB route objects and RPKI. The filtering algorithm is explained below.
If enabled, the route servers are set up to accept BGP connections from your router. Please contact email@example.com if not enabled or for assistance. Once enabled, you will need to configure BGP peering sessions to the each address of the resilient route server cluster: