Configure a Layer 3 Service Profile
A Layer 3 service profile is created by combining routing instances (RI) into a service profile and defining its characteristics and business rules.
Basic Layer 3 Service Profile Work-flow
You can support redundancy by having a second and redundant RI that advertises the same routes as the primary, and include BOTH in your service profile, per metro. When this is in your service profile, a buyer who subscribes to your service will continue to receive routes if one of your devices fail, even if they don't have redundancy.
You can add, edit, or remove ports and RIs to your profile, as well as other activities throughout the time of your service. You can use connectors to add many ports to one or more RIs, swap between or migrate services from one device to another without taking down the RI, and add or remove RIs from your service profile.
Warning: This could have consequences to existing customers if the advertised routes change over the life cycle.
Unlike Layer 2 service profiles, it is not necessary to approve each subscription as it's created by the buyer. As soon as the pre-requisites have been met, the subscription goes live and route advertisement begins.
Users can enable their profile to receive remote subscriptions. However, the provider must be capable of accepting routes from all interconnected metros, which could significantly increase the size of the route table. This includes the Equinix public routes, which amount to a /24 per metro.
Example: Service profile is available in metros 2 and 4 with buyers in metros 1-4. Each metro has a block of IP addresses used for NAP, reservation and other purposes by Equinix. Provider must allow advertisement from all in order to received remote connections.
