Routing Instance Details
The RI defines how peering will work with the owner of the RI and all services selected to create or subscribe. It includes virtual routing and forwarding (VRF) and a series of routing statements that help control the flow of traffic between all the connectors attached to it, and all the subscriptions attached to it.
A RI has the following required parameters to create:
RI type: choose either public or private. Users can send either private or public routes to a private RI, but only public routes to a public RI
Important: Users should check the specifications of the services they wish to subscribe to, as most restrict what type of routes they are willing to receive, or you might need to add additional services to make the RI work properly, such as NAT.
Autonomous system number (ASN): indicate a BGPBorder Gateway Protocol. A standardized exterior gateway protocol designed to exchange routing and reachability information between autonomous systems on the internet ASN from your network that the ECX will peer with. It can be either public or private, regardless of your IP addressing schema, and can be either 2- or 4-byte. Certain ASNs are restricted because they are already dedicated to other purposes, and the system will tell you which ones those are. The value is entered as a number only
Primary RI name: this will default to “RI-[incrementing numeral]-[metro]” but the user can enter any value they want, as long as it is unique to their account and that metro
Conditional (MD5 authentication): users can check this to require all connectors to this RI to have a specific MD5 authorization keyThe authorization key typically contains alpha-numeric characters and is a unique identifier authorizing Equinix to provision a connection towards the CSPNote: To Equinix, authorization key is a generic term and is NOT encrypted on ECX. CSPs might use a different name to refer to the same key. For example: Azure ExpressRoute calls the authorization key the “service key” while AWS calls it the “account ID”, and the key must be entered so that our systems will recognize and permit them.
Note: Subscriptions do NOT require MD5.
Conditional (Redundancy): if the user selects this, a second and identical RI will be created on the secondary ECX router group and the user will be prompted to enter a name for that RI in addition to the primary below
Notifications: user indicates any email addresses to receive notifications about this component
Some RIs, once added to a service profile with specific additional optional services, will be limited in what they can do. For example, under normal operating conditions, an RI can be used for both “outgoing” subscriptions to services you wish to procure, and as part of a profile of services you wish to offer to others. However, if an RI is part of a profile that also has the “Equinix-only routes” service added, it will be unable to host outgoing subscriptions until that RI is removed from the profile and any active “incoming” subscriptions to it have been deleted.
In general, a user cannot delete an RI until all subscriptions associated with it—whether they belong to the same account or not—have first been removed.
The ECX will remove private ASNs when advertising to the party on the other side, regardless of traffic direction.
Tip: If you are building a private network with private ASN and addressing that you will not broadcast as a public service profile, we recommend using the same private ASN on both RIs in a solution.