Route server details:
- General info on route servers is at AMS-IX Route Servers.
- The SIX ASN is 33108.
- Max prefix for IPv4 and IPv6 comes from your ASN's PeeringDB record. For your peering, if you use a max prefix with the route server, we recommend 100,000 for IPv4 routes and 30,000 for IPv6 routes.
- IPv4 routes shorter than /8 are filtered and IPv6 routes shorter than /19 are filtered. Bogon ASNs and martian prefixes are filtered.
- Strict filtering is performed using Internet Routing Registry (IRR) data. IRR Explorer may also be useful. You can verify your RADB data with:
IPv4 prefixes: whois -h whois.radb.net '!gasYOUR_ASN_NUM' IPv6 prefixes: whois -h whois.radb.net '!6asYOUR_ASN_NUM' AS-SET ASNs: whois -h whois.radb.net '!iYOUR_AS_SET_NAME'The route servers update from the IRR about once per hour.
- The route servers are configured to be passive. If you have a PeeringDB record and IRR records, you are ready to peer with the SIX route servers. Your PeeringDB "IRR Record" should contain simply your IRR as-set name. The route servers use this information. (Please no colons in your as-set name. If you must have a colon, email info_a_t_seattleix.net for special handling.)
- IRR Setup tutorial.
- The route server service is intended to supplement, not replace your direct peering. If you have a peer you value, take the time to establish direct peering.
- It is important to establish sessions with all of the route servers available on the VLANs to which you are attached, so that maintenance on one route server does not affect your connectivity.
- The communities specified in the table below may be used to control the propagation of your routes. In addition, the RFC 7999 BLACKHOLE community 65535:666 is supported. See our blackholing page for additional details.
- The route server software is BIRD. Much appreciation to the BIRD team.
- BGP passwords (RFC 2385) are not supported.
- Jumbo VLAN participants: You may want to prefer the jumbo VLAN for equal paths received from both VLANs. One way to do this is with MEDs (external metric) since that will not override AS path selection.
- Write to info_a_t_seattleix.net to trunk your circuit to gain access to the Jumbo VLAN.
- A looking glass for prefixes sent to the route servers is available for each participant at the participants page, including the reasoning behind any prefixes dropped by the filters. Data may be a minute or two old. The error files listing dropped prefixes are reset daily UTC.
Route server list:
Route server example peer config:
no bgp enforce-first-as ! neighbor SIX-peer maximum-prefix 100000 neighbor v6SIX-peer maximum-prefix 30000 ! neighbor 22.214.171.124 remote-as 33108 neighbor 126.96.36.199 peer-group SIX-peer neighbor 188.8.131.52 description six_rs2 ! neighbor 184.108.40.206 remote-as 33108 neighbor 220.127.116.11 peer-group SIX-peer neighbor 18.104.22.168 description six_rs3 ! neighbor 2001:504:16::2 remote-as 33108 neighbor 2001:504:16::2 peer-group v6SIX-peer neighbor 2001:504:16::2 description six_rs2 ! neighbor 2001:504:16::3 remote-as 33108 neighbor 2001:504:16::3 peer-group v6SIX-peer neighbor 2001:504:16::3 description six_rs3
neighbor 22.214.171.124 remote-as 33108 use neighbor-group SIX description six_rs2 enforce-first-as disable address-family ipv4 unicast maximum-prefix 100000 restart 30 ! neighbor 126.96.36.199 remote-as 33108 use neighbor-group SIX description six_rs3 enforce-first-as disable address-family ipv4 unicast maximum-prefix 100000 restart 30 ! neighbor 2001:504:16::2 remote-as 33108 use neighbor-group SIXv6 description six_rs2 enforce-first-as disable address-family ipv6 unicast maximum-prefix 30000 restart 30 ! neighbor 2001:504:16::3 remote-as 33108 use neighbor-group SIXv6 description six_rs3 enforce-first-as disable address-family ipv6 unicast maximum-prefix 30000 restart 30
Route server communities. These are processed by the route servers and not propagated. Unless prevented by a community, routes will be propagated to other route server peers. (For extended communities, ro == so == soo.):
|1||33108:0:peer-as||Do not advertise to peer-as|
|2||33108:1:peer-as||Advertise to peer-as|
|3||33108:0:0||Do not advertise to any peer|
|4||0:peer-as||ro:0:peer-as||Do not advertise to peer-as|
|5||33108:peer-as||ro:33108:peer-as||Advertise to peer-as|
|6||0:33108||ro:0:33108||Do not advertise to any peer|
|N/A||65001:peer-as||ro:65001:peer-as||33108:65001:peer-as||Prepend 1 time to peer-as|
|N/A||65002:peer-as||ro:65002:peer-as||33108:65002:peer-as||Prepend 2 times to peer-as|
|N/A||65003:peer-as||ro:65003:peer-as||33108:65003:peer-as||Prepend 3 times to peer-as|
rs2 1500 MTU IPv4:
rs3 1500 MTU IPv4:
rs2 1500 MTU IPv6:
rs3 1500 MTU IPv6:
rs2 9000 MTU IPv4:
rs3 9000 MTU IPv4:
rs2 9000 MTU IPv6:
rs3 9000 MTU IPv6: