Layer 3 Service Profile Details

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:

  1. Service Name: the service or company that is reached through this service. The 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. Profile Availability: the RIs that will be part of this profile so that the profile becomes available in those markets.

Optional services

The following optional services are available on the Service Profile component:

Limitations

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.

Note: 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.

Feedback

How are we doing?