A routing instance (RI) is the most important component of a Layer 3 service. It sets up the necessary elements to peer with ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection and serves as the hub for most of your routing policy and business rules that govern the dynamic nature of your services.
To access the Routing Instances section, navigate to the Inventory page and click the Routing Instances tab.
To find a Routing Instance, go to the Search Routing Instances text field and enter the name of the Routing Instance you want to locate. The handy autocomplete function helps you narrow down the list.
The filter bar contains a number of useful options so that you can sort and narrow your search results. You can sort your Routing Instances based on: location, status, name and date created. To sort your results, simply click the drop-down for each category.
Create a Routing Instance
From the Inventory page, select the "Routing Instances" tab, and click Create Routing Instance to begin. You need to input or select:
Basic Information: Select location, name, and redundancy settings
Route Type: Equinix highly recommends that you check with each provider you may want to subscribe to, as many of them do not accept Private Routes.
Autonomous system number (ASN)
Optional ASN authentication can be enabled and requires a key.
Note: Certain ASNs and ranges are reserved for network use. The reserved list can be viewed by clicking the info (i) icon. You can not create a routing instance if the ASN field is invalid.
Manage your Routing Instances
Edit a Routing Instance
From the Routing Instance details window, you can edit the Routing Instance name and notification contact information. First, click the Edit link in the section you want to modify, then make the changes, and click Update. If the edit is successful, the updated name appears in the header, and the recent activity section records the change. Only RIs in “Provisioned” status can be edited.
Clone a Routing Instance
When you clone, you can make a copy of an existing RI. In the Routing Instances detail window, click the Clone button. A new, pre-populated "Create Routing Instance" displays with all parameters replicated, except for the name.
You find the following settings are replicated in the new RI: location, public vs. private, ASN, redundancy, email contact, and 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”. You can still modify the parameters before you complete the RI request. Click Next to continue, review and submit the Clone Routing Instance request.
Delete a Routing Instance
Before you can delete a RI, you must first remove any subscriptions, connectors or service profiles attached to the RI. Only RIs that have a “Created” status can be deleted. At the bottom of the Routing Instance details window, click Delete Routing Instance. A message asks you to confirm your decision. Once you confirm, a notification appears to indicate your request is successful. The status on the RI card icon changes to “Being Deprovisioned.” As a result, you can no longer modify this RI.