Technical Components

Equinix Fabric takes a component-based approach to service design and implementation. Users can create solutions using a set of micro-services, or with predefined configurations.

Equinix Fabric users are empowered to create solutions that ideally suit their network needs from a set of business objects that can be combined in a variety of ways:

  • The component model is highly scalable and flexible and can be combined into nearly unlimited solution variations
  • The same components are used by both buyers and sellers
  • Each component has a minimum viable operating state and a series of optional services that any user can enable to enhance their design

Note: In some cases, an optional service might be required depending on the configuration of other components in the solution. New services are added to the components with nearly every software release.

Components Involved in Building Solutions

There are several components you can use in building your Equinix Fabric solutions, including the following:

  • Port – Typically ordered separately from the portal. Speed and usage are accessed online.

  • Standard Port – Preferred when fewer connections might be needed per port and fixed connection speed tiers are sufficient.

    Note: Both port charges (monthly recurring charges (MRCs) and non-recurring charges (NRCs)) and connection charges (MRCs) apply.

  • Unlimited Port – New package that offers unlimited connections to enhance support capability when you need a higher number of connections.

  • Virtual Connections (VC) – For all connection types using a sub-interface.

  • Connector – A primary business object that connects two points, such as ports or routing instances. A Connector looks similar to the VC found in Layer 2 services, but is simpler to deploy and has more options based on where it terminates.

  • Routing Instance (RI) – An important component of the Layer 3 services, and sets up the necessary elements to peer with Equinix Fabric. It serves as the hub for most routing policies and business rules that govern network traffic routing.

  • Subscription – A method to acquire service profile services. Subscription includes information such as the required provider-specific technology and authentication, if requested.

  • Service Profile – Aggregates several other components for the purpose of offering services to create connections. A service profile is either Layer 2-centric (built around ports) or Layer 3-centric (built around Routing Instances).

Layer 2 Solution

Layer 3 Solution