Guide to route server usage at MBIX.
MBIX runs two route servers. Here we describe their operation and suggestions for using them to the benefit of your network.
These route servers run BGP and allow members’ routers to exchange routes with each other more easily than peering with every member individually. They implement multilateral peering: if you peer with the route servers, you automatically peer with everyone else who peers with them.
Without the route servers, you would need to configure your router with the IP address and parameters of every other member. Each time a new member joined, you would need to add that configuration to your router. Most people do not need that hassle and choose to use the route servers instead.
Not all MBIX members choose to peer with the route servers, but most do. The peers page confirms their route-server peering status.
The route servers are dual-stacked on IPv4 and IPv6. You should peer with both for redundancy. The route servers are maintained with up-to-date software and will go down for maintenance, but only one at a time, with 24 hours of stability between outages.
The route servers use AS16395, the MBIX Peering ASN. The route servers do not insert their own AS into the path. You will see routes the same as if you established direct peering to the remote AS. See the configuration examples below for router configuration tips.
Send all routes that originate from your AS and routes of your customers. Customers are ASes to which you provide transit as a service. Do not advertise routes of your private peers, or you may accidentally provide transit to them. This applies equally to IPv4 and IPv6.
You will receive all routes shared by other MBIX members. This applies equally to IPv4 and IPv6; MBIX is fully dual-stack.
Other ISPs send their routes and customer routes to the route server. The route server then echoes these routes back to you, preserving the BGP next-hop value.
See the dynamic Pelican Route Server Configuration.
Yes. Starting in October 2018, the Pelican route servers have performed fully automated filtering.
We pull data from IRR and RPKI. We determine your AS-SET by querying PeeringDB for your ASN.
The route servers filter on:
208.81.0.0/21 or 2605:e200::/32.The MBIX Looking Glass is lg.mbix.ca.
Use the Looking Glass to examine the best path MBIX has for a specific route, or examine which routes your AS is sending to the route servers.
We strongly recommend setting the LOCAL_PREF for routes received from MBIX higher than routes received from your transit providers.
Giving MBIX routes a higher LOCAL_PREF causes your router to prefer sending data via MBIX rather than your costly transit providers.
Manipulating LOCAL_PREF is often done with a route map; see the Cisco configuration tips below.
The route servers are 1U AMD64 server systems. They run Debian GNU/Linux 12 and an updated version of BIRD 2 — Internet Routing Daemon. We have two active servers and one spare, all connected to the peering fabric with 10G-LR optics.
See the complete Cisco BGP Configuration Tips guide.
Sure:
Disable spanning tree on your port/VLAN. The MBIX switchport will be disabled for 30 minutes if it receives a BPDU from your equipment.
Use no bgp enforce-first-as in your router bgp xxxx configuration to allow Cisco IOS to accept a route from route-server AS16395 without seeing AS16395 in the AS_PATH.
Apply a route map to increase local preference. If routes received from your transit provider have a local preference of 100, set the local preference to 200 on routes received from MBIX:
neighbor 206.72.208.11 route-map LOCALPREF-mbix in
route-map LOCALPREF-ix permit 10
set local-preference 200
Use no cdp enable to disable CDP on the interface facing MBIX.