Deploying, Monitoring, and Auditing Service Requests


To apply L2VPN, VPLS, or FlexUNI policies to network devices, you must deploy the service request. When you deploy a service request, Prime Fulfillment compares the device information in the Repository (the Prime Fulfillment database) with the current device configuration and generates a configlet. Additionally, you can perform various monitoring and auditing tasks on service requests. These common task that apply to all types of Prime Fulfillment service requests are covered in Chapter 47, "Managing Service Requests." See that chapter for more information on these tasks.

This chapter covers specific issues related to managing service request tasks for FlexUNI/EVC, L2VPN and VPLS services. It contains the following sections:

Pre-Deployment Changes

Pre-Deployment Changes

You can change the Dynamic Component Properties Library (DCPL) parameter actionTakenOnUNIVlanList before you deploy a FlexUNI/EVC, L2VPN, or VPLS service request. This will be necessary if the trunk allowed vlan list is not present on the User Network Interface (UNI).

To make this change, perform the following steps.


Step 1 Choose Administration > Control Center > Hosts.

Step 2 Choose the host that you want to change.

Step 3 Click Config.

The Host Configuration window appears.

Step 4 In the DCPL properties panel, choose Provisioning > Service > shared > actionTakenOnUNIVlanList.

The Attribute details appear.

Step 5 In the New Value drop-down list, choose one of the following:

prune to have Prime Fulfillment create the minimum VLAN list. This is the default.

abort to have Prime Fulfillment stop the L2VPN or VPLS service request provisioning with the error message: trunk allowed vlan list is absent on ERS UNI.

nochange to have Prime Fulfillment allow all VLANs.

Step 6 Click Set Property.