What are L3 VPN services?

L3 VPN services

NSP supports the creation of L3 VPN services. L3 VPN services utilize layer 3 VRF (VPN/virtual routing and forwarding) to routing tables for each customer utilizing the service. The customer peers with the service provider router and the two exchange routes, which are placed into a routing table specific to the customer. Multiprotocol BGP (MP-BGP) is required to utilize the service.

The RD and RT is auto-generated as per policy direction and the topology type selected. Parameters specified in the referenced template complete the service definition. Other parameters of the L3 VPN service are obtained from the specific templates referenced in the abstract API definition. The service definition in the abstract API, the detailed configuration in the service templates, and other network and tunnel parameters form the complete service definition, which is represented in the normalized model for L3 VPN. Specific configurations based on the devices are then constructed and deployed using NFM-P. L3 VPN services can use service tunnels that were not created using NSP.

The discovery and deployment of a hub-and-spoke L3 VPN service where two hubs are configured for redundancy is supported on NFM-P and MDM managed NEs. Redundancy is achieved by having the hubs advertise the same import/export routes with a unique route distinguisher. This feature is not supported on Wavence SM NEs.

NSP allows you to configure the properties on each hub-and-spoke or full mesh L3 VPN service site. You can also configure one or more SAPs on an L3 VPN service site.

Note: Before provisioning L3 VPN services using NSP, you must have MP-BGP configured and working between the PE nodes to support IP VPN. The Peer CE nodes must also be configured. Only one AS is supported per provider.

Use subject to agreed restrictions on disclosure and use.