Equinix Cloud Exchange takes a “component-based approach” to service design and implementation. By this, we mean that users create their solutions using a platform-like set of “microservices,” or parts that can be bolted together one at a time or with some defined and preset configurations. Users do so in the way that best suits their network and needs from a set of business objects that are 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 whether you are acting as a buyer or a seller or somewhere in between. Each component has a minimum viable operating state and a series of optional services that the user can add to enhance the design. In some cases, an optional service may become required depending on the configuration of other components in the solution. New services are added to the components with nearly every software release.
The following is a summary of the components you will encounter when building solutions:
Port: physical access point between an ECX customer and the ECX. It is typically ordered separately from the portal but the results and use of it is accessed online.
- Standard port: suitable when fewer connections may be needed per port and fixed connection speed tiers are sufficient. Both port charges (MRC and NRC) and connection charges (MRC) apply
- Unlimited port: formerly known as Buyout port, this new package offers unlimited connections at $0 per connection to better support when you need a high number of connections
Virtual circuit (VC): used for most Layer 2 services using a sub-interface.
Connector: primary business object that “connects” two points together, such as ports or routing instances. It will appear 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): the most important component of a Layer 3 service that sets up the necessary elements to peer with the ECX. It serves as the hub for most routing policy and business rules that govern the routing of traffic.
Subscription: method in which you get services that are part of a service profile. It includes information such as the required provider-specific technology and authentication, if requested. For Layer 2, this mostly happens in the background. In the context of a Layer 3 service profile, you “subscribe” your RI to that service profile, then routes are advertised between the two parties in a pre-arranged import/export policy.
Service profile: business object that aggregates several other components for the purpose of offering services to others to create connections. A service profile is either Layer 2-centric (and built around ports) or Layer 3-centric (built around RIs).
Using these components in basic formats, a Layer 2 solution would look like this:
A Layer 3 solution, end-to-end, is strung together as follows:
Service level agreements
The ECX is supported by industry-standard SLAs, including:
- Service delivery: Once the ports are ordered and provisioned, they will be available on Cloud Exchange Portal (CXP) and APIs for service
- Availability service level agreement (SLA): 99.999% when provisioning redundant ports on redundant ECX chassis in a single metro
- Port Provisioning SLA: up to 10 business days
For more information on the enforcement and remuneration of SLAs, please visit our website or contact your account representative.
The following section provides details and options on each component, and what you may need to be ready for when configuring your network to interface with the ECX and the applications to which it connects.