Route-Servers-Abstract-Line-Graphic-NYIIX

NYIIX ROUTE SERVERS

About the Route Servers

Telehouse America offers NYIIX Members the opportunity to peer via our New NYIIX Route Servers.

1. Benefits of Using the Route Servers:

Based on BIRD Internet Routing Daemon (http://bird.network.cz/)
Supports all IRR DBs as references to accept member’s routes (http://www.irr.net/docs/list.html)
Supports Export Filter based on BGP community attributes.
A large percentage of Members peer using the Route Servers. Once you connect you can start exchanging traffic immediately.
Setting up peering takes time and effort. When you use the Router Servers, only one peering session is required.
You will receive all routes announced by the members who peer with the Route Servers. When a new party connects you can automatically exchange new prefixes.

6. Communities Supported

NYIIX Route servers support the following communities:

Eval Order	Community	Action
1	0:peer-as (standard)	Do Not Advertise to peer-as
	rt:0:peer-as (extended)
	ro:0:peer-as (extended)
	13538:0:peer-as (large)
2	13538:peer-as (standard)	Advertise to peer-as
	rt:13538:peer-as (extended)
	ro:13538:peer-as (extended)
	13538:1:peer-as (large)
3	0:13538 (standard)	Do Not Advertise to any peer
	rt:0:13538 (extended)
	ro:0:13538 (extended)
	13538:0:0 (large)
4	13538:13538 (standard)	Advertise to any peer
	rt:13538:13538 (extended)
	ro:13538:13538 (extended)
	13538:1:13538 (large)

Note on Google routes (Google Verified Peering Provider):
Google (AS15169) prefixes reach NYIIX via the Google Verified Peering Provider (GVPP) program. When using BGP communities to control announcements to or from Google, the peer-as value is 401887 (NYIIX GVPP service ASN), not 15169.

0:401887 — Do not advertise to Google
13538:401887 — Advertise only to Google

[!IMPORTANT]
The communities 0:15169 / 13538:15169 have no effect.

NYIIX Route-Servers-Abstract Lines Graphic

4. How do I Join the Route Server Service?

Prerequisites

Either AS-SET or Aut-num must be registered with an IRRdb.
Either Route objects or Route6 objects must be registered with an IRRdb.

Provide the following information:

ASN
IP Address at IIX: IPv4 or IPv6 or both
AS-SET name in Internet Routing Registry (the “IRR”) and the IRRdb in which it is registered. ex: RIPE RADB, ARIN etc..
TCP MD5 Signature: yes or no. If yes, need a password from you.
GTSM: yes or no

Please contact our IIX Engineering team to join the Route Servers @ iixeng@telehouse.com

5. Route Servers

NYIIX-NY Route Servers:

198.32.160.1/23 (primary)
198.32.160.2/23 (secondary)
2001:504:1::a501:3538:1/64 (primary)
2001:504:1::a501:3538:2/64 (secondary)
ASN 13538

*In order to receive all prefixes from the Route Server, “no bgp enforce-first-as” needs to be configured on your side.

NYIIX-LA Route Servers:

149.112.104.1/23 (primary)

149.112.104.2/23 (secondary)

2001:504:a::a501:3538:1 /64 (primary)
2001:504:a::a501:3538:2 /64 (secondary)
ASN 13538

*In order to receive all prefixes from the Route Server, “no bgp enforce-first-as” needs to be configured on your side.

6. Communities Supported

NYIIX Route servers support the following communities:

Eval Order	Community	Action
1	0:peer-as (standard)
	rt:0:peer-as (extended)	Do Not Advertise to peer-as
	ro:0:peer-as (extended)
	13538:0:peer-as (large)

2	13538:peer-as (standard)
	rt:13538:peer-as (extended)	Advertise to peer-as
	ro:13538:peer-as (extended)
	13538:1:peer-as (large)

3	0:13538 (standard)
	rt:0:13538 (extended)	Do Not Advertise to any peer
	ro:0:13538 (extended)
	13538:0:0 (large)

4	13538:13538 (standard)
	rt:13538:13538 (extended)	Advertise to any peer
	ro:13538:13538 (extended)
	13538:1:13538 (large)

Learn More About NYIIX Route Servers and How to Join Today.

Enter your email to get in touch or find out more.