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 they 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 buyer never dictates or determines which port their traffic will be associated with—this is a provider responsibility. See the section later in this document about creating Layer 2 service profiles and managing their availability.
The Layer 2 service profile must create the following required parameters:
- Service Name: indicate the service or company that is reached through this service: it is the name that will appear to all users of the ECX in all relevant places
- Service Summary: describe the service and its benefits in a few short words
- Connection Name: if you have a discrete or specific product or service name for your interconnection needs, provide the name here that aligns with your internal nomenclature and that your customers will recognize
- Speed Selection: indicate the rate limited speeds you wish to offer as available connections for a buyer. There are some defaults but they can be removed, and the user can define up to 20 separate speeds. The system will indicate which Billing Tier each speed will be in, as presented to and paid for by the buyer, not the provider
- Profile Availability: select 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 may indicate that some ports within a market are “In Trial Testing”
Note: this does not prevent a buyer from requesting a connection to the service, but will display a warning message to the user that the connection may not work and the provider reserves the right to reject or delete the request.
The following optional services are available on the Layer 2 Service Profile:
- Redundancy Requirement: indicate if you require the buyer when requesting to create redundant connections to your service
Note: if you make redundancy available but not required, users may still choose to build a second connection
- Enhanced Dot1q to QinQ Translation Support: allows the user to 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 pre-defined metadata can be selected for capture, and the ECX 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 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