Create a Service Profile for a Layer 2 Service
To be discoverable by others in ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection Portal, you'll need to define and build your service profiles for connectivity to your services. A service profile is designed to help ease a 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.'s provisioning of services through the cloud exchange. You create a profile for each service that you offer.
Service Profile Creation Workflow
First, you must have ports provisioned, and shown on the portal under Inventory. Then, from the My Company page, click Create a Service Profile. To create a service profile, from the Layer 2 Service section, click Create a Layer 2 Service.
Follow the steps to define custom configuration options for public and private connectivity to your service. The chart tracks your progress as you advance through the service profile creation process. As you complete each section, select Next to proceed to the next window.
The main steps are:
- Service details—Select the basic service profile details
- Optional details—Add any optional network details
- Locations available—Select the locations where you offer your services
- Speeds—Add the connection speeds available to customers
- Review—Check your inputs and preview the new service profile
In the Basic Information section, enter a name for your service profile, and if applicable, add a brief description of your service.
For the Notifications section, enter the email address of the person who receives email notifications about this service profile. Click Add Another Email to add any additional email address.
You can click an option to expand the block. Each section explains the purpose. Follow the instructions on the page to complete the optional fields as required.
This window has a detailed list of optional network details for you to select. Depending on the new service profile requirement, you can set any number of optional network details, including:
|Redundancy||Specify if your connections require redundancy. If yes, then users need to create a secondary redundant connection|
|Enhance .1q to QinQ translation support||Either you require a subscriber to add a C-tag, or provide names of the applications that you offer|
|Remote connection||Allow customers to reach a location through a non-local (remote) connection|
|Use API integration for this service||Use API integration to complete connection provisioning|
|Custom name for connection||If your company uses a different name to refer to connections, enter the name in the text field|
|Custom fields for your service||Add up to 10 custom fields that you might want to use to gather information|
|Private connection||Select the checkbox if this service profile is private|
|Provisioned Bandwidth Threshold Alert||You can set an alert for when a percentage of your profile has sold. This alert notifies you to add more ports or to create a new service profile|
|Authentication KeyThe Authentication Key is a unique identifier authorizing Equinix to provision a connection towards the CSP. This Key usually contains alphanumeric characters. Note: to Equinix, an Authentication Key is a generic term and is not encrypted on ECX. Cloud Service Providers might use a different name to refer to the same key. For example: Azure ExpressRoute calls the authorization key the “service key” while AWS calls it the “account ID.” for QinQ Ports||Allows customers with .1q ports to group connections when connecting to QinQ ports|
Authentication Key Service for QinQ Service Providers
Typically, QinQ service providers must accept a connection for each c-tag when the originating port is configured for 802.1q encapsulation. Alternatively, you can choose to accept only the first connection request by enabling Authentication Key service. Using this service, QinQ destinations will accept the first connection in a service group and all subsequent requests (c-tags) with the same authentication key will be automatically associated to the same s-tag or service group and provisioned immediately. This capability can be enabled by selecting this option in the service profile for QinQ port service providers.
Subscribers will be able to either generate a new authentication key for a particular connection, creating a new service group, or use a preexisting authentication key in order to designate which connections belong within the same service group.
Additionally, service providers can specify a custom name for the Authentication key. The new custom name will appear instead of authentication key where applicable.
Some restrictions apply:
- Only available for QinQ ports
- Destination or CSP must not be using API Integration
- After the first connection in a service group is created, any subsequent connections associated with that same group cannot have a bandwidth tier/speed larger than the first connection
- All connections within a service group must have the same origin and destination
On this window, you select the locations where you offer your service. There needs to be at least one active port present in each location.
From the regions and locations where you have ECX Fabric ports turned up, select the ports you want to assign to the service. Drill down to the required port by first selecting each region and location you want, and the available ports display.
From here, you can select and group the ports. You group the ports per encapsulation, so you can only select those ports with either QinQ or Dot1Q.
When setting your service regions, you have two options:
- API-enabled—If the service profile is API-enabled (such as AWS or Azure), then instead of being able to customize or create region names, you see a drop-down selection of pre-assigned region names. Once you highlight each port you want in the group, then select the designated region name from the drop-down and click Apply.
- Non-API enabled—For other service profiles, you can select from the list of designated region names or select assign customized names to the regions. Once you highlight each port you want in the group, select the Enable Custom Service Regions checkbox (Azure allows you to input regions). In the field that displays, enter the customized zone name and click Apply. Remember that if you are creating custom regions, every port selected in the service profile needs to be assigned to a region.
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. speeds are billed by billing tiers, and you set the connection speed options that your customers can select when creating a connection request. To do this, specify the connection speeds you want to offer the customer. For each option, specify the unique speed, units and billing tier—you can add a maximum of 20 speed options. If you specify a speed greater than the port connection speed, an error message displays.
If you want, you can select the checkbox option that allows your customers to enter a custom speed. The custom speeds map directly to the billing tiers specified in the service profile.
Once you have added all the selections and settings, you can preview the service profile details to check that everything is correct before submitting it to Equinix. A service profile preview card displays showing the highlights of the new profile, as well as an overview of the details based on your specifications.
When you are satisfied with the details, click Create Service Profile.
A success message indicates that your service profile is being review by an Equinix Admin. The new service profile displays on your “My Company” page. You receive an email notification when the profile is approved.