Layer 2 Service Profile Details

Layer 2 service profiles are defined with ports that are either Dot1q or Q-in-Q enabled.

A user can have as few or as many ports as desired, and those ports can be in one or more markets. If at least one port is added to the profile from a specified market, the service will be available in that market, regardless of other factors or the amount of fill on that port.

Users can augment markets by adding ports to the market, but the buyerA buyer is a user who connects to an available service through ECX. A buyer can be an enterprise end customer of the seller service or an aggregator, managed service provider, network service provider or system integrator company that bundles its service offerings with ECX. never dictates or determines which port their traffic will be associated with—this is a provider responsibility.

Layer 2 Service Profile: Required Parameters

The Layer 2 service profile must create the following required parameters:

  1. Service Name - the service or company that is reached through this service. This name will appear to all users of the ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection in all relevant places

  2. Service Summary - a few words that describe the service and its benefits

  3. ConnectionConnection is a general term that refers to any solution that results in the ability to pass data from one point to another. Connections can be made with Layer 2 or Layer 3 technology, may involve several parts or components and can be created from the portal or with APIs in a variety of ways. Name - a discrete or specific product or service name for your interconnection needs. Provide the name that:

    • Aligns with your internal nomenclature and

    • Your customers will recognize

  4. Speed Selection - the rate limitedA rate limit is a bandwidth control that is placed on a connection or service that limits the amount of traffic that can be sent or received to an amount less than the physical size of the ports. This is also referred to as a policer or “policing” a service, and is typically implemented using a VLAN on a sub-interface. speeds you'd like to offer as available connections for a buyer. There are some default speeds, but they can be removed. The user can define up to 20 separate speeds. The system will indicate the Billing Tier for each speed. The Billing Tier information is presented to and paid for by the buyer, not the provider.

  1. Profile Availability - the ports you wish to be part of this profile so it becomes available in those markets

    • Conditional - users can name a region for the market or ports that aligns with the provider’s nomenclature, such as Americas West or EU-HR

    • Conditional - users should elect whether they wish to receive remote connections from markets outside of those defined by port selection

    • Conditional - users might indicate that some ports within a market are In Trial Testing

Note: This designation does not prevent a buyer from requesting a connection to the service, but displays a warning message to the user that the connection might not work. The provider reserves the right to reject or delete the request.

Optional Services

The following optional services are available on the Layer 2 Service Profile:

  • Redundancy Requirement - does the buyer need to create redundant connections to your service? If redundancy is available but not required, users can still choose to build a second connection.

  • Enhanced Dot1q to QinQ Translation Support - users can define names for one or more services reachable through this profile. More information about how this works is included in the section on configuring to sell Layer 2 services

  • Additional Fields to Capture from a Buyer - a series of defined metadata can be selected for capture, and the ECX Fabric portal will then ask the buyer to enter this information. The entered data is passed to the provider as part of the connection record but is not otherwise used for configuration or other needs by the ECX Fabric platform

  • Notifications - indicate who should be notified via email in the event of changes to the profile state or parameters, connection requests, and thresholds for bandwidth. See more about this in the section about configuring to sell Layer 2 services

  • Oversubscription - Customers who chose API Integration can select option fields to oversubscribe their Equinix managed ports. This allows ports to accept subscriptions higher than the actual port capacity to maximize utility. There is no charge for the over-subscription feature. Ports can be oversubscribed up to 20x the port capacity.