Skip Headers
Oracle® Communications Unified Inventory Management L2 VPN Technology Pack Implementation Guide
Release 7.2.2

Part Number E36037-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

6 Layer 2 VPN Technology Pack Service Example

This chapter provides an example of using the L2 VPN Technology Pack to configure a port-based VPLS that uses border gateway protocol (BGP) for auto discovery and signaling.

This example is for a Full Mesh VPN with three sites.

Overview

A service such as this example comprises two services that you create in Oracle Communications Unified Inventory Management (UIM):

After the customer and transport services have been created, you link them together to complete the overall service. See "Linking the Customer View to the Service Provider View" for more information.

Assumptions

Inventory administration includes Data Networking Device and Data Networking Device Interface specifications for PE devices and CE devices.

For this example, we will assume that all the required PE and CE devices have been discovered and populated.

Note:

This example is based on the use of the default specifications and characteristics supplied with the technology pack. Extending the technology pack may influence how you configure the service.

Creating the Customer View

The customer view includes the CPE and sites that are to be connected by the service-provider Layer 2 VPN. The customer service is an instance of the Data Networking Service specification provided in the technology pack.

Creating the customer service involves the following steps:

Creating the Data Networking Service

The customer service is represented by an instance of the Data Networking Service specification. This specification has an accompanying configuration specification.

You create a configuration version based on this specification so that you can assign the customer sites that you create. Later, you will also assign a transport service to this service configuration. See "Linking the Customer View to the Service Provider View".

Complete the following steps to create and provision the customer service:

  • Create a service based on the Data Networking Service specification.

  • Specify a name (for example ACME Service) for the Data Networking service.

  • Add a configuration to the service. Only one specification (Data Networking Service Configuration) is available for this configuration.

Creating Customer Service Locations

The technology pack includes a location-type Place specification called serviceLocation. You create entities based on this specification for the locations of customer sites. These locations are then assigned to customer site configurations. For this example, you need a serviceLocation entity for each of the three customer sites.

Creating Customer Sites

You create Place entities for the customer sites where the CPE devices are located. The technology pack includes a Data Networking Site specification and an accompanying configuration specification.

You create three Place entities, one for each customer site. For each site:

  • Create a Place entity of type Site based on the Data Networking Site specification.

  • Specify a name; for example New York, Miami, and Los Angeles.

  • Add a configuration version. Only one configuration specification (Data Networking Site Configuration) is available. See "Provisioning the Customer Sites" for information about assigning resources to the site configuration.

Provisioning the Customer Sites

You provision the customer sites, New York, Miami, and Los Angeles, that you created by specifying their location, site termination, and CPE devices.

For each site configuration:

  • Add a Location Address configuration item and assign one of the service locations you created previously.

  • Add a Customer Premise Equipment configuration item. Assign a Data Networking Device entity to this item, selecting the logical device entity that is appropriate for each site.

  • Add a Site Termination configuration item. To this configuration item, add a Customer Premise Equipment Interface configuration item and assign a logical device interface that is provided by the logical device you selected as the CPE.

    Do not assign a resource to the Transport Termination configuration item at this time. You will assign this resource after you have created the transport service. See "Linking the Customer View to the Service Provider View" for more information.

  • In the Data Networking Service Configuration specification, under Sites, create three configuration items of type Data Networking Site.

  • For the first configuration item, assign New York; for the second configuration item, assign Miami; for the third configuration item, assign Los Angeles.

Creating the Service Provider View

The service provider view includes the creation of resources such as route distinguishers, route targets, VSIs, VPLS networks, terminations, and the Layer 2 VPLS to be assigned for the realization of an instance of this service.

Creating the Route Distinguishers

The route distinguisher is a six-byte number that is prepended to a standard IPv4 or IPv6 address to create a VPN-IPv4 or VPN-IPv6 address that is unique across the core network.

PEs use route distinguishers to ensure that traffic is routed to the proper CE. You must create a pool of route distinguishers so that they can be assigned to VSI configurations.

To create a route distinguisher, do the following:

  • Create an Inventory Group entity of type Route Distinguisher; for example, create a Route Distinguisher Type 0 group.

  • Specify a name for the route distinguisher inventory group; for example, RD 0 Group.

  • In the Initial Route Distinguisher Group Name list, specify the range of route distinguishers you want to create, such as 1:1-1:10.

    Custom network addresses based on the Route Distinguisher specification are created automatically. Their names correspond to the range you entered in the Initial Route Distinguisher Group Name list.

  • Verify whether the route distinguisher inventory group is created properly.

Note:

You must not edit the route distinguishers that are automatically generated because the inventory group, Route Distinguisher Type Group, controls these route distinguishers.

Creating Route Targets

The route target represents a route target scoped to a route target group. You must create a pool of route targets so that they can be assigned to VSI configurations.

To create a route target, do the following:

  • Create an Inventory Group entity of type Route Target; for example, create a Route Target Type 0 group.

  • Specify a name for the route target inventory group; for example, RT 0 Group.

  • In the Initial Route Target Group Name list, specify the range of route targets you want to create, such as 2:1 - 2:10.

    Custom network addresses based on the Route Target specification are created automatically. Their names correspond to the range you entered in the Initial Route Target Group Name list.

  • Verify whether the route target inventory group is created properly.

Note:

You must not edit the route targets that are automatically generated because the inventory group, Route Target Type Group, controls these route targets.

Creating VSIs

A VSI defines a VSI instance in the Layer 2 VPN.

You must create three VPLS VSI instances; for example VSI1, VSI2, and VSI3. Then, associate VSI1, VSI2, and VSI3 to PE1, PE2, and PE3 respectively. The following procedure describes the steps to create VSI1. You must repeat these steps for VSI2 and VSI3:

  • Create the Logical Device specification, VSI.

  • Specify a name for the VSI instance; for example, VSI1.

  • Select the route distinguisher inventory group that you created, such as RD 0 Group.

  • Associate the VSI to a PE. All VSIs would have a parent data networking device

    • Search for PE1 and associate.

  • Add a configuration to the VSI. Only one configuration specification is available, VPLS VSI Configuration.

  • UIM automatically assigns an unassigned route distinguisher from the group that you selected in the Preferred Route Distinguisher Group list. Auto Assignment occurs when the you choose the Auto-Assign menu item from the Related Pages menu.

Creating the VPN Network

A VPLS network represents a topology segment for a larger VPLS network. A VPLS network is either a Full Mesh topology or Hub and Spoke topology. Each VPLS network can be divided into a set of Full Mesh and Hub and Spoke network segments.

To create a VPLS network:

  • Create the Network specification, Layer 2 VPLS Network.

  • Specify a name for the Network specification; for example, Network1.

  • In the Preferred Route Target Group list, select the route target inventory group that you created, such as RT 0 Group.

  • Add a configuration to the Layer 2 VPN Network service. Two configuration specifications (VPLS-BGP Network and VPLS-LDP Network) are available. Because this is a BGP-based example, choose VPLS-BGP Network.

  • Add a route target and three VSI configuration items; for example VSI1, VSI2, and VSI3.

  • Set VPLS Topology to Full Mesh.

  • Select the first, second, and third VSI configuration items and assign objects VSI1, VSI2, and VSI3 respectively, and then set the Membership Type characteristic to Full Mesh Member.

  • Assign the unassigned route target from the group that you selected in the Preferred Route Target Group list.

Creating the Terminations

The Layer 2 VPN termination is the service-provider side of the attachment circuit. It can include configurations based on the Layer 2 VPLS Port Based Termination Configuration specification.

You must create three Terminations; for example Termination 1, Termination 2, and Termination 3. The following procedure describes the steps to create Termination 1. You must repeat these steps for Termination 2 and Termination 3:

  • Create a instance of the Place specification VPLS Switching Termination.

  • Specify a name for the Place specification; for example, Termination 1.

  • Add a VPLS Port-Based Switching Termination configuration to the termination.

  • Assign VSI1 object of the type VSI.

  • Add a Provider Edge Interface configuration item.

  • Assign a PE Interface object of type Data Networking Device Interface that represents the PE customer-facing interface.

    This example assumes that the PE and its interfaces are already inventoried and the PE interface and the VSI are on the same data networking device.

Creating the Layer 2 VPN Service

The Layer 2 VPN service includes VPLS networks and VPLS terminations.

You create an entity based on the Layer 2 VPN Service specification to represent the transport service. The specification is accompanied by the configuration specification, Layer 2 VPLS Configuration.

To create a service:

  • Create the Service specification, Layer 2 VPLS Service.

  • Specify a name for the Service specification; for example, ACME VPLS.

  • Add a configuration, Layer 2 VPLS Configuration, to the service.

  • Add a VPLS Service ID configuration item.

  • Under the VPN Transport Terminations folder, add three VPN Terminations configuration items.

  • Select the first, second, and third VPN Termination configuration items and assign objects Termination 1, Termination 2, and Termination 3 respectively.

  • Assign object Layer 2 VPLS Network.

  • Assign the VPLS Service ID.

  • Run state transition on the VPLS

  • Execute the validation rules for the VPLS

Until now, we have created the service provider view of the service request; we created a transport service instance and attached three terminations to that service. In each of the terminations, we captured information modeling the PE interface, which is customer facing. We also captured information about the termination VSI. The service is not complete until we update the customer view of the service, which references this instance.

Linking the Customer View to the Service Provider View

After the transport service is complete, you can return to the customer view to link the two. Linking the views includes:

When these two assignments have been made, the entire Layer 2 VPLS is complete.

Assigning the Transport Service

You assign a Layer 2 VPLS instance to the customer service configuration. This relationship defines the service that is used to enable connectivity between the three customer sites.

In the customer service configuration:

  • Add a Transport Service configuration item to the Transport Services configuration item. Assign the Layer 2 VPLS Service instance you created previously.

Assigning Terminations

You assign a Layer 2 VPLS termination to each customer site. This relationship defines which service-provider termination is used to connect the customer site to the Layer 2 VPLS network.

For each customer site:

  • In the site configuration, assign the appropriate Layer 2 VPLS termination to the Transport Termination configuration item. This configuration item was left undefined when you provisioned the site originally. See "Provisioning the Customer Sites" for more information.

Now we have created the customer view of the service as well as the service provider view of the service; we created a data networking service instance composed of sites, which represents what the end user considers as the service. We also created a transport service composed of networks and terminations, which represents what the service provider considers as the implementation of interconnecting the sites together through terminations.