Introduction to Interconnections¶

As a part of Platform Equinix, your Equinix Metal™ infrastructure can connect with other parties such as public cloud providers, network service providers, or your own colocation cages in Equinix.

There are several options:

• Connect to AWS Direct Connect
• Metal-billed Fabric Virtual Connections
• Fabric-billed Fabric Virtual Connections
• Dedicated Ports

Availability¶

Interconnections are available in all Equinix Metal Metros. When you go to request a new Interconnection, you will select the Metro where you would like it to live. It should be the same Metro as the Equinix Metal servers and VLANs that you will use to connect to it.

On the other side of the Interconnection:

• Metal-billed Fabric Virtual Connections support connecting to Fabric in the same Metro.
• Fabric-billed Fabric Virtual Connections support connecting to Fabric or Network Edge devices across Metros.
• Connecting to AWS Direct Connect supports connecting to the equivalent AWS Region.
• Dedicated Ports provide the most flexible location options. Connect your Metal infrastructure to any other Cloud Service Provider, Fabric port, or your own colo in any other Metro.

Connecting to AWS Direct Connect¶

If your use case requires a connection from your Layer 2 Metal network to your AWS environment, Metal supports Connecting to AWS Direct Connect.

Intended for Metal-only customers; this does not require a Fabric account or access to the Fabric portal for configuration. All charges associated with this connection will be billed to your Metal invoice.

If you are both a Metal and a Fabric customer you can configure and manage these connections through Fabric, but the billing is still handled through your Metal invoice. More information for the Fabric user experience is available on the Quick Connect to AWS Direct Connect page in the Fabric documentation.

Signing Up for a Fabric Account¶

All of the following Interconnection options require a Fabric account or Equinix Customer Portal account.

• For all Fabric Virtual Connections, Metal-billed and Fabric-billed, an Equinix Fabric account and access to the Fabric portal is required.

• Specifically for Fabric-Billed Fabric VCs, you are required to have a Fabric billing account for Network Edge devices or Fabric port charges.

If you do not already have a Fabric account you can follow the set up on the New User Equinix Fabric Portal Access page from the Equinix docs. There is also a video walkthrough available.

Your use case for Dedicated Ports might also require a Fabric billing account, if you are connecting your Dedicated Ports to Fabric. If you are using Cross-Connects or Internet Exchange, you will need an account with the Equinix Customer Portal.

Connecting a Fabric Cloud Router to Equinix Metal¶

If you are a Fabric customer, you can connect a Fabric Cloud Router (FCR) over IPv4 or IPv6 to your Metal VLANs in the same Metro. Use the Fabric portal or the Fabric API to view and mange the network information and routing configuration between the FCR and Metal. All charges and billing for Metal to FCR connectivity is billed to your Fabric account.

Documentation on setup and configuration is available on the Connect to a Metal VLAN page in the Fabric documentation.

Metal-Billed Fabric Virtual Connections¶

Make a connection from Equinix Metal to other Cloud Service Providers on Fabric in the same metro, without the need for a Network Edge device. All usage is billed hourly, all charges for Metal-Billed Fabric Virtual Connections will appear on your Equinix Metal invoice. Rates can be found on the Interconnection product page.

Example Use Case - Connecting to a Public Cloud Provider in the Same Metro¶

1. Request a new Metal-Billed Fabric Virtual Connections in the Equinix Metal console.
2. Redeem the a-side service token in the Fabric portal.
3. Select the cloud service provider as the "to" side (z-side) of the connection from Equinix Metal.
4. Complete the networking setups for both Equinix Metal and the cloud service provider.

Note: You can connect to AWS using the process on Connecting to AWS Direct Connect. This feature is based on Metal-billed Fabric VCs, but all of the token redemption process is handled for you, and you do not need to manage a Fabric account.

Fabric-Billed Fabric Virtual Connections¶

Make a connection from your Fabric ports or Network Edge devices to Equinix Metal, either within the same metro or across metros. Use cases include using a Network Edge as a router for your Equinix Metal services or connecting Equinix Metal to a cloud service provider across Metros. All usage, Network Edge, and virtual device charges will appear on your Equinix Fabric account.

Example Use Case - Connecting to a Cloud Service Provider through a Network Edge Device¶

1. If you don't already have one, create a Network Edge device in the Fabric Portal.
2. Request a new Fabric Virtual Connection - Fabric Billed in the Equinix Metal console.
3. Redeem the z-side service token from Equinix Metal in the Fabric portal.
4. Setup the your Network Edge Device as the “from” side (a-side) of the connection to Equinix Metal.
5. Setup the Network Edge Device to the cloud service provider connection in Fabric Portal, by selecting the Public Cloud Provider (for example, AWS) as your “connect to” side (Z-side) and the same Network Edge Device above as the “from” side (a-side).
6. Complete the networking setups on both Equinix Metal and the cloud service provider.

Dedicated Ports¶

Make dedicated connections between Equinix Metal and your own physical Fabric ports, colocation cage/cabinet, or Cross Connects. Use cases include connecting to a 3rd-party Network Service Provider or appearing as a cloud service provider on Fabric so that other Equinix customers can make private connections to you. Dedicated ports are billed on Equinix Metal with a non-recurring charge for setup and a monthly recurring charge for usage. Rates for these charges can be found on the Interconnection product page. Any associated Fabric port charges or Cross Connect charges will appear on your Equinix Fabric or Equinix Customer accounts.

Example Use Case - Connecting to your Equinix IBX Colocation Infrastructure¶

1. Request a new Interconnection with a Dedicated Port in the Equinix Metal console.
2. Order a Cross-Connect through the Equinix Customer Portal.
3. When the order is completed (may take up to 10 to 15 business days), verify in the Equinix Metal console that the Port is “Active” and the link state is “Up”.
4. You can then create virtual circuits in the Equinix Metal console and continue your VLAN setups in Equinix Metal and on your colocation switching devices.

Example Use Case - Connecting to a 3rd-party Networking Service Provider¶

1. Request a new Interconnection with a Dedicated Port in the Equinix Metal console.
2. Order a Dedicated Port in the Fabric portal.
3. Once the Fabric Dedicated Port order is completed, create a connection in Fabric Portal by selecting the Networking Service Provider (NSP) as your “connect to” point (Z-side) and the Port you ordered from Equinix Metal as the “from” point (A-side).
4. Follow the recommendations from the NSP to set up your Layer 2 connections.

Virtual Routing and Forwarding Support for Interconnections¶

Metal offers a virtual router that provides Virtual Routing and Forwarding (VRF) support for your Metal Layer 2 networks that connect to destinations on Fabric or in an Equinix IBX. VRF is currently supported on:

• Metal-billed Fabric VCs
• Fabric-billed Fabric VCs
• Dedicated Ports.

For more information on how to configure VRF for Interconnections, refer to the Using VRF with Interconnections page.