Multi-Lateral Peering Exchange (MLPE)
The MASS IX route server service consists of two separate VM hypervisors running Cisco CSR1000v with iBGP session in between. From time to time, MASS IX staff will conduct maintenance on the boxes that will cause BGP sessions to go down momentarily. Therefore, two route servers are provided for redundancy- service will be maintained if you are peered with both route servers, as you will continue to receive routes from the second route server.
Note: Peering with route servers is optional and not required of participants.
MASS IX Route Server InformationAS Number26563Route Server #118.104.22.168
2001:504:47::CE35:8FFC:1Route Server #222.214.171.124
Route Server Configuration
For Cisco, you need to configure "no bgp enforce-first-as" in order to use the route servers. RS will feed you routes without appending its own AS number, in order to ensure transparent propagation of routes without modifying attributes. A sample route server peering configuration will look like:
! router bgp $your_as_number no bgp enforce-first-as ! neighbor 126.96.36.199 remote-as 26563 neighbor 188.8.131.52 description rs1.mass-ix.net neighbor 184.108.40.206 send-community both neighbor 220.127.116.11 remote-as 26563 neighbor 18.104.22.168 description rs2.mass-ix.net neighbor 22.214.171.124 send-community both neighbor 2001:504:47::CE35:8FFC:1 remote-as 26563 neighbor 2001:504:47::CE35:8FFC:1 description rs1.mass-ix.net neighbor 2001:504:47::CE35:8FFC:1 send-community both neighbor 2001:504:47::CE35:8FFD:1 remote-as 26563 neighbor 2001:504:47::CE35:8FFD:1 description rs2.mass-ix.net neighbor 2001:504:47::CE35:8FFD:1 send-community both ! address-family ipv4 neighbor 126.96.36.199 activate neighbor 188.8.131.52 prefix-list $your_outbound_prefix_list out neighbor 184.108.40.206 activate neighbor 220.127.116.11 prefix-list $your_outbound_prefix_list out ! address-family ipv6 neighbor 2001:504:47::CE35:8FFC:1 activate neighbor 2001:504:47::CE35:8FFC:1 prefix-list $your_ipv6_outbound_prefix_list out neighbor 2001:504:47::CE35:8FFD:1 activate neighbor 2001:504:47::CE35:8FFD:1 prefix-list $your_ipv6_outbound_prefix_list out ! !
Route Server Control
Filtering of incoming routes can be done by yourself by applying an inbound route policy (such as route-map) against MASS IX route server sessions.
For controlling outbound routing information, you can do this by sending us BGP communities as follows:block announcement of a route to certain peer0:<Peer AS>announce a route to a certain peer26563:<Peer AS>block announcement of a route to ALL peers0:26563announce a route to ALL peers (default behavior)26563:26563
Communities not starting with 26563: or 0: will not be processed by the RS. Routes with no community at all will be construed as "26563:26563" and be sent to all peers by default. Please don't forget to set "send-community" against MASS-IX route server neighbors if you want to influence route propagation.
IX Participants with 32-bit ASN
MASS IX implements N:M filtering based on standard community strings. As standard BGP communities support only 4 bytes, this only works for 2-byte ASNs and peers with 2-byte ASNs. For BGP peers with 32-bit ASN, substitute the "<Peer AS>" section in accordance with the following list:Enfopoint (AS393965)65000EndLayer (AS393965)65002VI Concepts (AS394149)65003
Route Server Transparency
MASS IX route servers will propagate BGP routes while transparently passing the following attributes unchanged: MED, AS Path (RS will not append its own ASN to the path) and next-hop. The transparency of attributes is important for many reasons, including ease of traffic engineering and to facilitate redundancy. For example, some networks may have a mix of both bilateral and multilateral sessions to a same peer.
To peer with MASS IX route servers, please email your request to email@example.com.