Route Server Configuration
CM-IX has two route servers connected to separate switches in the exchange fabric for member routes. These route servers do not forward any traffic. The third route server is for Content Delivery Networks and does handle traffic forwarding.
For members participating in multilateral peering, its recommended to peer with both route servers for redundancy. The default behavior of the route servers will announce all routes to all peers.
Server | ASN | IPv4 | IPv6 |
|---|---|---|---|
Route Server 1 | 397186 | 207.241.143.2 | 2606:E400:241:143::2 |
Route Server 2 | 397186 | 207.241.143.3 | 2606:E400:241:143::3 |
*The route server AS will be removed from the path, 'no bgp enforce-first-as' or equivalent is required.
IRR
The route servers require all routes to be registered in a public Internet Routing Registry. Downstream ASNs need to be registered as part of your as-set.
Filtering
The following prefixes are not permitted on the route servers and will be filtered out:
-
Default Routes
-
RFC1918 prefixes
Communities
OPTIONAL
For granular control, the following community strings are supported.
​
Large-communities are used for both 16 bit and 32 bit AS number support.
397186:0:peer-as
| Prevent announcement to peer |
397186:1:peer-as | Announce to peer |
397186:0:0 | Prevent announcement to all peers |
397186:101:peer-as | Prepend peer AS once |
397186:102:peer-as | Prepend peer AS twice |
397186:103:peer-as | Prepend peer AS three times |
* Well known communities are not interpreted by the route servers and are passed though to peers. (Includes NO_EXPORT and NO_ADVERTISE)
CDN Route Server
For access to Content Delivery Networks, members can peer with Route Server 3.
Server | ASN | IPv4 | IPv6 |
|---|---|---|---|
Route Server 3 (CDN) | 397186 | 207.241.143.4 | 2606:E400:241:143::4 |
No routes are advertised by Route Server 3 and members should configure a deny policy for received routes. Only member originated routes should be advertised to Route Server 3.