Layer 3 service profiles are defined with routing instances (RIs). A user can have as few or as many RIs as needed in the profile. The RIs may be in the same or other markets, and may be primary or secondary within the rules of the RI itself.
Because an RI is present in a specific market, it defines where the service will be available for subscribers. Therefore, when a user adds three RIs in Atlanta, two in Chicago, and one in London, the service will become available as a single line item in those three markets—the system will not list RIs to a subscriber because a subscriber receives routes from all RIs present in that market.
Layer 3 Service Profile: Required Parameters
The Layer 3 service profile must create the following required parameters:
- Service Name: the service or company that is reached through this service. This name will appear to all users of the ECX in all relevant places.
- Service Summary: a few words that describe the service and its benefits.
- Profile Availability: the RIs that will be part of this profile so that the profile becomes available in those markets.
- Conditional: users may indicate that some RIs within a market are “In Trial Testing.” The In Trial Testing status 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. The provider reserves the right to reject or delete the request.
- Conditional: users should elect whether they wish to receive remote connections from markets outside of those defined by port selection
The following optional services are available on the Service Profile component:
- Equinix-Only Routes: a provider may specify the following:
- The provider will only receive a pre-determined and verified IP address block from the Equinix range.
- The provider will not accept public routes from the subscriber’s address space. The provider must select the most specific routes they are capable of accepting. This may result in additional charges to a subscriber if they are required to NAT or allocate addresses. This will result in some traffic being NATted, which means this feature should only be used if your customers only access applications that operate properly with NAT
- Subscriber-Side Rate Limits: this service adds the ability for a provider to impose pre-determined rate limits on a subscriber. The provider selects a range of speed options that the subscriber will be obligated to pick from, or the provider can opt to allow subscribers to enter their own speed, as long as one is entered.
- We recommend that rate limited services be built using a Layer 2 service profile type to allow the subscriber maximum flexibility.
- The subscriber will be required to dedicate a connector to this service, causing additional charges and the loss of some routing function control.
- BGP Community Tags: if community tags are available, add a hyperlink for users to learn more and include the provider’s rules for usage.
- Optional Fields: Providers can add in optional text/number fields of information that they can request from customers. This allows the option to ask customers for more information, specified by the provider. You can select whether these fields are optional or required, and show up as "Additional Details Requested by the Provider".
When “Equinix-Only Routes” service is added, all RIs that are part of the profile will have additional configuration added, and the RIs will become ineligible for use with other subscriptions other than those inbound to this profile. The additional configuration can be deleted upon removal of the RI from the profile, assuming there are no existing subscriptions actively associated with it.
When Subscriber-Side Rate Limits are added to a profile, the subscriber must select from available speeds and apply them as a policer to a connector and dedicate that connector. The provider does not have any specified rate limits on their side of the configuration, resulting in a risk of dropped packets. We advise that providers select Layer 2 services if they expect a rate limit on ingest from either direction of the traffic.
When a user removes an RI from a service profile, that service is also withdrawn from any markets that RI was present in, if it was the only RI in that market part of the active profile. If the user removes the last remaining RI for that profile, the profile will go into an inactive state, as it no longer has any routes to advertise to subscribers. The user can add an RI back to the profile to reinstate it to active service in the related market.