Ir para o conteúdo principal

Fabric One

Equinix Fabric One is a network service that manages a private, resilient, and scalable any-to-any routed network interconnecting local endpoints.

You declare:

  • Where - The Equinix Metro where the Fabric One network is located. Fabric One networks are metro-based and connect local endpoints together within that metro.

  • What Endpoints - A Fabric One Endpoint is a destination in your Fabric One network, such as a Fabric port in your colocation space or a cloud provider connection.

  • How much Bandwidth - Endpoint Bandwidth is the bandwidth capacity you request for an endpoint. The Package Bandwidth determines the total amount of bandwidth that can be used by all endpoints within the Fabric One.

This creates a Fabric Interconnect - the orchestrated routing instance that performs the routing between your endpoints. Fabric One handles selecting and configuring the routing instances and the path between the endpoints; creating resilient virtual connections, building layer 2 and layer 3 configurations, and exchanging connection details with the cloud service provider. It sizes the connections to the bandwidth you request as needed to each endpoint.

Fabric One is:

  • Resilient by default. Every endpoint has at least two connections. Certain endpoints, such as AWS Interconnect have up to four connections.
  • Private. Traffic travels over the Equinix private network and does not cross the public internet. MACsec is also supported to select endpoints.
  • Managed end to end. Fabric One configures and manages the connections that make up your interconnect.
  • Scalable. New endpoints can be added dynamically.

Fabric One Preview​

Fabric One Preview

Fabric One is available for customers in Preview. Customers with existing Equinix accounts can build a Fabric One Interconnect and test non-production traffic between endpoints.

The following Fabric One capabilities are available to customers in Preview:

  • Metro Availability – Fabric One is available globally in the 66 metros where Fabric is available.

  • Fabric One Lab Package – The Fabric One Preview supports a Lab package with 3 Gbps of total bandwidth to endpoints. This package is available free of charge.

  • Endpoints – select endpoints listed below are available in preview:

    • AWS Interconnect
    • AWS Direct Connect
    • Microsoft ExpressRoute
    • Google Partner Interconnect
    • Oracle FastConnect
    • Fabric Ports

    Please note: the above endpoints require local presence in the same metro where the you are creating Fabric One. The cloud providers listed above may not have local points of presence with Equinix in certain metros.

  • User Interface – You can build Fabric One using the Equinix Customer Portal.

  • Usage and Service Guarantees – Preview is provided to customers for evaluation purposes only and is intended for non-production traffic. All Fabric One service is provided under our Evaluation Services Product Policy.

Fabric One Packages​

A Fabric One Package package pre-defines the following attributes of the Fabric One:

  • Metro where Fabric One is enabled.
  • Total bandwidth available for all endpoints connected in the Fabric One
  • Maximum routes allowed for the Fabric One.

The Package Bandwidth determines the total amount of bandwidth that can be used by all endpoints within the Fabric One. You are not limited to a particular number of endpoints for a package as long as the combined bandwidth to the endpoints is equal to or less than the total package bandwidth.

While in Preview, the only package available is the Lab package with 3 Gbps of total bandwidth to endpoints. This package is available free of charge.

Prerequisites​

  • You must have an existing Equinix Account.

  • You must have the Fabric Manager role. If you do not have this role associated with your user account contact your Company Administrator to give you permission. For more information, see Managing Users' Access and Roles.

  • You must have or create new Service Provider resources. Enabling cloud service provider endpoints requires new connections. You cannot reuse existing Fabric connections to cloud service providers.

Creating a Fabric Interconnect​

To start building your any-to-any Fabric One network:

  1. Sign in to the Customer Portal and navigate to the Interconnection Dashboard.

  2. From the Connections menu, select Fabric One.

  3. From the Fabric One Inventory page, click Create Interconnect.

  4. In the Create Fabric Interconnect panel enter the following info:

    • An Interconnect Name
    • A description (optional)
    • Select the project to create the Interconnect in.
    • Select the Metro location – this is the metro where Fabric One will be located.
    • Select a Billing Account.
    • Select the Fabric One Package. In Preview, Lab is the only available package.
    • Add email addresses for notification contacts for this Interconnect.

  5. Click Create Fabric Interconnect*.

Adding Endpoints​

To continue building your network, add endpoints.

  1. From the Fabric One Inventory page, click on your Interconnect's name.

  2. In the Endpoint section of the Interconnection Overview, click Add Endpoint.

  3. Select one of the available endpoints from the available Cloud Service Providers, and fill in the required information for that service provider.

    OR choose to connect to one of your existing Fabric Ports.

Adding an AWS Interconnect Endpoint​

For the Fabric One Preview, AWS and Equinix are supporting the following service scope for AWS Interconnect:

  • Interconnect speed of 1Gbps.
  • Supported metros and regions are Ashburn (us-east N. Virginia) and Silicon Valley (US West N. California).
  • MACsec encryption
  • AWS Interconnects are support from Equinix Fabric One Lab package in Preview
  • Bi-directional service flow. You can generate AWS Interconnect authentication keys from either the AWS console or Equinix Fabric One workflow.
  • No SLAs

Requirements:

  • An existing Fabric Interconnect in the Metro where you want to connect.

  • You need AWS Interconnect – last mile connection. Equinix supports the bi-directional provisioning flow when creating an AWS Interconnect. You can initiate a new connection from either the AWS Console or from the Equinix Customer Portal.

    • Start the process from the AWS Console, where you must have the Equinix Project ID for the Project containing your Fabric Interconnect. After creating the AWS Interconnect connection in the AWS console, enter the Activation Key from AWS when adding an endpoint to your Fabric Interconnect.

    • Start the process from the Equinix Customer Portal, where you must have your 12-digit AWS Account ID. Equinix does not ask for your AWS credentials to create the endpoint. When adding an endpoint to your Fabric Interconnect, generate an activation key and then provide it to AWS to complete the AWS Interconnect - Last Mile connection.

    For more documentation on how to create an AWS Interconnect - last mile connection, see Getting started with AWS Interconnect - last mile.

Adding an AWS Hosted Direct Connect Endpoint​

Add an AWS Direct Connect hosted connection endpoint to connect your Fabric Interconnect to your AWS environment. The endpoint is redundant consisting of two hosted connections to AWS Direct Connect, a primary and a secondary.

Requirements:

  • An existing Fabric Interconnect in the metro where you want to connect.
  • An AWS account with permission to accept Direct Connect connections and create virtual interfaces, and its 12-digit AWS Account ID. Equinix does not ask for your AWS credentials to create the endpoint.
  • A BGP ASN for your side of the peering. A public ASN must be owned by you; a private ASN must be in the private range.
  • The network prefixes you plan to advertise. Any advertised prefix must include only your ASN in the BGP AS-PATH.
  • Each hosted connection must be accepted in AWS and then attached to a virtual interface (VIF) before traffic can flow.

Adding a Google Cloud Endpoint​

Add a Google Cloud endpoint to connect your Fabric Interconnect to Google Cloud Partner Interconnect. Every endpoint is redundant consisting of two connections to Google Cloud, one for each pairing key.

Requirements:

  • An existing Fabric Interconnect in the metro where you want to connect.
  • A Google Cloud account with enough VLAN attachment quota. Provisioning fails if the quota is too low.
  • Two new Google Cloud pairing keys: a primary key (ends with /1) and a secondary key (ends with /2).

Adding a Microsoft Azure Endpoint​

Add a Microsoft Azure ExpressRoute endpoint to connect your Fabric Interconnect to Azure. The endpoint is redundant consisting of two connections to Microsoft Azure.

Requirements:

  • An existing Fabric Interconnect in the metro where you want to connect.
  • A Microsoft Azure account.
  • An ExpressRoute circuit created with Equinix as the provider, and its Azure Service Key.

Adding an Oracle Cloud Endpoint​

Add an Oracle Cloud Infrastructure (OCI) FastConnect endpoint to connect your Fabric Interconnect to your OCI resources. The endpoint is redundant consisting of two connections to Oracle Cloud Infrastructure, one for each Oracle Cloud ID (OCID).

Requirements:

  • An existing Fabric Interconnect in the metro where you want to connect.
  • An Oracle Cloud account with a Virtual Cloud Network (VCN).
  • Two FastConnect virtual circuits, with their OCIDs: a primary and a secondary.

Configure Routing​

After you have added some endpoints, configure the routing so traffic can flow.

  1. On the Fabric Interconnect Overview. In the Endpoints section, expand an endpoint to see its two connections.

  2. Click the options menu on a connection and select Edit Routing Settings.

  3. On the Basic tab, select the Address Family and enter the Fabric Interconnect Address (IPv4), for example 192.68.100.1/30.

  4. To use BGP, select Enable Border Gateway Protocol (BGP) and enter the BGP Peer Address (IPv4), an optional Authentication Key, and the Peer ASN. The Advanced tab adds options for the maximum routes received and AS path prepending.

  5. Click Apply Changes, and repeat for the second connection.

Deleting an Endpoint​

Before you delete an endpoint to a cloud provider, deprovision the connection to the cloud service providers in the provider's console first. The provider side must be removed for the connection to finish deprovisioning.

  1. From the Fabric One Inventory page, click on your Interconnect's name.

  2. In the Endpoints section, click the options menu for the endpoint and select Delete Endpoint.

  3. In the Delete Endpoint dialog, check the endpoint name in the message in the confirmation dialog and click Delete.

A success message confirms the endpoint was deleted. The endpoint and its connections have the status DEPROVISIONING until they are removed, which can take up to a minute.

Deleting a Fabric Interconnect​

To delete a Fabric Interconnect, you must delete all endpoints first.

  1. From the Fabric One Inventory page, click on your Interconnect's name.

  2. From the Interconnection Overview, click Actions, and select Delete Interconnect.

  3. In the Delete Interconnection dialog, check the Interconnection name in the message in the confirmation dialog and click Delete.

A success message confirms the Fabric Interconnect was deleted. The Equinix-managed Fabric Cloud Router that was created with your Fabric Interconnect is deleted with it. Its status changes to DEPROVISIONED.

Esta página foi útil?