Cisco Prime Fulfillment User Guide 6.2

Managing L2VPN and Carrier Ethernet Services

This chapter describes how to use Prime Fulfillment policies and service requests to manage various L2VPN and Carrier Ethernet services. It contains the following sections:

•Getting Started with L2VPN Services

•Setting Up the Prime Fulfillment Services

•Creating an EVC Ethernet Policy

•Managing an EVC Ethernet Service Request

•Creating an EVC ATM-Ethernet Interworking Policy

•Managing an EVC ATM-Ethernet Interworking Service Request

•Creating an L2VPN Policy

•Managing an L2VPN Service Request

•Creating a VPLS Policy

•Managing a VPLS Service Request

•Deploying, Monitoring, and Auditing Service Requests

•Using Autodiscovery for L2 Services

•Provisioning VPLS Autodiscovery on Devices using EVC Service Requests

•Setting Up VLAN Translation for L2VPN ERS (EVPL) Services

•Sample Configlets

Getting Started with L2VPN Services

This section provides a road map to help you get started using the L2VPN component in Cisco Prime Fulfillment 6.2. It contains the following sections:

•Overview

•Installing Prime Fulfillment and Configuring the Network

•Configuring the Network to Support Layer 2 Services

•Setting Up Basic Prime Fulfillment Services

•Working with EVC, L2VPN, and VPLS Policies and Service Requests

•A Note on Terminology Conventions

Overview

Before you can use the L2VPN component to provision Layer 2 services, you must complete several installation and configuration steps, as outlined in this section. In addition, you should be familiar with basic concepts for Prime Fulfillment and L2VPN services. The following subsections provide a summary of the key tasks you must accomplish to be able to provision L2VPN, VPLS and EVC services using Prime Fulfillment. You can use the information in this section as a checklist. Where appropriate, references to other sections in this guide or to other guides in the Prime Fulfillment documentation set are provided. See the referenced documentation for more detailed information. After the basic installation and configuration steps are completed for both Prime Fulfillment and the L2VPN component, see the subsequent sections to create and provision L2VPN, VPLS and EVC services.

Installing Prime Fulfillment and Configuring the Network

Before you can use the L2VPN module in Prime Fulfillment to provision L2VPN or VPLS services, you must first install Prime Fulfillment and do the basic network configuration required to support Prime Fulfillment. Details on these steps are provided in Chapter 2 "Before Setting Up Prime Fulfillment." See that chapter for information about Prime Fulfillment installation and general network configuration requirements.

Note To use the L2VPN component within Prime Fulfillment, you must purchase and activate the L2VPN license.

Configuring the Network to Support Layer 2 Services

In addition to basic network configuration required for Prime Fulfillment, you must perform the following network configuration steps to support Layer 2 services. Information on doing these steps is not provided in the Prime Fulfillment documentation. See the documentation for your devices for information on how to perform these steps.

1. Enable MPLS on the core-facing interfaces of the N-PE devices attached to the provider core.

2. Set up /32 loopback addresses on N-PE devices. These loopback addresses should be the termination of the LDP connection(s).

3. Set all Layer 2 devices (switches) to VTP transparent mode. This ensures that none of the switches will operate as VLAN servers and will prevent VLAN information from automatically propagating through the network.

Setting Up Basic Prime Fulfillment Services

After the basic network configuration tasks are completed to support Prime Fulfillment and L2 services, you use Prime Fulfillment to define elements in the Prime Fulfillment repository, such as providers and regions, customers and sites, devices, VLAN and VC pools, NPCs, and other resources that are necessary to provision L2 services. Detailed steps to perform general Prime Fulfillment tasks are covered in Chapter 2 "Before Setting Up Prime Fulfillment." You can also find a summary of some important Prime Fulfillment set up tasks in Setting Up the Prime Fulfillment Services. The information below is a checklist of basic Prime Fulfillment services you must set up before provisioning L2 services.

Setting Up Providers, Customers, and Devices

Perform the following steps to set up providers, customers, and devices in the Prime Fulfillment repository. These are global resources that can be used by all Prime Fulfillment services.

1. Set up service providers and regions. The region is important because a single provider could have multiple networks. The region is used as a further level of differentiation to allow for such circumstances. To create a provider and a region, see Setting Up Resources. See also Defining a Service Provider and Its Regions.

2. Set up customers and customer sites. A customer is a requestor of a VPN service from an ISP. Each customer can own many customer sites. Each customer site belongs to one and only one Customer and can own many CEs. For detailed steps to create customers and sites, see Setting Up Resources. See also Defining Customers and Their Sites.

3. Import or add raw devices. Every network element that Prime Fulfillment manages must be defined as a device in the Prime Fulfillment repository. An element is any device from which Prime Fulfillment can collect information. In most cases, devices are Cisco IOS routers and switches. You can set up devices in Prime Fulfillment manually, through autodiscovery, or through importing device configuration files. For detailed steps for importing, adding, and collecting configurations for devices, see "Inventory - Discovery." See also Using Autodiscovery for L2 Services.

4. Assign devices roles as PE or CE. After devices are created in Prime Fulfillment, you must define them as customer (CE) or provider (PE) devices. You do this by editing the device attributes on individual devices or in batch editing through the Prime Fulfillment inventory manager. To set device attributes, see Setting Up Devices and Device Groups.

Setting Up the N-PE Loopback Address

Within Prime Fulfillment, you must set the loopback address on the N-PE device(s). For details about this procedure, see Setting Up the N-PE Loopback Address.

Setting Up Prime Fulfillment Resources for L2VPN and VPLS Services

Some Prime Fulfillment resources, such as access domains, VLAN pools, and VC pools are set up to support Prime Fulfillment L2VPN and VPLS services only. To set up these resources, perform the following steps.

1. Create access domain(s). For L2VPN and VPLS, you create an access domain if you provision an Ethernet-based service and want Prime Fulfillment to automatically assign a VLAN for the link from the VLAN pool. For each Layer 2 access domain, you need a corresponding access domain object in Prime Fulfillment. During creation, you select all the N-PE devices that are associated with this domain. Later, one VLAN pool can be created for an access domain. For detailed steps to create access domains, see Setting Up Resources. See also Creating Access Domains.

2. Create VLAN pool(s). A VLAN pool is created for each access domain. For L2VPN and VPLS, you create a VLAN pool so that Prime Fulfillment can assign a VLAN to the links. VLAN ID pools are defined with a starting value and a size. For detailed steps to create VLAN pools, see Setting Up Resources. See also Creating VLAN Pools.

3. Create VC pool(s).VC ID pools are defined with a starting value and a size of the VC ID pool. A given VC ID pool is not attached to any inventory object (a provider or customer). Create one VC ID pool per network. For detailed steps to create VC pools, see Setting Up Resources. See also Creating a VC ID Pool.

Setting Up NPCs

Before creating an L2VPN or VPLS service request, you must predefine the physical links between CEs and PEs or between U-PEs and N-PEs. The Named Physical Circuit (NPC) represents a link going through a group of physical ports. Thus, more than one logical link can be provisioned on the same NPC. Therefore, the NPC is defined once but used by several L2VPN or VPLS service requests. For detailed steps to create NPCs, see Setting Up Logical Inventory. See also Creating Named Physical Circuits.

Setting Up VPNs

You must define VPNs before provisioning L2VPN or VPLS services. In L2VPN, one VPN can be shared by different service types. In VPLS, one VPN is required for each VPLS instance. To define VPNs, see Setting Up Logical Inventory. See also Defining VPNs.

Working with EVC, L2VPN, and VPLS Policies and Service Requests

After you have set up providers, customers, devices, and resources in Prime Fulfillment, you are ready to create EVC, L2VPN, or VPLS policies, provision service requests (SRs), and deploy the services. After the service requests are deployed you can monitor, audit and run reports on them. All of these tasks are covered in this guide. To accomplish these tasks, perform the following steps.

1. Review overview information about L2 services concepts. See the chapter "Prime Fulfillment Layer 2 VPN Concepts" in the Cisco Prime Fulfillment Theory of Operations Guide 6.2.

2. Set up an EVC, L2VPN, or VPLS policy. See the appropriate section, depending on the type of policy you want to create:

–Creating an EVC Ethernet Policy

–Creating an EVC ATM-Ethernet Interworking Policy

–Creating an L2VPN Policy

–Creating a VPLS Policy

3. Provision the EVC, L2VPN, or VPLS service request. See the appropriate section, depending on the type service request you want to provision:

–Managing an EVC Ethernet Service Request

–Managing an EVC ATM-Ethernet Interworking Service Request

–Managing an L2VPN Service Request

–Managing a VPLS Service Request

4. Deploy the service request. See Deploying, Monitoring, and Auditing Service Requests.

5. Check the status of deployed services. You can use one or more of the following methods:

–Monitor service requests. See Deploying, Monitoring, and Auditing Service Requests.

–Audit service requests. See Deploying, Monitoring, and Auditing Service Requests.

–Run L2 and VPLS reports. See Generating L2 and VPLS Reports.

A Note on Terminology Conventions

The Prime Fulfillment GUI and this chapter of the user guide use specific naming conventions for Ethernet services. These align closely with the early MEF conventions. This is expected to be updated in future releases of to conform with current MEF conventions. For reference, the equivalent terms used by the MEF forum are summarized in Table 3-1.

See the chapter "Prime Fulfillment Layer 2 VPN Concepts," in the Cisco Prime Fulfillment Theory of Operations Guide 6.2, for more information on terminology conventions and how these align with underlying network technologies.

Setting Up the Prime Fulfillment Services

To create L2VPN, VPLS, and EVC policies and service requests, you must first define the service-related elements, such as target devices, VPNs, and network links. Normally, you create these elements once.

This section contains the basic steps to set up the Cisco Prime Fulfillment 6.2 resources for L2VPN services. It contains the following sections:

•Creating Target Devices and Assigning Roles (N-PE or U-PE)

•Configuring Device Settings to Support Prime Fulfillment

•Defining a Service Provider and Its Regions

•Defining Customers and Their Sites

•Defining VPNs

•Creating Access Domains

•Creating VLAN Pools

•Creating Outer VLAN Pools

•Creating a VC ID Pool

•Creating Named Physical Circuits

•Creating and Modifying Pseudowire Classes

•Defining L2VPN Group Names for IOS XR Devices

Note This section presents high-level information on Prime Fulfillment services that are relevant to L2VPN. For more detailed information on setting up these and other basic Prime Fulfillment services, see Chapter 2 "Before Setting Up Prime Fulfillment."

Creating Target Devices and Assigning Roles (N-PE or U-PE)

Every network element that Prime Fulfillment manages must be defined as a device in the system. An element is any device from which Prime Fulfillment can collect information. In most cases, devices are Cisco IOS routers that function as N-PE, U-PE, or P. For detailed steps to create devices, see Setting Up Devices and Device Groups.

Configuring Device Settings to Support Prime Fulfillment

Two device settings must be configured to support the use of Prime Fulfillment in the network:

•Switches in the network must be operating in VTP transparent mode.

•Loopback addresses must be set on N-PE devices.

Note These are the two minimum device settings required for Prime Fulfillment to function properly in the network. You must, of course, perform other device configuration steps for the proper functioning of the devices in the network.

Configuring Switches in VTP Transparent Mode

For security reasons, Prime Fulfillment requires VTPs to be configured in transparent mode on all the switches involved in ERS or EWS services before provisioning L2VPN service requests. To set the VTP mode, enter the following Cisco IOS commands:

Switch# configure terminal

Switch(config)# vtp mode transparent

Enter the following Cisco IOS command to verify that the VTP mode has changed to transparent:

Switch# Show vtp status

Setting the Loopback Addresses on N-PE Devices

The loopback address for the N-PE has to be properly configured for an Any Transport over MPLS (AToMPLS) connection. The IP address specified in the loopback interface must be reachable from the remote pairing PE. The label distribution protocol (LDP) tunnels are established between the two loopback interfaces of the PE pair. To set the PE loopback address, perform the following steps.

Step 1 Choose Inventory > Resources > Provider Devices.

The Provider Devices window appears.

Step 2 Choose a specific PE device and click the Edit button.

The Edit Provider Device window appears.

To prevent a wrong loopback address being entered into the system, the Loopback IP Address field on the GUI is read-only.

Step 3 Choose the loopback address by clicking the Select button (in the Loopback IP Address attribute).

The Select Device Interface window appears.

Step 4 Choose one of the loopback addresses listed in the Interface Name column.

This step ensures that you choose only a valid loopback address defined on the device.

Step 5 To further narrow the search, you can check the LDPTermination Only check box and click the Select button.

This limits the list to the LDP-terminating loopback interface(s).

Setting Up Devices for IOS XR Support

L2VPN in Cisco Prime Fulfillment 6.2, supports devices running Cisco's IOS XR software. IOS XR, a new member of the Cisco IOS family, is a unique self-healing and self-defending operating system designed for always-on operation while scaling system capacity up to 92Tbps. In L2VPN, IOS XR is only supported on Cisco XR12000 and CRS-1 series routers functioning as network provider edge (N-PE) devices.

In L2VPN, the following E-line services are supported for IOS XR:

•Point-to-point ERS with or without a CE.

•Point-to-point EWS with or without a CE.

The following L2VPN features are not supported for IOS XR:

•Standard UNI port on an N-PE running IOS XR. (The attribute Standard UNI Port in the Link Attributes window is disabled when the UNI is on an N-PE device running IOS XR.)

•SVI interfaces on N-PEs running IOS XR. (The attribute N-PE Pseudo-wire On SVI in the Link Attributes window is disabled for IOS XR devices.)

•Pseudowire tunnel selection. (The attribute PW Tunnel Selection in the Link Attributes window is disabled for IOS XR devices.)

•EWS UNI (dot1q tunnel or Q-in-Q) on an N-PE running IOS XR.

•Frame Relay/ATM and VPLS services.

To enable IOS XR support in L2VPN, perform the following steps.

Step 1 Set the DCPL property Provisioning\Service\l2vpn\platform\CISCO_ROUTER\IosXRConfigType to XML.

Possible values are CLI, CLI_XML, and XML (the default).

Step 2 Create the device in Prime Fulfillment as an IOS XR device, as follows:

a. Create the Cisco device by choosing Inventory > Devices > Create Cisco Devcie.

b. Choose Cisco Device in the drop-down list.

The Create Cisco Router window appears.

c. Set the OS attribute, located under Device and Configuration Access Information, to IOS_XR.

Note For additional information on setting DCPL properties and creating Cisco devices, see "Property Settings."

Step 3 Create and deploy L2VPN service requests, following the procedures in this guide.

Sample configlets for IOS XR devices are provided in Sample Configlets.

Defining a Service Provider and Its Regions

You must define the service provider administrative domain before provisioning L2VPN. The provider administrative domain is the administrative domain of an ISP with one BGP autonomous system (AS) number. The network owned by the provider administrative domain is called the backbone network. If an ISP has two AS numbers, you must define it as two provider administrative domains. Each provider administrative domain can own many region objects.

For detailed steps to define the provider administrative domain, see Setting Up Resources.

Defining Customers and Their Sites

You must define customers and their sites before provisioning L2VPN. A customer is a requestor of a VPN service from an ISP. Each customer can own many customer sites. Each customer site belongs to one and only one Customer and can own many CPEs. For detailed steps to create customers, see Setting Up Resources.

Defining VPNs

You must define VPNs before provisioning L2VPN or VPLS. In L2VPN, one VPN can be shared by different service types. In VPLS, one VPN is required for each VPLS instance. For detailed steps to create VPNs, see Setting Up Logical Inventory.

Note The VPN in L2VPN is only a name used to group all the L2VPN links. It has no intrinsic meaning as it does for MPLS VPN.

Creating Access Domains

For L2VPN and VPLS, you create an Access Domain if you provision an Ethernet-based service and want Prime Fulfillment to automatically assign a VLAN for the link from the VLAN pool.

For each Layer 2 access domain, you need a corresponding Access Domain object in Prime Fulfillment. During creation, you select all the N-PE devices that are associated with this domain. Later, one VLAN pool can be created for an Access Domain. This is how N-PEs are automatically assigned a VLAN.

Before you begin, be sure that you:

•Know the name of the access domain that you want to create.

•Have created a service provider to associate with the new access domain.

•Have created a provider region associated with your provider and PE devices.

•Have created PE devices to associate with the new access domain.

•Know the starting value and size of each VLAN to associate with the new access domain.

•Know which VLAN will serve as the management VLAN.

For detailed steps on creating Access Domains, see Setting Up Resources.

Creating VLAN Pools

For L2VPN and VPLS, you create a VLAN pool so that Prime Fulfillment can assign a VLAN to the links. VLAN ID pools are defined with a starting value and a size of the VLAN pool. A VLAN pool can be attached to an access domain. During the deployment of an Ethernet service, VLAN IDs can be autoallocated from the access domain's pre-existing VLAN pools. When you deploy a new service, Prime Fulfillment changes the status of the VLAN pool from Available to Allocated. Autoallocation gives the service provider tighter control of VLAN ID allocation.

You can also allocate VLAN IDs manually.

Note When you are setting a manual VLAN ID on a Prime Fulfillment service, Prime Fulfillment warns you if the VLAN ID is outside the valid range of the defined VLAN pool. If so, Prime Fulfillment does not include the manually defined VLAN ID in the VLAN pool. We recommend that you preset the range of the VLAN pool to include the range of any VLAN IDs that you manually assign.

Create one VLAN pool per access domain. Within that VLAN pool, you can define multiple ranges.

Before you begin, be sure that you:

•Know each VLAN pool start number.

•Know each VLAN pool size.

•Have created an access domain for the VLAN pool.

•Know the name of the access domain to which each VLAN pool will be allocated.

To have Prime Fulfillment automatically assign a VLAN to the links, perform the following steps.

Step 1 Choose Service Design > Resources > Resource Pools.

The Resource Pools window appears.

Step 2 Choose VLAN from the Pool Type drop-down list.

Step 3 Click Create.

The Create New VLAN Resource Pool window appears.

Step 4 Enter a VLAN Pool Start number.

Step 5 Enter a VLAN Pool Size number.

Step 6 If the correct access domain is not showing in the Access Domain field, click Select to the right of Access Domain field.

The Select Access Domain dialog box appears.

If the correct access domain is showing, continue with Step 9.

a. Choose an Access Domain Name by clicking the button in the Select column to the left of that Access Domain.

b. Click Select. The updated Create New VLAN Resource Pool window appears.

Step 7 Click Save.

The updated VLAN Resource Pool window appears.

Note The pool name is created automatically, using a combination of the provider name and the access domain name.

Note The Status field reads "Allocated" if you already filled in the Reserved VLANs information when you created the access domain. If you did not fill in the Reserved VLANs information when you created the access domain, the Status field reads "Available." To allocate a VLAN pool, you must fill in the corresponding VLAN information by editing the access domain. (See Creating Access Domains.) The VLAN pool status automatically sets to "Allocated" on the Resource Pools window when you save your work.

Step 8 Repeat this procedure for each range you want to define within the VLAN.

Creating Outer VLAN Pools

An outer VLAN pool is used in conjunction with the AutoPick Outer VLAN attribute in EVC Ethernet and EVC ATM-Etherner policies. For instructions on how to set up outer VLAN pools, see the section Resource Pools.

Creating a VC ID Pool

VC ID pools are defined with a starting value and a size of the VC ID pool. A given VC ID pool is not attached to any inventory object (a provider or customer). During deployment of an L2VPN or VPLS service, the VC ID can be autoallocated from the same VC ID pool or you can set it manually.

Note When you are setting a manual VC ID on a Prime Fulfillment service, Prime Fulfillment warns you if the VC ID is outside the valid range of the defined VC ID pool. If so, Prime Fulfillment does not include the manually defined VC ID in the VC ID pool. We recommend that you preset the range of the VC ID pool to include the range of any VC IDs that you manually assign.

Create one VC ID pool per network.

In a VPLS instance, all N-PE routers use the same VC ID for establishing emulated Virtual Circuits (VCs). The VC-ID is also called the VPN ID in the context of the VPLS VPN. (Multiple attachment circuits must be joined by the provider core in a VPLS instance. The provider core must simulate a virtual bridge that connects the multiple attachment circuits. To simulate this virtual bridge, all N-PE routers participating in a VPLS instance form emulated VCs among them.)

Note VC ID is a 32-bit unique identifier that identifies a circuit/port.

Before you begin, be sure that you have the following information for each VC ID pool you must create:

•The VC Pool start number

•The VC Pool size

For all L2VPN and VPLS services, perform the following steps.

Step 1 Choose Service Design > Resources > Resource Pools.

The Resource Pools window appears.

Step 2 Choose VC ID from the Pool Type drop-down list.

Because this pool is a global pool, it is not associated with any other object.

Step 3 Click Create.

The Create New VC ID Resource Pool window appears.

Step 4 Enter a VC pool start number.

Step 5 Enter a VC pool size number.

Step 6 Click Save.

The updated Resource Pools window appears.

Creating Named Physical Circuits

Before creating an L2VPN or VPLS service request, you must predefine the physical links between CEs and PEs. The Named Physical Circuit (NPC) represents a link going through a group of physical ports. Thus, more than one logical link can be provisioned on the same NPC; therefore, the NPC is defined once but used during several L2VPN or VPLS service request creations.

There are two ways to create the NPC links:

•Through an NPC GUI editor. For details on how to do this, see Creating NPCs Through the NPC GUI Editor.

•Through the autodiscovery process. For details on how to do this, see Creating NPC Links Through the Autodiscovery Process.

An NPC definition must observe the following creation rules:

•An NPC must begin with a CE or an up-link of the device where UNI resides or a Ring.

•An NPC must end with an N-PE or a ring that ends in an N-PE.

If you are inserting NPC information for a link between a CE and UNI, you enter the information as:

•Source Device is the CE device.

•Source Interface is the CE port connecting to UNI.

•Destination Device is the UNI box.

•Destination interface is the UNI port.

If you are inserting NPC information for a CE not present case, you enter the information as:

•Source Device is the UNI box.

•Source Interface is the UP-LINK port, not the UNI port, on the UNI box connecting to the N-PE or another U-PE or PE-AGG.

•Destination Device is the U-PE, PE-AGG, or N-PE.

•Destination Interface is the DOWN-LINK port connecting to the N-PE or another U-PE or PE-AGG.

If you have a single N-PE and no CE (no U-PE and no CE), you do not have to create an NPC since there is no physical link that needs to be presented.

If an NPC involves two or more links (three or more devices), for example, it connects ence11, enpe1, and enpe12, you can construct this NPC as follows:

•Build the link that connects two ends: mlce1 and mlpe4.

•Insert a device (enpe12) to the link you just made.

Creating NPCs Through the NPC GUI Editor

To create NPCs through the NPC GUI editor, perform the following steps.

Step 1 Choose Inventory > Logical Inventory > Named Physical Circuits.

The Named Physical Circuits window appears.

To create a new NPC, you choose a CE as the beginning of the link and a N-PE as the end. If more than two devices are in a link, you can add or insert more devices (or a ring) to the NPC.

Note The new device or ring added is always placed after the device selected, while a new device or ring inserted is placed before the device selected.

Each line on the Point-to-Point Editor represents a physical link. Each physical link has five attributes:

•Source Device

•Source Interface

•Destination Device (must be an N-PE)

•Destination Interface

•Ring

Note Before adding or inserting a ring in an NPC, you must create a ring and save it in the repository. To obtain information on creating NPC rings, see Setting Up Logical Inventory.

Source Device is the beginning of the link and Destination Device is the end of the link.

Step 2 Click Create.

The Create Named Physical Circuits window appears.

Step 3 Click Add Device.

The Select a Device window appears.

Step 4 Choose a CE as the beginning of the link.

Step 5 Click Select.

The device appears in the Create a Named Physical Circuits window.

Step 6 To insert another device or a ring, click Insert Device or Insert Ring.

To add another device or ring to the NPC, click Add Device or Add Ring. For this example, click Add Device to add the N-PE.

Step 7 Choose a PE as the destination device.

Step 8 Click Select.

The device appears.

Step 9 In the Outgoing Interface column, click Select outgoing interface.

A list of interfaces defined for the device appears.

Step 10 Choose an interface from the list and click Select.

Step 11 Click Save.

The Create Named Physical Circuits window now displays the NPC that you created.

Creating a Ring-Only NPC

To create an NPC that contains only a ring without specifying a CE, perform the following steps.

Step 1 Choose Inventory > Logical Inventory > Named Physical Circuits.

Step 2 Click Create.

The Create Named Physical Circuits window appears.

Step 3 Click Add Ring.

The Select NPC Ring window appears.

Step 4 Choose a ring and click Select. The ring appears.

Step 5 Click the Select device link to select the beginning of the ring.

A window appears showing a list of devices.

Step 6 Choose the device that is the beginning of the ring and click Select.

Step 7 Click the Select device link to choose the end of the ring.

Step 8 Choose the device that is the end of the ring and click Select.

Note The device that is the end of the ring in a ring-only NPC must be an N-PE.

Step 9 The Named Physical Circuits window appears showing the Ring-Only NPC.

Step 10 Click Save to save the NPC to the repository.

Terminating an Access Ring on Two N-PEs

Prime Fulfillment supports device-level redundancy in the service topology to provide a failover in case one access link should drop. This is accomplished through a special use of an NPC ring that allows an access link to terminate at two different N-PE devices. The N-PEs in the ring are connected by a logical link using loopback interfaces on the N-PEs. The redundant link starts from a U-PE device and may, optionally, include PE-AGG devices.

For details on how to implement this in Prime Fulfillment, see "Terminating an Access Ring on Two N-PEs."

Creating NPC Links Through the Autodiscovery Process

With autodiscovery, the existing connectivity of network devices can be automatically retrieved and stored in the Prime Fulfillment database. NPCs are further abstracted from the discovered connectivity.

For detailed steps to create NPCs using autodiscovery, see Setting Up Logical Inventory.

Creating and Modifying Pseudowire Classes

The pseudowire class feature provides you with the capability to configure various attributes associated with a pseudowire that is deployed as part of an L2VPN service request on IOS XR-capable devices.

Note The pseudowire class feature is supported for IOS XR 3.6.1 and higher.

The pseudowire class feature supports configuration of the encapsulation, transport mode, fallback options, and selection of a traffic engineering tunnel down which the pseudowire can be directed. For tunnel selection, you can select the tunnel using the Prime Fulfillment Traffic Engineering Management (TEM) application, if it is being used. Otherwise, you can specify the identifier of a tunnel that is already provisioned within the network. For IOS XR-capable devices, the pseudowire class is a separately defined object in the Prime Fulfillment repository, which can be attached to an L2VPN service policy or service request. The pseudowire class feature is only available for use in L2VPN ERS, EWS and ATM policies and service requests.

This section describes how to create and modify pseudowire classes. For information on how the pseudowire class is associated to a L2VPN policy and used within a service request, see Creating an L2VPN Policy. and Managing an L2VPN Service Request.

Creating a Pseudowire Class

To create a pseudowire class, perform the following steps.

Step 1 Choose Inventory > Logical Inventory > Pseudowire Class.

The Pseudowire Class window appears.

Step 2 Click the Create button.

The Create Pseudowire Class window appears.

Step 3 In the Name field, enter a valid PseudoWireClass name.

The pseudowire class name is used for provisioning pw-class commands on the IOS XR device. The name should not exceed 32 characters and should not contain spaces.

Step 4 In the Description field, enter a meaningful description of less than 128 characters.

This field is optional.

Step 5 Choose the MPLS encapsulation type from the Encapsulation drop-down list.

Note Currently, the only encapsulation type supported is MPLS.

Step 6 Choose the transport mode from the TransportMode drop-down list. The choices are:

•NONE (default)

•Vlan

•Ethernet

Note If you want to set the TransportMode to Vlan, we recommend you do this via a pseudowire class, if supported by the version of IOS XR being used. If pseudowire class is not supported in a particular version of IOS XR, then you must set the TransportMode using a Dynamic Component Properties Library (DCPL) property, as explained in the section Configuring the Transport Mode When Pseudowire Classes are Not Supported.

Step 7 Choose the protocol from the Protocol drop-down list. The choices are:

•NONE (default)

•LDP—Configures LDP as the signaling protocol for this pseudowire class.

Step 8 To configures sequencing on receive or transmit, choose a selection from the Sequencing drop-down list. The choices are:

•NONE (default)

•BOTH—Configures sequencing on receive and transmit.

•TRANSMIT—Configures sequencing on transmit.

•RECEIVE—Configures sequencing on receive.

Step 9 Enter a Tunnel ID of a TE tunnel that has already been provisioned by Prime Fulfillment or that has been manually provisioned on the device.

This value is optional. You can also select a TE tunnel that has already been provisioned by Prime Fulfillment, as covered in the next step.

Step 10 Click Select TE Tunnel if you want to select a TE tunnel that has been previously provisioned by Prime Fulfillment.

The Select TE Tunnel pop-up window appears. Choose a TE tunnel and click Select. This populates the TE Tunnel field with the ID of the selected TE tunnel.

Note After a TE tunnel is associated to a pseudowire class or provisioned in a service request, you will receive an error message if you try to delete the TE tunnel using the Traffic Engineering Management (TEM) application. TE tunnels associated with a pseudowire class or service request cannot be deleted.

Step 11 Check the Disable Fallback check box to disable the fallback option for the pseudowire tunnel.

Choose this option based on your version of IOS XR. It is required for IOS XR 3.6.1 and optional for IOS XR 3.7 and above.

Modifying a Pseudowire Class

This section describes how to modify (edit) an existing pseudowire class and how the editing operation might impact L2VPN service requests.

To modify a pseudowire class, perform the following steps.

Step 1 Choose Inventory > Logical Inventory > Pseudowire Class.

The Pseudowire Class window appears.

Step 2 Select the pseudowire class object you want to modify, and click Edit.

The PseudoWire Class Edit window appears.

Step 3 Make the desired changes and click Save.

Note The Name field is not editable if the pseudowire class is associated with any service requests.

If the pseudowire class being modified is associated with any L2VPN service requests, the Affected Jobs window appears, which displays a list of affected service requests

Note A list of affected service requests only appears if the Transport Mode, Tunnel ID, or Disable Fallback values are changed in the pseudowire class being modified.

Step 4 Click Save to update service requests associated with the modified pseudowire class.

The impacted service requests are moved to the Requested state.

Step 5 Click Save and Deploy to update and deploy service requests associated with the modified pseudowire class.

Deployment tasks are created for the impacted service requests that were previously in the Deployed state.

Step 6 Click Cancel to discard changes made to the modified pseudowire class.

In this case, no change of state occurs for any service requests associated with the pseudowire class.

Deleting a Pseudowire Class

To delete a Pseudowire class, follow these steps:

Note A PseudoWire Class that is in use with a service request or policy cannot be deleted.

Step 1 Choose Inventory > Logical Inventory > PseudoWire Class.

The Pseudowire Classes window appears.

Step 2 Check the check box(es) next to the pseudowire class(es) you want to delete.

Step 3 Click the Delete button and a window appears with the selected pseudowire class name.

Step 4 Click the Delete button to confirm that you want to delete the specified pseudowire class(es).

Step 5 Click Cancel if you want to return without deleting the selected pseudowire class(es).

Configuring the Transport Mode When Pseudowire Classes are Not Supported

This section describes how to configure the pseudowire transport mode to be of type Vlan for versions of IOS XR that do not support pseudowire classes. This is done through setting a Dynamic Component Properties Library (DCPL) property. See the usage notes following the steps for additional information.

Perform the following steps.

Step 1 In Prime Fulfillment, navigate to Administration > Control Center > Hosts.

Step 2 Check a check box for a specific host and click the Config button.

Step 3 Navigate to the DCPL property Services\Common\pseudoWireVlanMode.

Step 4 Set the property to true.

Step 5 Click Set Property.

Prime Fulfillment then generates VLAN transport mode configuration for the pseudowire.

Usage notes:

•To set the transport mode to Vlan, it is recommended that you do this via a pseudowire class, if supported by the version of IOS XR being used. If the pseudowire class feature is not supported, then the transport mode must be set using a DCPL property, as explained in the steps of this section

•The DCPL property pseudoWireVlanMode only sets the default value for PseudoWireClass TransportMode as Vlan if the DCPL property is set to true. Users can always over ride it.

•The DCPL property pseudoWireVlanMode acts in a dual way:

–It sets a default value for PseudoWireClass TransportMode to Vlan.

–In the absence of a pseudowire class, it generates a deprecated command transport-mode vlan. The transport-mode vlan command is a deprecated command in IOS XR 3.6 and later. Thus, when a pseudowire class is selected for an IOS XR device and the DCPL property is also set to true, the transport-mode vlan command is not generated. Pseudowire class and the transport-mode vlan command do not co-exist. If a pseudowire class is present, it takes precedence over the deprecated transport-mode vlan command.

•The value of the DCPL property pseudoWireVlanMode should not be changed during the life of a service request.

Defining L2VPN Group Names for IOS XR Devices

This section describes how to specify the available L2VPN group names for policies and service requests for IOS XR devices. The choices appear in a drop-down list of the L2VPN Group Name attribute in policies and service requests. The name chosen is used for provisioning the L2VPN group name on IOS XR devices. The choices are defined through setting a Dynamic Component Properties Library (DCPL) property.

Perform the following steps.

Step 1 In Prime Fulfillment, navigate to Administration > Control Center > Hosts.

Step 2 Check a check box for a specific host and click the Config button.

Step 3 Navigate to the DCPL property Services\Common\l2vpnGroupNameOptions.

Step 4 Enter a comma-separated list of L2VPN group names in the New Value field.

Step 5 Click Set Property.

Creating an EVC Ethernet Policy

This section contains an overview of EVC support in Cisco Prime Fulfillment 6.2, as well as the basic steps to create an EVC Ethernet policy. It contains the following subsections:

•Defining the EVC Ethernet Policy

•Setting the Service Options

•Setting the EVC Attributes

•Setting the Interface Attributes

•Enabling Template Association

For information on creating EVC Ethernet service requests, see Managing an EVC Ethernet Service Request.

Note For a general overview of EVC support in Prime Fulfillment, see the chapter "Layer 2 Concepts" in the Cisco Prime Fulfillment Theory of Operations Guide 6.2.

Note For Ethernet (E-Line and E-LAN) services, use of the EVC policy and service request is recommended. If you are provisioning services using the EVC syntax, or plan to do so in the future, use the EVC service. Existing services that have been provisioned using the L2VPN and VPLS service policy types are still supported and can be maintained with those service types. For ATM and FRoMPLS services, use the L2VPN service policy, as before.

Defining the EVC Ethernet Policy

You must define an EVC Ethernet policy before you can provision a service. A policy can be shared by one or more service requests that have similar service requirements.

A policy is a template of most of the parameters needed to define an EVC service request. After you define it, an EVC policy can be used by all the EVC service requests that share a common set of characteristics. You create a new EVC policy whenever you create a new type of service or a service with different parameters. EVC policy creation is normally performed by experienced network engineers.

An Editable check box in for an attribute in the policy gives the network operator the option of making a field editable. If the value is set to editable, the service request creator can change the value(s) of the particular policy attribute. If the value is not set to editable, the service request creator cannot change the attribute.

You can also associate Prime Fulfillment templates and data files with a policy. See Chapter 9 "Managing Templates and Data Files" for more about using templates and data files in policies.

It is also possible to create user-defined attributes within a policy (and service requests based on the policy). For background information on how to use the additional information feature, see "Adding Additional Information to Services."

To define an EVC Ethernet policy, you start by setting the service type attributes. To do this, perform the following steps.

Step 1 Choose Service Design > Policies > Policy Manager.

The Policy Manager window appears.

Step 2 Click Create.

The Policy Editor window appears.

Step 3 Choose EVC from the Policy Type drop-down list.

The Policy Editor window appears.

Step 4 Enter a Policy Name for the EVC policy.

Step 5 Choose the Policy Owner for the EVC policy.

There are three types of EVC policy ownership:

•Customer ownership

•Provider ownership

•Global ownership—Any service operator can make use of this policy.

This ownership has relevance when the Prime Fulfillment Role-Based Access Control (RBAC) comes into play. For example, an EVC policy that is customer-owned can only be seen by operators who are allowed to work on this customer-owned policy. Similarly, operators who are allowed to work on a provider's network can view, use, and deploy a particular provider-owned policy.

Step 6 Click Select to choose the owner of the EVC policy.

The policy owner was established when you created customers or providers during Prime Fulfillment setup. If the ownership is global, the Select function does not appear.

Step 7 Choose the Policy Type.

The choices are:

•ETHERNET

•ATM-Ethernet Interworking

Note This section describes creating the ETHERNET policy type. For information on using the EVC ATM-Ethernet Interworking policy type, see Creating an EVC ATM-Ethernet Interworking Policy.

Step 8 Click Next.

The Service Options window appears.

Step 9 Continue with the steps contained in the next section, Setting the Service Options.

Setting the Service Options

This section describes how to set the service options for the EVC Ethernet policy,

To set the EVC service options, perform the following steps.

Step 1 Check the CE Directly Connected to EVC check box if the CEs are directly connected to the N-PE.

This check box is not checked by default.

Note The Editable check box gives you the option of making a field editable. If you check the Editable check box, the service operator who is using this EVC policy can modify the editable parameter during EVC service request creation.

Usage notes:

•If the check box is checked, a service request created using this policy can have only directly connected links. No Ethernet access nodes will be involved.

•If the check box is unchecked, a service request created using this policy might or might not have Ethernet access nodes in the links.

•When a CE is directly connected to the N-PE, NPCs are not applicable to the link while creating service requests.

•When a CE is not directly connected to the N-PE, NPCs are used during service request creation, as per standard Prime Fulfillment behavior. There is no change in NPC implementation to support EVC functionality.

Step 2 Check the All Links Terminate on EVC check box if all links need to be configured with EVC features.

This check box is not check by default. Usage notes:

•If the check box is checked, a service request created using such policy will have all links using the EVC feature.

•If the check box is unchecked, zero or more links can use the EVC feature. This ensures that existing platforms can still be used in one or more links while delivering the services. This allows the possibility of a link with EVC support being added in the future.

Note If the check box is unchecked, in the service request creation process the user must indicate whether or not the created link is EVC or non-EVC.

•If no links are expected to use the EVC feature even in the future (for example, if the provider is not planning to upgrade to the EVC infrastructure for the service that is being created), existing Prime Fulfillment policy types (L2VPN or VPLS) can be used instead of EVC.

Step 3 Choose an MPLS Core Connectivity Type from the drop-down list.

Note The core option supports MPLS only. There is no L2TPv3 support for this service.

The choices are:

•PSEUDOWIRE—Choose this option to allow connectivity between two N-PEs across the MPLS core. This option does not limit the service to point-to-point (E-Line). This is because even with the PSEUDOWIRE option selected, there can still be multiple CEs connected to a bridge domain on one or both sides of the pseudowire.

•LOCAL—Choose this option for local connect cases in which there is no connectivity required across the MPLS core.

Local connect supports the following scenarios:

–All interfaces on the N-PE are EVC-capable and using the EVC infrastructure. This is configured by associating all of the customer traffic on these interfaces to a bridge domain. This consumes a VLAN ID on the N-PE (equal to the bridge domain ID).

–Some interfaces on the N-PE are EVC-capable, while others are switch-port-based. In such cases, all of the customer traffic on the interfaces that are configured with the EVC infrastructure are associated to a bridge domain. The traffic on the non-EVC interfaces (and all the access nodes/interfaces beyond this N-PE) are configured with the Service Provider VLAN ID, where the Service Provider VLAN ID is the same as the bridge domain ID for the EVC-based services.

–Only two interfaces on the N-PE are involved, and both are based on EVC-capable line cards. In the first case, the operator might choose not to configure the bridge domain option. In this case, the connect command that is used for the local connects are used, and the global VLAN is conserved on the device. If the operator chooses to configure with the bridge domain option, both interfaces are associated to a bridge domain ID, so that additional local links can be added to the service in future. This consumes a VLAN ID (bridge domain ID) on the N-PE.

•VPLS—Choose this option to allow connectivity between multiple N-PEs across the MPLS core.

There is no limit on the number of N-PEs across the MPLS core within a service request. However, many service requests can refer to the same customer-associated VPN.

Note Attributes available in subsequent windows of the policy workflow dynamically change based on the choice made for the MPLS Core Connectivity Type (PSEUDOWIRE, LOCAL, or VPLS). For completeness, all attributes available for the different core types are documented in the following steps. Attributes apply to all core types, unless otherwise noted.

Note Also, some attributes are supported only on IOS or IOS XR platforms. Attributes apply to both platforms, unless otherwise noted. All platform-specific attributes are visible in the policy workflow windows. Later, when a service request is created based on the policy (and specific devices are associated with the service request), platform-specific attributes are filtered from service request windows, depending on the device type (IOS or IOS XR).

Step 4 Check the Configure With Bridge Domain check box to determine bridge domain characteristics.

The behavior of the Configure With Bridge-Domain option works in tandem with the choice you selected in the MPLS Core Connectivity Type option, as follows.

•PSEUDOWIRE as the MPLS Core Connectivity Type. There are two cases:

A. With EVC:

–If Configure With Bridge Domain is checked, the policy configures pseudowires under SVIs associated to the bridge domain.

–If Configure With Bridge Domain is unchecked, the policy will configure pseudowires directly under the service instance. This conserves the global VLAN.

B. Without EVC:

–If Configure With Bridge Domain is checked, the policy configures pseudowires as in L2VPN services (with SVIs).

–If Configure With Bridge Domain is unchecked, the policy configures pseudowires directly under subinterfaces.

Only pseudowires can be either configured directly under service instance of the corresponding EVC-capable interface or under SVIs associated to the bridge domain.

•LOCAL as the MPLS Core Connectivity Type:

–If Configure With Bridge Domain is checked, the policy allows either point-to-point or multipoint local connect services.

–If Configure With Bridge Domain is unchecked, Prime Fulfillment allows only point-to-point local connects without bridge domain.

•VPLS—Configure With Bridge Domain is checked by default and non-editable.

Step 5 Click Next.

The EVC Attributes window appears.

Step 6 Continue with the steps contained in the next section, Setting the EVC Attributes.

Setting the EVC Attributes

This section describes how to set the EVC attributes for the EVC Ethernet policy.

EVC attributes are organized under the following categories:.

•Service Attributes

•VLAN Match Criteria

•VLAN Rewrite Criteria

The following sections describe how to set the options under each category.

Setting the Service Attributes

To set the EVC service attributes, perform the following steps.

Step 1 Check the AutoPick Service Instance ID check box to specify that the service instance ID will be autogenerated and allocated to the link during service request creation.

If the check box is unchecked, while setting the Prime Fulfillment link attributes during service request creation, Prime Fulfillment will prompt the operator to specify the service instance ID.

Usage notes:

•The service instance ID represents an Ethernet Flow Point (EFP) on an interface in the EVC infrastructure. The service instance ID is locally significant to the interface. This ID has to be unique only at the interface level. The ID must be a value from 1 to 8000.

•There are no resource pools available in Prime Fulfillment from which to allocate the service instance IDs.

•It is the responsibility of the operator creating the service request to maintain the uniqueness of the ID at the interface level.

Step 2 Check the AutoPick Service Instance Name check box to have Prime Fulfillment autogenerate a service instance name when you create a service request based on the policy. The autogenerated value is in the following pattern: CustomerName_ServiceRequestJobID.

If the check box is unchecked, then you can enter a value during service request creation.

Step 3 Check the Enable PseudoWire Redundancy check box to enable pseudowire redundancy (alternative termination device) under certain conditions.

Usage notes:

•Enable Pseudo Wire Redundancy is only available if the MPLS Core Connectivity Type was set as PSEUDOWIRE in the Service Options window (see Setting the Service Options).

•See "Terminating an Access Ring on Two N-PEs" and, specifically, the section Using N-PE Redundancy in FlexUNI/EVC Service Requests, for notes on how this option can be used.

Step 4 Check the AutoPick VC ID check box to have Prime Fulfillment autopick the VC ID during service request creation.

If this check box is unchecked, the operator will be prompted to specify a VC ID during service request creation.

Usage notes:

•This attribute is available only if MPLS Core Connectivity of Type was set as PSEUDOWIRE or VPLS in the Service Options window (see Setting the Service Options).

•When AutoPick VC ID is checked, Prime Fulfillment allocates a VC ID for pseudowires from the Prime Fulfillment-managed VC ID resource pool.

•If MPLS Core Connectivity of Type is VPLS, Prime Fulfillment allocates the VPLS VPN ID from the Prime Fulfillment-managed VC ID resource pool.

Step 5 Check the AutoPick VFI Name check box to have Prime Fulfillment autopick the virtual forwarding instance (VFI) name during service request creation.

If this check box is unchecked, the operator will be prompted to specify a VFI name during service request creation.

Note The AutoPick VFI Name attribute is only applicable if the MPLS Core Connectivity Type is set as VPLS. For other core types (PSEUDOWIRE and LOCAL), this attribute will not be displayed.

Step 6 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID for the service request during service request creation.

If this check box is unchecked, the operator will be prompted to specify a VLAN ID during service request creation.

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain/VLAN ID is picked from the existing Prime Fulfillment VLAN pool. Once the VLAN ID is assigned in the service request, Prime Fulfillment makes the VLAN ID unavailable for subsequent service requests.

•In the case of manual VLAN ID allocation, Prime Fulfillment does not manage the VLAN ID if the ID lies outside the range of an Prime Fulfillment-managed VLAN pool. In this case, the operator must ensure the uniqueness of the ID in the Ethernet access domain. If an operator specifies a VLAN ID that is within the range of an Prime Fulfillment-managed VLAN pool and the VLAN ID is already in use in the access domain, Prime Fulfillment displays an error message indicating that the VLAN ID is in use.

Note on Access VLAN IDs

An access VLAN ID is of local significance to the EVC-capable ports. It should not be confused with the global VLANs. This can be visualized as a partitioning of the Ethernet access network beyond the EVC ports into several subEthernet access domains (one each for an EVC-capable port).

However, all the service interfaces on the Ethernet access nodes beyond the EVC ports will have this very same VLAN ID for a link. This ID must be manually specified by the operator when setting the link attributes during service request creation. The operator must ensure the uniqueness of the ID across the EVC-demarcated Ethernet access domain.

These VLAN IDs are not managed by Prime Fulfillment by means of locally-significant VLAN pools. But once a VLAN ID is assigned for a link in the service request, Prime Fulfillment makes the VLAN unavailable for subsequent service requests within the Ethernet access domain demarcated by the EVC. Likewise, if a manually-specified VLAN is already in use in the access domain delimited by the EVC, Prime Fulfillment will display an error message indicating that the new VLAN ID being specified is already in use on the NPC. The operator will be prompted to specify a different VLAN ID, which will be provisioned on the L2 access nodes.

Step 7 Check the AutoPick Bridge Group Name check box to have Prime Fulfillment autopick the group name for the service request during service request creation.

If this check box is unchecked, the operator will be prompted to specify a group name during service request creation. If the check box is checked, the group name will default to the customer name.

Note This attribute is applicable only for supported IOS XR devices.

Step 8 Check the AutoPick Bridge Domain Name check box to have Prime Fulfillment autopick the domain name for the service request during service request creation.

Usage notes:

•If this check box is unchecked, the operator will be prompted to specify a domain name during service request creation.

•If the check box is checked, the domain name will default to the following format:

–For pseudowire and local connect core types: ISC-Job-Job_ID, where Job_ID is the service request job ID.

–For VPLS core type: ISC-VPN_Name-VPN_ID, where VPN_Name is the name of the VPLS VPN being used, and VPN_ID is the VPN ID used in the service request.

Note This attribute is applicable only for supported IOS XR devices.

Step 9 Continue with the steps contained in the next section, Setting the VLAN Matching Criteria Attributes.

Setting the VLAN Matching Criteria Attributes

Prior to the introduction of the EVC capability, service providers could either deploy service-multiplexed services (ERS/ERMS or EVPL/EVCS) or service-bundled services on a single port. Both could not be supported simultaneously due to the limitations in the infrastructure, which only allowed matching the outer-most VLAN tag.

One of the key benefits of EVC support in Prime Fulfillment is to provide a flexible means to examine the VLAN tags (up to two levels) of the incoming frames and associate them to appropriate Ethernet Flow Points (EFPs). This allows service providers to deploy simultaneously both the service-multiplexed and service-bundled services on a single port.

To set the EVC VLAN matching criteria attributes, perform the following steps.

Step 1 Check the Both Tags check box to enable service requests created with the policy to match both the inner and outer VLAN tags of the incoming frames.

If you do not check this check box, service requests created with the policy will match only the outer VLAN tag of the incoming frames.

Checking the Both Tags attribute causes the Inner VLAN Ranges attribute (covered in the next steps) to appear in the EVC Attribute window.

Step 2 Check the Inner VLAN Ranges check box to enable the range of inner VLAN tags to be specified during service request creation.

If the check box is unchecked, the range of inner VLAN tags are not allowed. In this case, the operator must specify discrete VLAN IDs during service request creation.

Step 3 Check the Outer VLAN Ranges check box to enable the range of outer VLAN tags to be specified during service request creation.

If the check box is unchecked, the range of outer VLAN tags are not allowed. In this case, the operator must specify discrete VLAN IDs during service request creation.

Step 4 Check the AutoPick Outer VLAN check box to have Prime Fulfillment autopick the outer VLAN ID from a previously created outer VLAN ID resource pool during service request creation.

If this check box is unchecked, the operator will be prompted to specify an outer VLAN ID during service request creation.

Note Use of the AutoPick Outer VLAN attribute requires that two elements have already been set up in Prime Fulfillment. One is an Interface Access Domain, which is a logical element that groups the physical ports of an N-PE device. The other is an EVC Outer VLAN resource pool, which is used by the Interface Access Domain. For instructions on how to set up these elements, see the sections Setting Up Resources, and Resource Pools.

Usage notes:

•AutoPick Outer VLAN can be used for interfaces that support EVC functionality.

•AutoPick Outer VLAN consumes a VLAN ID on the interface that supports EVC.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

Step 5 Continue with the steps contained in the next section, Setting the VLAN Rewrite Criteria Attributes.

Setting the VLAN Rewrite Criteria Attributes

Together with VLAN matching criteria, VLAN rewrite makes the EVC infrastructure very powerful and flexible. The following VLAN rewrite options are supported:

•Pop one or two tags.

•Push one or two tags.

•Translation (1:1, 2:1, 1:2, 2:2).

Be aware of the following considerations when setting the VLAN rewrite criteria attributes:

•Only one kind of rewrite can be done on every CE-facing EVC link.

•All VLAN rewrites are done using the symmetric keyword on the ingress traffic (for example, rewrite ingress tag pop 2 symmetric).

•For any service instance, only one type of rewrite option (pop, push, or translate) is allowed per instance. For example, if pop out is enabled, push inner, push outer, translate inner, and translate outer are not available.

To set the EVC VLAN rewrite criteria attributes, perform the following steps.

Step 1 Check the Pop Outer check box to pop the outer VLAN ID tag of the incoming frames that fulfill the match criteria.

If this check box is unchecked, the outer tag of the incoming traffic is not popped.

Step 2 Check the Pop Inner check box to pop the inner VLAN ID tag of the incoming frames that fulfill the match-criteria.

If this check box is unchecked, the inner tag is not popped. Note that, if Pop Inner is checked, Pop Outer is automatically checked.

Step 3 Check the Push Outer check box to impose an outer VLAN ID tag onto the incoming frames that fulfill the match criteria.

If this check box is unchecked, no outer tag is imposed on the incoming frames.

Usage notes:

•If Push Outer is checked, all service requests created with the policy push a dot1q outer tag on the incoming frames matching the match criteria. When creating the link during service creation, the operator can specify an outer tag with a value from 1 to 4096.

•This attribute is available regardless of the number of tags used in the match criteria. Whether the incoming traffic is double tagged or single tagged, if Push Outer is enabled, all corresponding service requests push an outer tag. All subsequent nodes consider only the outer-most two tags (if EVC-capable) or just one tag (not EVC-capable) and treat the inner-most tags transparently as payload.

•This VLAN ID is not derived from Prime Fulfillment-managed VLAN ID pools.

Step 4 Check the Push Inner check box to impose an inner VLAN ID tag onto the incoming frames that fulfill the match criteria.

This operation pushes both an inner and an outer tag onto the incoming packet, not just an inner tag. If this check box is unchecked, no inner tag is imposed on the incoming frames.

Usage notes:

•If Push Inner is checked, all service requests created with the policy push a dot1q inner tag on the incoming frames matching the match criteria. When creating the link during service creation, the operator can specify an inner tag with a value from 1 to 4096.

•If Push Inner is checked, Push Outer is automatically checked.

•This attribute is available regardless of the number of tags used in the match criteria. Regardless of whether the incoming traffic is double tagged or single tagged, if Push Inner is enabled, all corresponding service requests push an inner tag. All subsequent nodes consider only the outer-most two tags (if EVC-capable) or just one tag (not EVC-capable) and treat the inner-most tags transparently as payload.

•This VLAN ID is not derived from Prime Fulfillment-managed VLAN ID pools.

Step 5 Check the Translate Outer check box to allow the operator to specify a target outer VLAN ID during service request creation.

The outer tag of all the incoming frames that fulfill the match criteria are translated to this ID. If the check box is unchecked, no outer tag translation is performed. See Table 3-2.

Step 6 Check the Translate Inner check box to allow the operator to specify a target inner VLAN ID during service request creation.

The inner tag of all the incoming frames that fulfill the match criteria are translated to this ID. If the check box is unchecked, no inner tag translation is performed. See Table 3-2.

Note Table 3-2 summarizes the realization of different VLAN translations available in the EVC infrastructure. The second and third columns (Match Outer Tag and Match Inner Tag) refer to policy settings. The last two columns (Translate Outer Tag and Translate Inner Tag) indicate the VLAN translation that occurs on the incoming frames.

Step 7 Click Next.

The Interface Attribute window appears.

Step 8 Continue with the steps contained in the next section, Setting the Interface Attributes.

Setting the Interface Attributes

This step of creating the EVC Ethernet policy involves setting the interface attributes in the Interface Attribute window. The attributes you can configure in this window are grouped under the following categories:

•UNI Information

•VLAN

•Pseudowire

•ACL

•Security

•UNI Storm Control

•Protocol

In some cases, checking an attribute causes additional attributes to appear in the GUI. This is covered in the steps that follow.

Note If the CE is directly connected to an N-PE, only speed, duplex, UNI shutdown, and other generic options are presented. In this case, port security, storm control, L2 protocol tunneling, and other advanced features are not supported due to the current platform limitations. If these features are needed for a service, the service provider must deploy Layer 2 Ethernet access nodes beyond the EVC to support these requirements.

Note Attributes available in the Interface Attributes window dynamically change based on the choice made for the MPLS Core Connectivity Type (PSEUDOWIRE, LOCAL, or VPLS) in the Service Options window (see Setting the Service Options). For completeness, all attributes available for the different core types are documented in the following steps. Attributes apply to all core types, unless otherwise noted.

To set the EVC interface attributes, perform the following steps.

Step 1 Check the Standard UNI Port check box to enable port security.

This is the default. When you uncheck the check box, the port is treated as an uplink with no security features, and the window dynamically changes to eliminate items related to port security.

Step 2 Check the UNI Shutdown check box if you want to leave the UNI port shut during service activation, for example, when the service provider wants to deploy a service in the network but wants to activate it at a later time.

Step 3 Check the Keep Alive check box to configure keepalives on the UNI port.

By default, this check box is unchecked, which causes the command no keepalive to be provisioned on the UNI port. This prevents a CPE from sending keepalive packets to the U-PE, for security purposes. This attribute is editable, in order to support modification on a per-service request basis.

Step 4 Enter a Link Media (optional) of None, auto-select, rj45, or sfp.

Step 5 Enter a Link Speed (optional) of None, 10, 100, 1000, Auto, or nonegotiate.

Step 6 Enter a Link Duplex (optional) of None, Full, Half, or Auto.

Step 7 Choose an Encapsulation type.

The choices are:

•DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation. If the UNI belongs to a directly connected and EVC link, this setting signifies that the incoming frames are 802.1q encapsulated and that they match the VLAN ID configured for the link. This specific topology does not involve a trunk UNI as such.

•DOT1QTUNNEL—Configures the UNI as an 802.1q tunnel (also known as a dot1q tunnel or Q-in-Q) port.

•ACCESS—Configures the UNI as an access port.

Step 8 Specify the type of VLAN Translation for this policy by clicking the appropriate radio button.

The choices are:

•No—No VLAN translation is performed. (This is the default.)

•1:1—1:1 VLAN translation. Translates an incoming customer VLAN to another.

•2:1—2:1 VLAN translation. Converts both inner and outer VLANs to a single VLAN.

•1:2—1:2 VLAN translation. Pushes one more provider VLAN.

•2:2—2:2 VLAN translation. Translates both inner and outer VLANs to two other VLANs.

Note For more details on how VLAN translation is supported in EVC Ethernet services, see the coverage of the VLAN Translation attribute in Managing an EVC Ethernet Service Request.

Step 9 Check the Use PseudoWireClass check box to enable the selection of a pseudowire class.

This attribute is unchecked by default.

Usage notes:

•The pseudowire class name is used for provisioning pw-class commands on IOS XR devices. See Creating and Modifying Pseudowire Classes for additional information on pseudowire class support for IOS XR devices.

•If Use PseudoWireClass is checked, an additional attribute, PseudoWireClass, appears in the GUI. Click the Select button of PseudoWireClass attribute to choose a pseudowire class previously created in Prime Fulfillment.

•The Use PseudoWireClass attribute is only available if the MPLS core connectivity type was set as PSEUDOWIRE in the Service Options window (see Setting the Service Options).

•Use PseudoWireClass is only applicable for IOS XR devices.

Step 10 For L2VPN Group Name choose one of the following from the drop-down list:

•ISC

•VPNSC

Usage notes:

•This attribute is used for provisioning the L2VPN group name on IOS XR devices.

Note The choices in the drop-down list are derived from a configurable DCPL property. For information about how to define the L2VPN Group Name choices available in the drop-down list, see Defining L2VPN Group Names for IOS XR Devices.

•The L2VPN Group Name attribute is not available if the MPLS core connectivity type was set as VPLS in the Service Options window (see Setting the Service Options).

•L2VPN Group Name is only applicable for IOS XR devices.

Step 11 Enter an E-Line Name to specify the point-to-point (p2p) E-line name.

Usage notes:

•If no value is specified for the E-Line Name in either the policy or the service request based on the policy, Prime Fulfillment autogenerates a default name as follows:

–For PSEUDOWIRE core connectivity type, the format is:

DeviceName--VC_ID

–For LOCAL core connectivity type, the format is:

DeviceName--0--VLAN_ID

If the default name is more than 32 characters, the device names are truncated.

•The E-Line Name attribute is not available if the MPLS core connectivity type was set as VPLS in the Service Options window (see Setting the Service Options).

•E-Line Name is only applicable for IOS XR devices.

Step 12 Check the PW Tunnel Selection check box if you want to be able to manually select the Traffic Engineering (TE) tunnel for the pseudowire connecting point-to-point N-PEs.

This attribute is unchecked by default.

Subsequently, when you create a service request based on this policy, you must specify the TE tunnel ID in a field provided. Prime Fulfillment uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs. This pseudowire class can be shared by more than one pseudowire, as long as the pseudowires share the same tunnel ID and remote loopback address. You are responsible to ensure that the tunnel interface and associated ID are configured. During service request creation when you specify the tunnel ID number, Prime Fulfillment does not check the validity of the value. That is, Prime Fulfillment does not verify the existence of the tunnel.

Step 13 Check the N-PE Pseudo-wire on SVI check box to have Prime Fulfillment generate forwarding commands under SVIs (switch virtual interfaces).

By default, this check box is not checked. In this case, Prime Fulfillment generates forwarding commands under the service instance.

For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (this is available in the policy workflow in the EVC Policy Editor - Service Options window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE Pseudo-wire on SVI is enabled.

Usage notes:

•Prime Fulfillment supports a hybrid configuration for EVC service requests. In a hybrid configuration, the forwarding commands (such as xconnect) for one side of an attachment circuit can be configured under a service instance, and the xconnect configuration for the other side of the attachment circuit can be configured under a switch virtual interface (SVI).

•For examples of these cases, see configlet examples EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) and EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI).

•N-PE Pseudo-wire on SVI is applicable for all connectivity types (PSEUDOWIRE, VPLS, and LOCAL), but a hybrid SVI configuration is possible only for pseudowire connectivity.

•When MPLS Core Connectivity Type is set as VPLS, the N-PE Pseudo-wire on SVI attribute is always enabled in the policy and service request.

•When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy and service request.

•The N-PE Pseudo-wire on SVI attribute is not supported for IOS XR devices. Only subinterfaces are supported on ASR 9000 devices; service instance is not supported. All the xconnect commands are configured on L2 subinterfaces.

•Table 3-3 shows various use cases for hybrid configuration for EVC service requests.

Step 14 Check the Use Existing ACL Name check box if you want to assign your own named access list to the port.

By default, this check box is not checked and Prime Fulfillment automatically assigns a MAC-based ACL on the customer facing UNI port, based on values you enter in UNI MAC addresses (below).

Step 15 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step).

Note Prime Fulfillment does not create this ACL automatically. The ACL must already exist on the device, or be added as part of a template, before the service request is deployed. Otherwise, deployment will fail.

Step 16 Enter one or more Ethernet MAC addresses in UNI MAC addresses.

This selection is present only if you uncheck the Use Existing ACL Name check box. Click the Edit button to bring up a pop-up window in which you enter MAC addresses to be allowed or denied on the port. You can also specify a range of addresses by setting a base MAC address and a filtered MAC address.

Step 17 Check the UNI Port Security check box if you to want to provision port security-related CLIs to the UNI port by controlling the MAC addresses that are allowed to go through the interface.

a. For Maximum Number of MAC address, enter the number of MAC addresses allowed for port security.

b. For Aging, enter the length of time the MAC address can stay on the port security table.

c. For Violation Action, choose what action will occur when a port security violation is detected:

•PROTECT—Drops packets with unknown source addresses until a sufficient number of secure MAC addresses are removed to drop below the maximum value.

•RESTRICT—Drops packets with unknown source addresses until a sufficient number of secure MAC addresses are removed to drop below the maximum value and causes the Security Violation counter to increment.

•SHUTDOWN—Puts the interface into the error-disabled state immediately and sends an SNMP trap notification.

d. In the Secure MAC Addresses field, enter one or more Ethernet MAC addresses.

Step 18 Check the Enable Storm Control check box to help prevent the UNI port from being disrupted by a broadcast, multicast, or unicast storm.

Enter a threshold value for each type of traffic. The value, which can be specified to two significant digits, represents the percentage of the total available bandwidth of the port. If the threshold of a traffic type is reached, further traffic of that type is suppressed until the incoming traffic falls below the threshold level.

Step 19 Check the Protocol Tunnelling check box if you want to define the Layer 2 Bridge Protocol Data Unit (BPDU) frames that can be tunneled over the core to the other end.

For each protocol that you choose, enter the shutdown threshold and drop threshold for that protocol:

a. Enable cdp—Enable Layer 2 tunnelling on Cisco Discover Protocol (CDP).

b. cdp shutdown threshold—Enter the number of packets per second to be received before the interface is shut down.

c. cdp drop threshold—Enter the number of packets per second to be received at which point the interface will start dropping CDP packets.

d. Enable vtp—Enable Layer 2 tunnelling on VLAN Trunk Protocol (VTP).

e. vtp shutdown threshold—Enter the number of packets per second to be received before the interface is shut down.

f. vtp drop threshold—Enter the number of packets per second to be received at which point the interface will start dropping VTP packets.

g. Enable stp—Enable Layer 2 tunnelling on Spanning Tree Protocol (STP).

h. stp shutdown threshold—Enter the number of packets per second to be received before the interface is shut down.

i. stp drop threshold—Enter the number of packets per second to be received at which point the interface will start dropping STP packets.

j. Recovery Interval—Enter the amount of time, in seconds, to wait before recovering a UNI port.

Step 20 Enter the MTU Size in bytes.

The maximum transmission unit (MTU) size is configurable and optional. The default size is 9216, and the range is 1500 to 9216. Prime Fulfillment does not perform an integrity check for this customized value. If a service request goes to the Failed Deploy state because this size is not accepted, you must adjust the size until the Service Request is deployed.

In Cisco Prime Fulfillment 1.0, different platforms support different ranges.

•For the 3750 and 3550 platforms, the MTU range is 1500 to 1546.

•For the Cisco 7600 Ethernet port, the MTU size is always 9216. Even with the same platform and same IOS release, different line cards support the MTU differently. For example, older line cards only take an MTU size of 9216 and newer cards support 1500 to 9216. However, Prime Fulfillment uses 9216 in both cases.

•For the Cisco 7600 SVI (interface VLAN), the MTU size is 1500 to 9216.

Step 21 If you would like to enable template association for this policy, click the Next button.

See the section Enabling Template Association for information about this feature.

Note An additional window appears the policy workflow before the Template Association window. This window allows you to create user-defined attributes within the policy (and service requests based on the policy). For background information on how to use the additional information feature, see "Adding Additional Information to Services." If you are not using this feature, click Next to proceed to the Template Association window, or else click Finish to save the policy.

Step 22 To save the EVC policy, click Finish.

To create a service request based on an EVC policy, see Managing an EVC Ethernet Service Request.

Enabling Template Association

The Prime Fulfillment template feature gives you a means to download free-format CLIs to a device. If you enable templates, you can create templates and data files to download commands that are not currently supported by Prime Fulfillment.

Step 1 To enable template association for the policy, click the Next button in the Interface Attribute window (before clicking Finish).

The Template Association window appears. In this window, you can enable template support and, optionally, associate templates and data files with the policy. For instructions about associating templates with policies and how to use the features in this window, see Using Templates with Service Requests.

Step 2 When you have completed setting up templates and data files for the policy, click Finish in the Template Association window to close it and return to the Policy Editor window.

Step 3 To save the EVC policy, click Finish.

To create a service request based on an EVC policy, see Managing an EVC Ethernet Service Request.

Managing an EVC Ethernet Service Request

This section provides information on how to provision an EVC Ethernet service request. It contains the following subsections:

•Configuring Device Settings to Support Prime Fulfillment

•Creating an EVC Service Request

•Setting the Service Request Details

•Modifying the EVC Service Request

•Using Templates and Data Files with an EVC Ethernet Service Request

•Saving the EVC Service Request

Introducing EVC Service Requests

An EVC Ethernet service request allows you to configure interfaces on an N-PE to support the EVC features described in Creating an EVC Ethernet Policy. To create an EVC service request, an EVC service policy must already be defined. Based on the predefined EVC policy, an operator creates an EVC service request and deploys the service. One or more templates can also be associated to the N-PE as part of the service request.

Creating an EVC Ethernet service request involves the following steps:

•Choose an existing EVC Ethernet policy.

•Choose a VPN.

Note When working with VPN objects in the context of EVC Ethernet policies and service requests, only the VPN name and customer attributes are relevant. Other VPN attributes related to MPLS and VPLS are ignored.

•Specify a bridge domain configuration (if applicable).

•Specify a service request description.

•Specify automatic or manual allocation of the VC ID or VPLS VPN ID.

•Add direct connect links (if applicable).

•Add links with L2 access nodes (if applicable).

•Choose the N-PE and UNI interface for links.

•For links with L2 access nodes, choose a Named Physical Circuit (NPC) if more than one NPC exists from the N-PE or the UNI interface.

•Edit the link attributes.

•Modify the service request.

•Save the service request.

For sample configlets for EVC Ethernet scenarios, see Sample Configlets.

Creating an EVC Service Request

To create an EVC Ethernet service request, perform the following steps.

Step 1 Choose Operate > Service Requests > Service Request Manager.

The Service Request Manager window appears.

Step 2 Click Create.

The Service Request Editor window appears.

Step 3 From the Policy drop-down list, choose an EVC policy from the policies previously created (see Creating an EVC Ethernet Policy).

The EVS Service Request editor window appears.

The new service request inherits all the properties of the chosen EVC policy, such as all the editable and non-editable features and pre-set parameters.

Step 4 Continue with the steps contained in the next section, Setting the Service Request Details.

Setting the Service Request Details

After you have selected the EVC Ethernet policy to be used as the basis of the service request, the EVC Service Request Editor window appears. It is divided into three main sections:

•Link Page

•Direct Connect Links (no NPCs)

•Links with L2 Access Nodes (involves NPCs)

This window enables you to specify options for the service request, as well as configure directly connected links and links with L2 access nodes. The options displayed in first section of the window change, depending on the MPLS Core Connectivity Type that was specified in the policy (pseudowire, VPLS, or local). For clarity, each of these scenarios is presented in a separate section below, to highlight the different window configurations and behavior of the displayed options.

Proceed to the appropriate section, as determined by the MPLS Core Connectivity Type for the policy:

•Pseudowire Core Connectivity

•VPLS Core Connectivity

•Local Core Connectivity

Instructions for setting up direct connect links and links with L2 access nodes are presented in later sections.

Pseudowire Core Connectivity

This sections covers the case in which the MPLS Core Connectivity Type for the EVC Ethernet policy is PSEUDOWIRE.

To set the attributes in the first section of the Link Page window. perform the following steps.

Note The Job ID and SR ID fields are read-only. When the service request is being created for the first time, the fields display a value of NEW. When an existing service request is being modified, the values of the fields indicate the respective IDs that the Prime Fulfillment database holds within the editing flow of the service request.

Note The Policy field is read-only. It displays the name of the policy on which the service request is based. Clicking on the read-only policy name displays a list of all the attribute values set within the policy.

Step 1 Click Select VPN to choose a VPN for use with this service request.

The Select VPN window appears with the VPNs defined in the system.

Note The same VPN can be used by service requests with LOCAL and PSEUDOWIRE core types. If a VPN for a service request is used with VPLS core type, the same VPN cannot be used for service requests with LOCAL or PSEUDOWIRE core type.

Step 2 Choose a VPN Name in the Select column.

Step 3 Click Select.

The EVC Service Request Editor window appears with the VPN name displayed.

Step 4 Check the AutoPick VC ID check box if you want Prime Fulfillment to choose a VC ID.

If you do not check this check box, you will be prompted to provide the ID in the VC ID field, as covered in the next step.

When AutoPick VC ID is checked, Prime Fulfillment allocates a VC ID for pseudowires from the Prime Fulfillment-managed VC ID resource pool. In this case, the text field for the VC ID option is non-editable.

Step 5 If AutoPick VC ID was unchecked, enter a VC ID in the VC ID field.

Usage notes:

•The VC ID value must be an integer value corresponding to a VC ID.

•When a VC ID is manually allocated, Prime Fulfillment verifies the VC ID to see if it lies within Prime Fulfillment's VC ID pool. If the VC ID is in the pool but not allocated, the VC ID is allocated to the service request. If the VC ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VC ID. If the VC ID lies outside of the Prime Fulfillment VC ID pool, Prime Fulfillment does not perform any verification about whether or not the VC ID allocated. The operator must ensure the VC ID is available.

•The VC ID can be entered only while creating a service. If you are editing the service request, the VC ID field is not editable.

Step 6 Check the Enable PseudoWire Redundancy check box to enable pseudowire redundancy (alternative termination device) under certain conditions.

See "Terminating an Access Ring on Two N-PEs" and, specifically, the section Using N-PE Redundancy in FlexUNI/EVC Service Requests, for notes on how this option can be used.

Step 7 If the AutoPick VC ID attribute was unchecked, enter a VC ID for the backup pseudowire in the Backup PW VC ID field.

See the usage notes for the AutoPick VC ID attribute in Step 7, above. The backup VC ID behaves the same as the VC ID of the primary pseudowire.

Step 8 Check the Configure Bridge Domain check box to determine bridge domain characteristics.

The behavior of the Configure Bridge Domain option works in tandem with the choice you selected in the MPLS Core Connectivity Type option in the EVC policy, which in this case is pseudowire core connectivity. There are two cases:

•With EVC:

–If Configure With Bridge Domain is checked, the policy will configure pseudowires under SVIs associated to the bridge domain.

–If Configure With Bridge Domain is unchecked, the policy will configure pseudowires directly under the service instance. This will conserve the global VLAN.

•Without EVC:

–If Configure With Bridge Domain is checked, the policy will configure pseudowires under SVIs.

–If Configure With Bridge Domain is unchecked, the policy will configure pseudowires directly under subinterfaces.

Pseudowires can be configured either directly under service instance of the corresponding EVC-capable interface or under SVIs associated to the bridge domain.

Step 9 Check the Use Split Horizon check box to enable split horizon with bridge domain.

Usage notes:

•The Use Split Horizon attribute is disabled by default.

•The Use Split Horizon attribute can be used only when the Configure Bridge Domain check box is checked (enabled).

•When Use Split Horizon is enabled, the bridge domain command in the CLI will be generated with split horizon. When it is disabled, the bridge domain command will be generated without split horizon.

Step 10 Click the "Click here" link of the Description attribute to enter a description label for the service request.

This is useful for searching the Prime Fulfillment database for the particular service request.

A dialogue appears in which you can enter a description.

Step 11 To set up direct connect links, see the section Setting Direct Connect Links.

Step 12 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes.

VPLS Core Connectivity

This section covers the case in which the MPLS Core Connectivity Type for the EVC Ethernet policy is VPLS.

To set the attributes in the first section of the Link Page window, perform the following steps.

Step 1 The Job ID and SR ID fields are read-only.

When the service request is being created for the first time, the fields display a value of NEW. When an existing service request is being modified, the values of the fields indicate the respective IDs that the Prime Fulfillment database holds within the editing flow of the service request.

Step 2 The Policy field is read-only. It displays the name of the policy on which the service request is based.

Step 3 Click Select VPN to choose a VPN for use with this service request.

The Select VPN window appears with the VPNs defined in the system.

Note The same VPN can be used by service requests with LOCAL and PSEUDOWIRE core types. If a VPN for a service request is used with VPLS core type, the same VPN cannot be used for service requests with LOCAL or PSEUDOWIRE core type.

Note If the same VPN is used among multiple service requests, all having VPLS core type, then all these service requests participate in the same VPLS service.

Step 4 Choose a VPN Name in the Select column.

Step 5 Click Select.

The EVC Service Request Editor window appears with the VPN name displayed.

Step 6 Check the AutoPick VPLS VPN ID check box if you want Prime Fulfillment to choose a VPLS VPN ID.

If you do not check this check box, you will be prompted to provide the VPN ID in the VPLS VPN ID field, as covered in the next step.

•When AutoPick VPLS VPN ID is checked, Prime Fulfillment allocates a VPLS VPN ID from the Prime Fulfillment-managed VC ID resource pool. In this case, the text field for the VPLS VPN ID option is non-editable.

•If AutoPick VPLS VPN ID is checked and a service request already exists that refers to same VPN object, the VPLS VPN ID of the existing service request is allocated to the new service request.

Step 7 If AutoPick VPLS VPN ID was unchecked, enter a VPLS VPN ID in the VPLS VPN ID field.

Usage notes:

•The VPLS VPN ID value must be an integer value corresponding to a VPN ID.

•When a VPLS VPN ID is manually allocated, Prime Fulfillment verifies the VPLS VPN ID to see if it lies within Prime Fulfillment's VC ID pool. If the VPLS VPN ID is in the pool but not allocated, the VPLS VPN ID is allocated to the service request. If the VPLS VPN ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VPLS VPN ID. If the VPLS VPN ID lies outside of the VC ID pool, Prime Fulfillment does not perform any verification about whether the VPLS VPN ID allocated. The operator must ensure the VPLS VPN ID is available.

•The VPLS VPN ID can be entered only while creating a service. If you are editing the service request, the VPLS VPN ID field is not editable.

Step 8 Check the AutoPick VFI Name check box if you want Prime Fulfillment to choose a virtual forwarding instance (VFI) name.

If you do not check this check box, you can provide the VFI name in the VFI Name field, as covered in the next step.

Usage notes:

•When AutoPick VFI name is checked, Prime Fulfillment generates a VFI name in the following format:

VPN name-VC ID

•This attribute is useful when importing an existing service into Prime Fulfillment and mapping it to a service request which has been created for this purpose. Manually specifying the VFI name in the service request allows the VFI name to be matched to that of existing service.

Step 9 If AutoPick VFI Name was unchecked, enter a VFI name in the VFI Name field.

Step 10 Choose the Discovery Mode type for VPLS autodiscovery.

The choices are:

•Manual—Does not provision VPLS autodiscovery on VPLS PE devices configured by the service request. In this case, when a new PE is device is added or removed from the VPLS domain, manual configuration of each neighbor in the VPLS domain is required.

•Auto Discovery—Provisions VPLS autodiscovery on VPLS PE devices configured by the service request. With VPLS autodiscovery enabled, neighbor devices automatically detect when PEs are added or removed from the VPLS domain.

For details on how this feature is supported in Prime Fulfillment, device preconfiguration requirements, and limitations, see Provisioning VPLS Autodiscovery on Devices using EVC Service Requests.

Step 11 The Configure Bridge Domain check box is check by default and cannot be changed.

Usage notes:

•For VPLS, all configurations are under the SVI.

•When the EVC feature is used, all configurations are under the SVI and also associated to a bridge domain.

Step 12 Check the Use Split Horizon check box to enable split horizon with bridge domain.

Usage notes:

•The Use Split Horizon attribute is disabled by default.

•The Use Split Horizon attribute can be used only when the Configure Bridge Domain check box is checked (enabled).

•When Use Split Horizon is enabled, the bridge domain command in the CLI will be generated with split horizon. When it is disabled, the bridge domain command will be generated without split horizon.

Step 13 Click the "Click here" link of the Description attribute to enter a description label for the service request.

A dialogue appears in which you can enter a description.

Step 14 To set up direct connect links, see the section Setting Direct Connect Links.

Step 15 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes.

Local Core Connectivity

This section covers the case in which the MPLS Core Connectivity Type for the EVC Ethernet policy is LOCAL.

To set the attributes in the first section of the Link Page window, perform the following steps.

Step 1 The Job ID and SR ID fields are read-only.

When the service request is being created for the first time, the fields display a value of NEW. When an existing service request is being modified, the values of the fields indicate the respective IDs that the Prime Fulfillment database holds within the editing flow of the service request.

Step 2 The Policy field is read-only.

It displays the name of the policy on which the service request is based.

Step 3 Click Select VPN to choose a VPN for use with this service request.

The Select VPN window appears with the VPNs defined in the system.

Note The same VPN can be used by service requests with LOCAL and PSEUDOWIRE core types. If a VPN for a service request is used with VPLS core type, the same VPN cannot be used for service requests with LOCAL or PSEUDOWIRE core type.

Step 4 Choose a VPN Name in the Select column.

Step 5 Click Select.

The EVC Service Request Editor window appears with the VPN name displayed.

Step 6 Check the Configure Bridge Domain check box to determine bridge domain characteristics.

Usage notes:

•If Configure Bridge Domain is checked, all links will have the same bridge domain ID allocated from the VLAN pool on the N-PE. All non-EVC links will have the Service Provider VLAN as the bridge domain ID. On the other hand, if no EVC links are added, the Service Provider VLAN will be allocated first and this will be used as the bridge domain ID when EVC links are added.

•If Configure Bridge Domain is unchecked, a maximum of two links that terminate on the same N-PE can be added. (This uses the connect command available in the EVC infrastructure.)

Note See the following comments for details on how Prime Fulfillment autogenerates the connect name.

Because the device only accepts a maximum of 15 characters for the connect name, the connect name is generated using the following format:

CustomerNameTruncatedToMaxPossibleCharacters_ServiceRequestJobID

For example, if the customer name is NorthAmericanCustomer and the service request job ID is 56345, the autogenerated connect name would be NorthAmer_56345.

The CLI generated would be:

connect NorthAmer_56345 GigabitEthernet7/0/5 11 GigabitEthernet7/0/4 18

In this case, 11 and 18 are service instance IDs.

•If the policy setting for Configure Bridge Domain is non-editable, the option in the service request will be read-only.

Step 7 Check the Use Split Horizon check box to enable split horizon with bridge domain.

Usage notes:

•The Use Split Horizon attribute is disabled by default.

•The Use Split Horizon attribute can be used only when the Configure Bridge Domain check box is checked (enabled).

•When Use Split Horizon is enabled, the bridge domain command in the CLI will be generated with split horizon. When it is disabled, the bridge domain command will be generated without split horizon.

Step 8 Click the "Click here" link of the Description attribute to enter a description label for the service request.

A dialogue appears in which you can enter a description.

Step 9 To set up direct connect links, see the section Setting Direct Connect Links.

Step 10 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes.

Setting up Links to the N-PE

The lower two sections of the EVC Service Request Editor window allow you to set up links to the N-PE. For direct connect links, the CE is directly connected to the N-PE, with no intermediate L2 access nodes. For links with L2 access nodes, there are intermediate devices present between the CE and NPE requiring NPCs to be created in Prime Fulfillment.

The Direct Connect Links section of the window is where you set up links that directly connect to the N-PE. No NPC are involved. The Links with L2 Access Nodes section is where you set up links with L2 (Ethernet) access nodes. NPCs are involved.

See the appropriate section, depending on which type of link you are setting up:

•Setting Direct Connect Links

•Setting Links with L2 Access Nodes

Note Many of steps for setting up the two link types are the same. The basic workflow for setting up links, as well as the attributes to be set, are presented in the section Setting Direct Connect Links. Even if you are setting up links with L2 access nodes, it will be helpful to refer to the information presented in that section, as the section on L2 access nodes only covers the unique steps for such links.

Setting Direct Connect Links

To set up the direct connect links, perform the following steps. Most of these steps apply to links with L2 access nodes also.

Step 1 Click Add to add a link.

A new numbered row for the link attributes appears.

Step 2 Click Select NPE in N-PE column.

The Select PE Device window appears. This window displays the list of currently defined PEs.

a. The Show PEs with drop-down list shows PEs by Provider, PE Region Name, or by Device Name.

b. The Find button allows a search for a specific PE or a refresh of the window.

c. The Rows per page drop-down list allows the user to configure the number of entries displayed on the screen at one time.

Step 3 In the Select column, choose the PE device name for the link.

Step 4 Click Select.

The EVC Service Request Editor window reappears displaying the name of the selected PE in the N-PE column.

Step 5 Choose the UNI interface from the drop-down list in the UNI column.

Note Prime Fulfillment only displays the available interfaces for the service, based on the configuration of the underlying interfaces, existing service requests that might be using the interface, and the customer associated with the service request. You can click the Detail button to display a pop-up window with information on the available interfaces, such as interface name, customer name, VPN name, job ID, service request ID, service request type, translation type, and VLAN ID information.

Note When the UNI is configured on an N-PE device running IOS XR, the Standard UNI Port attribute is not supported. All the CLIs related to Standard UNI Port and UNI Port Security are ignored in this case.

Step 6 Check the EVC check box to mark the link for configuring service instance for the links.

Note The EVC check box is mentioned at this stage because the setting of the check box alters the behavior of the link editing function available in the Link Attributes column. This is covered in the next steps.

Note The EVC check box is unchecked by default. The default value for the check box can be changed by setting the value of the DCPL property Pr ovisioning\ProvDrv\CheckFlexUniCheckBox.

Editing the Link Attributes

The next steps document the use of the Edit link in the Link Attributes column. (In the case where the link attributes have already been set, this link changes from Edit to Change.) The link editing workflow changes depending on the status of the EVC check box for the link. If the EVC check box is checked, the editing workflow involves setting attributes in two windows, for two sets of link attributes:

•The EVC Details

•Standard UNI Details

If the EVC check box for the link is not checked, only the Standard UNI Details window is presented.

In the steps that follow, both scenarios covered.

Step 7 Click Edit in the Link Attributes column to specify the UNI attributes.

EVC Details Window

If the EVC check box is checked, the EVC Details window appears.

All of the fields in the EVC Details screen are enabled based on the policy settings. For example, if Both Tags is selected in the policy and is editable, then the Match Inner and Outer Tags check box will be selected and editable in this window. The behavior is similar for the other attributes in the EVC Details window

Step 8 Check the AutoPick Service Instance ID check box to specify that the service instance ID will be autogenerated and allocated to the link during service request creation.

If the check box is unchecked, you must specify the service instance ID (see the next step).

Usage notes:

•The service instance ID represents an Ethernet Flow Point (EFP) on an interface in the EVC infrastructure. The service instance ID is locally significant to the interface. This ID has to be unique only at the interface level. The ID must be a value from 1 to 8000.

•There are no resource pools available in Prime Fulfillment from which to allocate the service instance IDs.

•In the case of a manually provided service instance ID, it is the responsibility of the operator to maintain the uniqueness of the ID at the interface level.

•This attribute is not displayed for IOS XR devices.

Step 9 If the AutoPick Service Instance ID check box is not checked, enter an appropriate value for the service instance ID in the Service Instance ID field.

This attribute is not displayed for IOS XR devices.

Step 10 Check the AutoPick Service Instance Name check box to specify that the service instance name will be autogenerated.

If the check box is unchecked, you can specify the service instance name (see the next step).

Usage notes:

•If the check box is checked, the Service Instance Name text field is disabled.

•The service instance name is autogeneratedi n the following pattern: CustomerName_ServiceRequestJobID.

•For example configlets, see EVC (AutoPick Service Instance Name), EVC (User-Provided Service Instance Name, Pseudowire Core Connectivity), and EVC (User-Provided Service Instance Name, Local Core Connectivity).

•This attribute is not displayed for IOS XR devices.

Step 11 If the AutoPick Service Instance Name check box is not checked, enter an appropriate value for the service instance ID in the Service Instance Name field.

Usage notes:

•The text string representing the service instance name must be 40 characters or less and contain no spaces. Other special characters are allowed.

•If AutoPick Service Instance Name is unchecked and no service instance name is entered in the text field, then Prime Fulfillment does not generate the global ethernet evc evcname command in the device configuration generated by the service request.

Step 12 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID for the service request during service request creation.

If this check box is unchecked, the you must specify a bridge domain VLAN ID (see the next step).

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

Step 13 If the AutoPick Bridge Domain/VLAN ID check box is unchecked, enter an appropriate value in the Bridge Domain/VLAN ID field.

Note This configuration applies in conjunction with the Configure Bridge Domain option in the EVC Service Request Editor window. If the option is not enabled in that window, then AutoPick Bridge Domain/VLAN ID check box is redundant and not required.

When a VLAN ID is manually allocated, Prime Fulfillment verifies the VLAN ID to see if it lies within Prime Fulfillment's VLAN ID pool. If the VLAN ID is in the pool but not allocated, the VLAN ID is allocated to the service request. If the VLAN ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VLAN ID. If the VLAN ID lies outside of the Prime Fulfillment VLAN ID pool, Prime Fulfillment does not perform any verification about whether the VLAN ID allocated. The operator must ensure the VLAN ID is available.

Step 14 Check the AutoPick Bridge Domain/VLAN ID Secondary N-PE check box to have Prime Fulfillment autopick the bridge domain VLAN ID for the secondary N-PE of a dual-homed ring during service request creation.

If this check box is unchecked, the you must specify a secondary bridge domain VLAN ID for the secondary N-PE (see the next step).

Usage notes:

•This attribute is only applicable in the case of a dual-homed ring (a ring that terminates on two different N-PEs). Prime Fulfillment supports having a separate bridge domain VLAN ID for the secondary N-PE.

•In a dual-homed ring, if the two N-PEs are in different access domains, Prime Fulfillment allocates the bridge domain VLAN IDs from both primary and secondary N-PE access domains. When both are in the same Access Domain, Prime Fulfillment allocates a common VLAN ID from the Access Domain to which these belong.

•AutoPick Bridge Domain/VLAN ID Secondary N-PE consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

•This attribute is not displayed for IOS XR devices.

Step 15 If the AutoPick Bridge Domain/VLAN ID Secondary N-PE check box is unchecked, enter an appropriate value in the Bridge Domain/VLAN ID Secondary N-PE field.

Step 16 Check the Match Inner and Outer Tags check box to enable service requests created with the policy to match both the inner and outer VLAN tags of the incoming frames.

If you do not check this check box, service requests created with the policy will match only the outer VLAN tag of the incoming frames.

Checking the Match Inner and Outer Tags attribute causes the Inner VLAN ID and Outer VLAN ID fields (covered in the next steps) to appear.

Step 17 If the Match Inner and Outer Tags check box is checked, enter the inner and outer VLAN tags in the Inner VLAN ID and Outer VLAN ID fields.

Usage notes:

•You can specify single values, single ranges, multiples values, multiple ranges, or combinations of these. Examples:

–10

–10, 15,17

–10-15

–10-15,17-20

–10,20-25

•If the Inner VLAN Ranges attribute is set to true in the policy, the Inner VLAN ID field can take a range of inner VLAN tags.

•If the Outer VLAN Ranges attribute is set to true in the policy, the Outer VLAN ID field can take a range of Outer VLAN tags.

Step 18 If the Match Inner and Outer Tags check box is unchecked, enter the outer VLAN tag in the Outer VLAN ID field.

Note The VLAN specified in Outer VLAN ID will be provisioned on the rest of the L2 access nodes (if the link has any), including the customer-facing UNI.

Note You may also have Prime Fulfillment autopick the outer VLAN ID as covered in the next step.

Step 19 Check the AutoPick Outer VLAN check box to have Prime Fulfillment autopick the outer VLAN ID from a previously created outer VLAN ID resource pool.

If this check box is unchecked, the operator will be prompted to specify an outer VLAN ID.

Note Use of the AutoPick Outer VLAN attribute requires that two elements have already been set up in Prime Fulfillment. One is an Interface Access Domain, which is a logical element that groups the physical ports of an N-PE device. The other is an EVC Outer VLAN resource pool, which is used by the Interface Access Domain. For instructions on how to set up these elements, see the sections Setting Up Resources, and Resource Pools.

Usage notes:

•AutoPick Outer VLAN can be used for interfaces that support EVC functionality

•AutoPick Outer VLAN consumes a VLAN ID on the interface that supports EVC.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

Step 20 In the VLAN Rewrite section of the window, choose a Rewrite Type from the drop-down list.

The choices are:

•Pop

•Push

•Translate

The subsequent attributes in the GUI change depending on the choice of Rewrite Type, as covered in the next steps.

Step 21 If Pop is the Rewrite Type, two check boxes appear:

a. Check the Pop Outer Tag check box to pop the outer VLAN ID tag of the incoming frames that fulfill the match criteria. If this check box is unchecked, the outer tag of the incoming traffic will not be popped.

b. Check the Pop Inner Tag check box to pop the inner VLAN ID tag of the incoming frames that fulfill the match-criteria. If this check box is unchecked, the inner tag will not be changed.

Note that if Pop Inner Tag is checked, Pop Outer Tag is automatically checked.

Step 22 If Push is the Rewrite Type, two text boxes appear:

a. In the text box Outer VLAN ID, enter an outer VLAN ID tag that will be imposed on the incoming frames that fulfill the match criteria. All service requests created with this setting push a dot1q outer tag on the incoming frames matching the match criteria. If a value is not provided, the push operation is ignored and not configured on the device.

b. In the text box Inner VLAN ID, enter an inner VLAN ID tag that will be imposed on the incoming frames that fulfill the match criteria. All service requests created with this setting push a dot1q inner tag on the incoming frames matching the match criteria. The Inner VLAN tag cannot be pushed without an Outer VLAN tag. That is, when pushing an Inner VLAN tag, the Outer VLAN tag also must be defined.

Step 23 If Translate is the Rewrite Type, a Translation Type drop-down list appears.

The choices available in this list vary depending on the setting of the Match Inner and Outer Tags attribute (set in a previous step).

a. If the Match Inner and Outer Tags check box is checked (true), choose a translation type of 1:1, 1:2, 2:1, or 2:2 from the Translation Type drop-down list.

–If you choose 1:1 or 2:1, enter a value in the Outer VLAN ID text box that appears. The outer tag of all the incoming frames that fulfill the match criteria will be translated to this ID.

–If you choose 1:2 or 2:2, enter values in the Outer VLAN ID and Inner VLAN ID text boxes that appear. The outer and inner tags of all the incoming frames that fulfill the match criteria will be translated to these IDs.

b. If the Match Inner and Outer Tags check box is unchecked (false), choose a translation type of 1:1 or 1:2 from the Translation Type drop-down list.

–If you choose 1:1, enter a value in the Outer VLAN ID text box that appears. The outer tag of all the incoming frames that fulfill the match criteria will be translated to this ID.

–If you choose 1:2, enter values in the Outer VLAN ID and Inner VLAN ID text boxes that appear. The outer and inner tags of all the incoming frames that fulfill the match criteria will be translated to these IDs.

Step 24 Clicked Next to save the settings in the EVC Details window.

The Standard UNI Details window appears.

Step 25 Continue with setting the standard UNI link attributes in the next steps.

Editing the Standard UNI Attributes

The following steps cover setting the attributes in the Standard UNI Details window. In the case of a link which is not set as an EVC link (by not checking the EVC check box in the EVC Service Request Editor window), editing the link attributes begins with this window.

Note The attributes that appear in the Standard UNI Details window are dynamically configured by Prime Fulfillment. Some of the attributes covered in the steps below might not appear in the window, depending on the policy and service request settings or the link type. For example, if the MPLS core connectivity type of the EVC policy is VPLS or local, the pseudowire-related attributes will not appear. Also, setting the link as EVC or non-EVC will change the attributes that appear in the window. In addition, attributes are filtered based on device type (IOS or IOS XR). These and other cases are noted in the steps, for reference.

Step 26 The N-PE/U-PE Information and Interface Name fields display the PE device and interface name selected in previous steps.

These fields are read-only.

Step 27 Choose an Encapsulation type from the drop-down list.

The choices are:

•DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation. If the UNI belongs to a directly connected and EVC link, this setting signifies that the incoming frames are 802.1q encapsulated and that they match the VLAN ID configured for the link. This specific topology does not involve a trunk UNI as such.

•DOT1QTUNNEL—Configures the UNI as an 802.1q tunnel (also known as a dot1q tunnel or Q-in-Q) port.

•ACCESS—Configures the UNI as an access port.

This attribute allows you to deploy different types of UNI encapsulation on different links of a service.

Usage notes:

•When a U-PE running with IOS is added in the same circuit terminating on an ASR 9000 (functioning in an N-PE role), the all three encapsulation types values will be visible in the drop-down list of the Encapsulation attribute.

•DOT1QTUNNEL is not directly supported for ASR 9000 devices.

•In the case of direct connect links for which EVC is enabled (by checking the EVC check box in the EVC Service Request Editor window), the choices for the Encapsulation type are DOT1Q and DEFAULT.

Step 28 In the PE/UNI Interface Description field, enter a description for the interface, if desired.

Step 29 Check the UNI Shutdown check box if you want to leave the UNI port shut during service activation (for example, when the service provider wants to deploy a service in the network but wants to activate it at a later time).

Step 30 Specify the type of VLAN Translation for the service request by clicking the appropriate radio button.

The choices are:

•No—No VLAN translation is performed. (This is the default.)

•1:1—1:1 VLAN translation.

•2:1—2:1 VLAN translation.

•1:2—1:2 VLAN translation.

•2:2—2:2 VLAN translation.

Usage notes:

•The VLAN Translation attribute does not appear for direct connect links if the EVC check box is enabled. It does appear for the following combinations:

–Direct connect links with EVC check box disabled.

–L2 access nodes with EVC check box enabled or disabled.

•Choosing a selection other than No causes other fields to appear in the GUI, which you can set based on your configuration:

–CE VLAN—Provide a value between 1 and 4096.

–Auto Pick—Check this check box to have Prime Fulfillment autopick the outer VLAN from the VLAN resource pool.

–Outer VLAN—If Auto Pick is unchecked, provide a value between 1 and 4096.

–Select where 2:1 or 2:2 translation takes place—Specify the device where the 2;1 or 2:2 VLAN translation will take place. If you choose Auto, the VLAN translation takes place at the device closest to the UNI port.

•VLAN translation, and all standard UNI and port security attributes are applicable for links with L2 access. If the UNI is on an N-PE, these attributes will not appear.

•When the VLAN translation takes place on a U-PE or PE-AGG device, the VLAN translation command is configured on the NNI interface of the selected device. When the VLAN translation takes place on an NP-E, the VLAN translation command is configured on the UNI interface of the device.

•When there are two NNI interfaces in a ring-based environment, VLAN translation is applied for both of these NNI interfaces.

•1:1 and 2:1 VLAN translations are supported with the same syntax as for non-EVC (switchport-based N-PE syntax) terminating attachment circuits.

Step 31 Check the N-PE Pseudo-wire on SVI check box to have Prime Fulfillment generate forwarding commands under SVIs (switch virtual interfaces).

By default, this check box is not checked. In this case, Prime Fulfillment generates forwarding commands under the service instance.

For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (this is available in the service request workflow in the EVC Service Request Editor window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE Pseudo-wire on SVI is enabled.

Usage notes:

•For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (in the EVC Service Request Editor window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE pseudo-wire on SVI is enabled.

•Prime Fulfillment supports a hybrid configuration for EVC service requests. In a hybrid configuration, the forwarding commands (such as xconnect) for one side of an attachment circuit can be configured under a service instance, and the xconnect configuration for the other side of the attachment circuit can be configured under a switch virtual interface (SVI).

•N-PE Pseudo-wire on SVI is applicable for all connectivity types (PSEUDOWIRE, VPLS, and LOCAL), but a hybrid SVI configuration is possible only for pseudowire connectivity.

•When MPLS Core Connectivity Type is set as VPLS, the N-PE Pseudo-wire on SVI attribute is always enabled in the policy and service request.

•When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy and service request.

•For examples of these cases, see configlet examples EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) and EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI).

•For additional information on the N-PE Pseudo-wire on SVI attribute, see the corresponding coverage in the EVC policy section in the section Setting the Interface Attributes.

•The N-PE Pseudo-wire on SVI attribute is not supported for IOS XR devices. All the xconnect commands are configured on L2 subinterfaces.

Step 32 Check the PW Tunnel Selection check box if you want to be able to manually select the Traffic Engineering (TE) tunnel for the pseudowire connecting point-to-point N-PEs.

Usage notes:

•Checking the PW Tunnel Selection check box activates the Interface Tunnel attribute field (see the next step).

•This attribute only appears if the MPLS core connectivity type is set as pseudowire in the EVC policy.

•The PW Tunnel Selection attribute is not supported for IOS XR devices.

Step 33 If you checked the PW Tunnel Selection check box, enter the TE tunnel ID in the Interface Tunnel text field.

Usage notes:

•Prime Fulfillment uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs. This pseudowire class can be shared by more than one pseudowire, as long as the pseudowires share the same tunnel ID and remote loopback address. During service request creation, Prime Fulfillment does not check the validity of the tunnel ID number. That is, Prime Fulfillment does not verify the existence of the tunnel.

•The Interface Tunnel attribute is not supported for IOS XR devices.

Step 34 Check the AutoPick Bridge Group Name check box to have Prime Fulfillment autopick the bridge group name during service request creation.

If this check box is unchecked, you are prompted to specify a bridge group name during service request creation (see the next step).

Usage notes:

•This attribute only displays for IOS XR devices.

•If the AutoPick Bridge Group Name check box is unchecked, enter an bridge group name in the Bridge Group Name text field.

•The AutoPick Bridge Group Name and Bridge Group Name attributes only appear if Configure Bridge Domain was enabled in the EVC Service Request Editor window earlier in the service request workflow.

Step 35 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID during service request creation.

If this check box is unchecked, you are prompted to specify a VLAN ID during service request creation (see the next step).

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

•The AutoPick Bridge Domain/VLAN ID attribute appears for both Cisco 7600 and ASR 9000 devices. It will be displayed only for non-EVC links.

Step 36 If the AutoPick Bridge Domain/VLAN ID check box is unchecked, enter an ID number in the Bridge Domain/VLAN ID text field.

Usage notes:

•If AutoPick Bridge Domain/VLAN ID is checked, this field is non-editable.

•When a VLAN ID is manually allocated, Prime Fulfillment verifies the VLAN ID to see if it lies within Prime Fulfillment's VLAN ID pool. If the VLAN ID is in the pool but not allocated, the VLAN ID is allocated to the service request. If the VLAN ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VLAN ID. If the VLAN ID lies outside of the Prime Fulfillment VLAN ID pool, Prime Fulfillment does not perform any verification about whether the VLAN ID allocated. The operator must ensure the VLAN ID is available.

•The Bridge Domain/VLAN ID text field appears for both Cisco 7600 and ASR 9000 devices. It will be displayed only for non-EVC links.

Step 37 Check the AutoPick Bridge Domain Name check box to have Prime Fulfillment autopick the bridge domain name during service request creation.

If this check box is unchecked, you are prompted to specify a bridge domain name during service request creation (see the next step).

Usage notes:

•The AutoPick Bridge Domain Name attribute appears only for Cisco ASR 9000 devices.

•The AutoPick Bridge Domain Name attribute only appears if Configure Bridge Domain was enabled in the EVC Service Request Editor window earlier in the service request workflow.

Step 38 If the AutoPick Bridge Domain Name check box is unchecked, enter a bridge domain name in the Bridge Domain Name text field.

Usage notes:

•Bridge Domain Name field appears only for Cisco ASR 9000 devices.

•The Bridge Domain Name attribute only appears if Configure Bridge Domain was enabled in the EVC Service Request Editor window earlier in the service request workflow.

Step 39 Check the Use PseudoWireClass check box to enable the selection of a pseudowire class.

This attribute is unchecked by default.

Usage notes:

•The pseudowire class name is used for provisioning pw-class commands on IOS XR devices. See Creating and Modifying Pseudowire Classes for additional information on pseudowire class support for IOS XR devices.

•If Use PseudoWireClass is checked, an additional attribute, PseudoWireClass, appears in the GUI. Click the Select button of PseudoWireClass attribute to choose a pseudowire class previously created in Prime Fulfillment.

•The Use PseudoWireClass attribute is only available if the MPLS core connectivity type was set as PSEUDOWIRE in the Service Options window (see Setting the Service Options).

•Use PseudoWireClass is only applicable for IOS XR devices.

•The Use PseudoWireClass and PseudoWireClass attributes only appear if Configure Bridge Domain was not enabled in the EVC Service Request Editor window earlier in the service request workflow.

Step 40 For L2VPN Group Name choose one of the following from the drop-down list:

•ISC

•VPNSC

Usage notes:

•This attribute is used for provisioning the L2VPN group name on IOS XR devices.

Note The choices in the drop-down list are derived from a configurable DCPL property. For information about how to define the L2VPN Group Name choices available in the drop-down list, see Defining L2VPN Group Names for IOS XR Devices.

•The L2VPN Group Name attribute is not available if the MPLS core connectivity type was set as VPLS in the Service Options window (see Setting the Service Options).

•L2VPN Group Name is only applicable for IOS XR devices.

•The L2VPN Group Name attribute only appears if Configure Bridge Domain was not enabled in the EVC Service Request Editor window earlier in the service request workflow.

Step 41 Enter an E-Line Name to specify the point-to-point (p2p) E-line name.

Usage notes:

•If no value is specified for the E-Line Name, Prime Fulfillment autogenerates a default name as follows:

–For PSEUDOWIRE core connectivity type, the format is:

DeviceName--VC_ID

–For LOCAL core connectivity type, the format is:

DeviceName--VLAN_ID

If the default name is more than 32 characters, the device names are truncated.

•The E-Line Name attribute is not available if the MPLS core connectivity type was set as VPLS in the Service Options window (see Setting the Service Options).

•E-Line Name is only applicable for IOS XR devices.

•The E-Line Name attribute only appears if Configure Bridge Domain was not enabled in the EVC Service Request Editor window earlier in the service request workflow.

Step 42 Click OK to save the Standard UNI settings and return to the EVC SR window.

The value in the Link Attributes column now displays as "Changed," signifying that the link settings have been updated. You can edit the link attributes now or at a future time by clicking on the Changed link and modifying the settings in the Standard UNI Details window.

See Modifying the EVC Service Request for details on editing the link attributes.

Step 43 To add another link click the Add button and set the attributes for the new link as in the previous steps in this section.

Step 44 To delete a link, check the check box in the first column of the row for that link and click the Delete button.

Step 45 If you want to set up links with L2 access nodes for this service request, see Setting Links with L2 Access Nodes.

Step 46 When you have completed setting the attributes in the EVC Service Request Editor window, click the Save button at the bottom of the window to save the settings and create the EVC service request.

If any attributes are missing or incorrectly set, Prime Fulfillment displays a warning in the lower left of the window. Make any corrections or updates needed (based on the information provided by Prime Fulfillment), and click the Save button.

For information on modifying an EVC service request see the section Modifying the EVC Service Request. For additional information about saving an EVC service request, see Saving the EVC Service Request.

Setting Links with L2 Access Nodes

The Links with L2 Access Nodes section of the EVC Service Request Editor window allows you to set up links with L2 (Ethernet) access nodes. These are similar to direct connect links, except that they have L2/Ethernet access nodes beyond the N-PE (towards the CE). Therefore, NPCs are involved. The steps for setting up links with L2 access nodes are similar to those covered in the section Setting Direct Connect Links. See that section for detailed steps on the following common operations:

•Adding and deleting links.

•Selecting the N-PE.

•Choosing the UNI interface.

•Setting the link as an EVC link.

•Editing the standard and EVC link attributes.

The main difference in setting up links with L2 access does is specifying the NPC details.

To set the NPC details for links with L2 access nodes, perform the following steps.

Step 1 The first step in the process of adding a link using NPCs is selecting the U-PE/PE-AGG device, rather than the N-PE.

If only one NPC exists for the chosen interface, that NPC is autopopulated in the Circuit Details column, and you need not choose it explicitly.

If more then one NPC is available, click Select one circuit in the Circuit Selection column. The NPC window appears, enabling you to choose the appropriate NPC.

Step 2 Click OK.

Each time you choose a PE and its interface, the NPC that was set up from this PE and interface is automatically displayed under Circuit Selection. This means that you do not have to further specify the PE to complete the link.

If you want to review the details of this NPC, click Circuit Details in the Circuit Details column. The NPC Details window appears and lists the circuit details for this NPC.

Step 3 For details about editing link attributes, adding or deleting links, or using the EVC check box, see the corresponding steps in the section Setting Direct Connect Links.

Step 4 When you have completed setting the attributes in the EVC Service Request Editor window, click the Save button at the bottom of the window to save the settings and create the EVC service request.

If any attributes are missing or incorrectly set, Prime Fulfillment displays a warning in the lower left of the window. Make any corrections or updates needed (based on the information provided by Prime Fulfillment), and click the Save button.

For information on modifying an EVC service request see the section Modifying the EVC Service Request. For additional information about saving an EVC service request, see Saving the EVC Service Request.

Modifying the EVC Service Request

You can modify an EVC service request if you must change or modify the links or other settings of the service request.

To modify an EVC service request, perform the following steps.

Step 1 Choose Operate > Service Requests > Service Request Manager.

The Service Request Manager window appears, showing service requests available in Prime Fulfillment.

Step 2 Check a check box for a service request.

Step 3 Click Edit.

EVC Service Request Editor window appears.

Step 4 Modify any of the attributes, as desired.

See the sections start with "Setting the Service Request Details" section for detailed coverage of setting attributes in this window.

Note Once the VC ID, VPLS VPN ID, and VLAN ID have been set in a service request they cannot be modified.

Step 5 To add a template/data file to an attachment circuit, see the section Using Templates and Data Files with an EVC Ethernet Service Request.

Step 6 When you are finished editing the EVC service request, click Save.

For additional information about saving an EVC service request, see Saving the EVC Service Request.

Using Templates and Data Files with an EVC Ethernet Service Request

Prime Fulfillment does not support configuration of all the available CLI commands on a device being managed by the application. In order to configure such commands on the devices, you can use Prime Fulfillment Template Manager functionality. Templates can be associated at the policy level on a per-device role basis. Templates can be overridden at service request level, if the policy-level setting permits the operator to do so.

To associate templates and data files in a service request select any link in the Service Request Editor window and click the Template button at the bottom of the window.

Note If the template feature has not been enabled in the associated policy then the Template button will not be available for selection.

The SR Template Association window appears. In this window, you can associate templates at a per-device level. The SR Template Association window lists the devices comprising the link, the device roles, and the template(s)/data file(s) associated with the devices. In this case, the template(s)/data file(s) have not yet been set up.

For further instructions on how to associate templates and data files with a service request, see Using Templates with Service Requests.

Saving the EVC Service Request

To save an EVC Ethernet service request, perform the following steps.

Step 1 When you have finished setting the attributes for the EVC Ethernet service request, click Save to create the service request.

If the EVC service request is successfully created, you will see the Service Request Manager window. The newly created EVC Ethernet service request is added with the state of REQUESTED.

Step 2 If, however, the EVC Ethernet service request creation failed for some reason (for example, a value chosen is out of bounds), you are warned with an error message.

In such a case, you should correct the error and save the service request again.

Step 3 If you are ready to deploy the EVC Ethernet service request, see Deploying Service Requests.

Creating an EVC ATM-Ethernet Interworking Policy

This section contains an overview of EVC ATM-Ethernet Interworking support in Prime Fulfillment, as well as the basic steps to create an EVC ATM-Ethernet Interworking policy. It contains the following subsections:

•Defining the EVC Ethernet Policy

•Setting the Service Options

•Setting the ATM Interface Attributes

•Setting the EVC Attributes

•Setting the Interface Attributes

•Enabling Template Association

For information on creating EVC ATM-Ethernet service requests, see Managing an EVC ATM-Ethernet Interworking Service Request.

Note For a general overview of EVC support in Prime Fulfillment, see the chapter "Layer 2 Concepts" in the Cisco Prime Fulfillment Theory of Operations Guide 6.2.

Defining the EVC ATM-Ethernet Interworking Policy

You must define an EVC ATM-Ethernet Interworking policy before you can provision a service. A policy can be shared by one or more service requests that have similar service requirements.

A policy is a template of most of the parameters needed to define an EVC service request. After you define it, an EVC policy can be used by all the EVC service requests that share a common set of characteristics. You create a new EVC policy whenever you create a new type of service or a service with different parameters. EVC policy creation is normally performed by experienced network engineers.

To define an EVC ATM-Ethernet Interworking policy, you start by setting the service type attributes. To do this, perform the following steps.

Step 1 Choose Service Design > Policies > Policy Manager.

The Policy Manager window appears.

Step 2 Click Create.

The Policy Editor window appears.

Step 3 Choose EVC from the Policy Type drop-down list.

The Policy Editor window appears.

Step 4 Enter a Policy Name for the EVC ATM-Ethernet Interworking policy.

Step 5 Choose the Policy Owner for the EVC policy.

There are three types of EVC policy ownership:

•Customer ownership

•Provider ownership

•Global ownership—Any service operator can make use of this policy.

This ownership has relevance when the Prime Fulfillment Role-Based Access Control (RBAC) comes into play. For example, an EVC policy that is customer-owned can only be seen by operators who are allowed to work on this customer-owned policy. Similarly, operators who are allowed to work on a provider's network can view, use, and deploy a particular provider-owned policy.

Step 6 Click Select to choose the owner of the EVC policy.

The policy owner was established when you created customers or providers during Prime Fulfillment setup. If the ownership is global, the Select function does not appear.

Step 7 Choose the Policy Type.

The choices are:

•ETHERNET

•ATM-Ethernet Interworking

Note This section describes creating the ATM-Ethernet Interworking policy type. For information on using the EVC ETHERNET policy type, see Creating an EVC Ethernet Policy.

Step 8 Click Next.

The Service Options window appears.

Step 9 Continue with the steps contained in the next section, Setting the Service Options.

Setting the Service Options

This section describes how to set the service options for the EVC policy.

To set the EVC service options, perform the following steps.

Step 1 Check the CE Directly Connected to EVC check box if the CEs are directly connected to the N-PE.

This check box is not checked by default.

Note The Editable check box gives you the option of making a field editable. If you check the Editable check box, the service operator who is using this EVC policy can modify the editable parameter during EVC service request creation.

Usage notes:

•If the check box is checked, a service request created using this policy can have only directly connected links. No Ethernet access nodes will be involved.

•If the check box is unchecked, a service request created using this policy might or might not have Ethernet access nodes in the links.

•When a CE is directly connected to the N-PE, NPCs are not applicable to the link while creating service requests.

•When a CE is not directly connected to the N-PE, NPCs are used during service request creation, as per standard Prime Fulfillment behavior. There is no change in NPC implementation to support EVC functionality.

Step 2 Check the All Links Terminate on EVC check box if all links need to be configured with EVC features.

This check box is not check by default. Usage notes:

•If the check box is checked, a service request created using such policy will have all links using the EVC feature.

•If the check box is unchecked, zero or more links can use the EVC feature. This ensures that existing platforms can still be used in one or more links while delivering the services. This allows the possibility of a link with EVC support being added in the future.

Note If the check box is unchecked, in the service request creation process the user must indicate whether or not the created link is EVC or non-EVC.

•If no links are expected to use the EVC feature even in the future (for example, if the provider is not planning to upgrade to the EVC infrastructure for the service that is being created), existing Prime Fulfillment policy types (L2VPN or VPLS) can be used instead of EVC.

Step 3 Choose an MPLS Core Connectivity Type from the drop-down list.

Note The core option supports MPLS only. There is no L2TPv3 support for this service.

The choices are:

•PSEUDOWIRE—Choose this option to allow connectivity between two N-PEs across the MPLS core. This option does not limit the service to point-to-point (E-Line). This is because even with the PSEUDOWIRE option selected, there can still be multiple CEs connected to a bridge domain on one or both sides of the pseudowire.

•LOCAL—Choose this option for local connect cases in which there is no connectivity required across the MPLS core.

Local connect supports the following scenarios:

–All interfaces on the N-PE are EVC-capable and using the EVC infrastructure. This is configured by associating all of the customer traffic on these interfaces to a bridge domain. This consumes a VLAN ID on the N-PE (equal to the bridge domain ID).

–Some interfaces on the N-PE are EVC-capable, while others are switch-port-based. In such cases, all of the customer traffic on the interfaces that are configured with the EVC infrastructure are associated to a bridge domain. The traffic on the non-EVC interfaces (and all the access nodes/interfaces beyond this N-PE) are configured with the Service Provider VLAN ID, where the Service Provider VLAN ID is the same as the bridge domain ID for the EVC-based services.

–Only two interfaces on the N-PE are involved, and both are based on EVC-capable line cards. In the first case, the operator might choose not to configure the bridge domain option. In this case, the connect command that is used for the local connects are used, and the global VLAN is conserved on the device. If the operator chooses to configure with the bridge domain option, both interfaces are associated to a bridge domain ID, so that additional local links can be added to the service in future. This consumes a VLAN ID (bridge domain ID) on the N-PE.

•VPLS—This option is not supported for EVC ATM-Ethernet Interworking policies and services requests.

Note Attributes available in subsequent windows of the policy workflow dynamically change based on the choice made for the MPLS Core Connectivity Type (PSEUDOWIRE or LOCAL). For completeness, all attributes available for the different core types are documented in the following steps. Attributes apply to all core types, unless otherwise noted.

Note Also, some attributes are supported only on IOS or IOS XR platforms. Attributes apply to both platforms, unless otherwise noted. All platform-specific attributes are visible in the policy workflow windows. Later, when a service request is created based on the policy (and specific devices are associated with the service request), platform-specific attributes are filtered from service request windows, depending on the device type (IOS or IOS XR).

Step 4 Check the Configure With Bridge Domain check box to determine bridge domain characteristics.

The behavior of the Configure With Bridge-Domain option works in tandem with the choice you selected in the MPLS Core Connectivity Type option, as follows.

•PSEUDOWIRE as the MPLS Core Connectivity Type. There are two cases:

A. With EVC:

–If Configure With Bridge Domain is checked, the policy configures pseudowires under SVIs associated to the bridge domain.

–If Configure With Bridge Domain is unchecked, the policy will configure pseudowires directly under the service instance. This conserves the global VLAN.

B. Without EVC:

–If Configure With Bridge Domain is checked, the policy configures pseudowires as in L2VPN services (with SVIs).

–If Configure With Bridge Domain is unchecked, the policy configures pseudowires directly under subinterfaces.

Only pseudowires can be either configured directly under service instance of the corresponding EVC-capable interface or under SVIs associated to the bridge domain.

•LOCAL as the MPLS Core Connectivity Type:

–If Configure With Bridge Domain is checked, the policy allows either point-to-point or multipoint local connect services.

–If Configure With Bridge Domain is unchecked, Prime Fulfillment allows only point-to-point local connects without bridge domain.

Step 5 Click Next.

ATM Interface Attribute window appears.

Step 6 Continue with the steps contained in the next section, Setting the ATM Interface Attributes.

Setting the ATM Interface Attributes

This section describes how to set the ATM Interface attributes for the EVC ATM-Ethernet Interworking policy.

To set the ATM interface attributes, perform the following steps.

Step 1 Choose the Transport Mode from the drop-down list.

The choices are:

•VP—Virtual path mode. This is the default.

•VC—Virtual circuit mode.

Step 2 Choose the ATM Encapsulation from the drop-down list.

•AAL5SNAP

Step 3 Click Next.

The EVC Attribute window appears.

Step 4 Continue with the steps contained in the next section, Setting the EVC Attributes.

Setting the EVC Attributes

This section describes how to set the EVC attributes for the EVC ATM-Ethernet Interworking policy.

EVC attributes are organized under the following categories:

•Service Attributes

•VLAN Match Criteria

•VLAN Rewrite Criteria

The following sections describe how to set the options under each category.

Setting the Service Attributes

To set the EVC service attributes, perform the following steps.

Step 1 Check the AutoPick Service Instance ID check box to specify that the service instance ID will be autogenerated and allocated to the link during service request creation.

If the check box is unchecked, while setting the Prime Fulfillment link attributes during service request creation, Prime Fulfillment will prompt the operator to specify the service instance ID.

Usage notes:

•The service instance ID represents an Ethernet Flow Point (EFP) on an interface in the EVC infrastructure. The service instance ID is locally significant to the interface. This ID has to be unique only at the interface level. The ID must be a value from 1 to 8000.

•There are no resource pools available in Prime Fulfillment from which to allocate the service instance IDs.

•It is the responsibility of the operator creating the service request to maintain the uniqueness of the ID at the interface level.

Step 2 Check the AutoPick Service Instance Name check box to have Prime Fulfillment autogenerate a service instance name when you create a service request based on the policy. The autogenerated value is in the following pattern: CustomerName_ServiceRequestJobID.

If the check box is unchecked, then you can enter a value during service request creation.

Step 3 Check the Enable PseudoWire Redundancy check box to enable pseudowire redundancy (alternative termination device) under certain conditions.

Usage notes:

•Enable Pseudo Wire Redundancy is only available if the MPLS Core Connectivity Type was set as PSEUDOWIRE in the Service Options window (see Setting the Service Options).

Step 4 Check the AutoPick VC ID check box to have Prime Fulfillment autopick the VC ID during service request creation.

If this check box is unchecked, the operator will be prompted to specify a VC ID during service request creation.

Usage notes:

•When AutoPick VC ID is checked, Prime Fulfillment allocates a VC ID for pseudowires from the Prime Fulfillment-managed VC ID resource pool.

Step 5 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID for the service request during service request creation.

If this check box is unchecked, the operator will be prompted to specify a VLAN ID during service request creation.

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain/VLAN ID is picked from the existing Prime Fulfillment VLAN pool. Once the VLAN ID is assigned in the service request, Prime Fulfillment makes the VLAN ID unavailable for subsequent service requests.

•In the case of manual VLAN ID allocation, Prime Fulfillment does not manage the VLAN ID if the ID lies outside the range of an Prime Fulfillment-managed VLAN pool. In this case, the operator must ensure the uniqueness of the ID in the Ethernet access domain. If an operator specifies a VLAN ID that is within the range of an Prime Fulfillment-managed VLAN pool and the VLAN ID is already in use in the access domain, Prime Fulfillment displays an error message indicating that the VLAN ID is in use.

Note on Access VLAN IDs

An access VLAN ID is of local significance to the EVC-capable ports. It should not be confused with the global VLANs. This can be visualized as a partitioning of the Ethernet access network beyond the EVC ports into several subEthernet access domains (one each for an EVC-capable port).

However, all the service interfaces on the Ethernet access nodes beyond the EVC ports will have this very same VLAN ID for a link. This ID must be manually specified by the operator when setting the link attributes during service request creation. The operator must ensure the uniqueness of the ID across the EVC-demarcated Ethernet access domain.

These VLAN IDs are not managed by Prime Fulfillment by means of locally-significant VLAN pools. But once a VLAN ID is assigned for a link in the service request, Prime Fulfillment makes the VLAN unavailable for subsequent service requests within the Ethernet access domain demarcated by the EVC. Likewise, if a manually-specified VLAN is already in use in the access domain delimited by the EVC, Prime Fulfillment will display an error message indicating that the new VLAN ID being specified is already in use on the NPC. The operator will be prompted to specify a different VLAN ID, which will be provisioned on the L2 access nodes.

Step 6 Continue with the steps contained in the next section, Setting the VLAN Matching Criteria Attributes.

Setting the VLAN Matching Criteria Attributes

Prior to the introduction of the EVC capability, service providers could either deploy service-multiplexed services (ERS/ERMS or EVPL/EVCS) or service-bundled services on a single port. Both could not be supported simultaneously due to the limitations in the infrastructure, which only allowed matching the outer-most VLAN tag.

One of the key benefits of EVC support in Prime Fulfillment is to provide a flexible means to examine the VLAN tags (up to two levels) of the incoming frames and associate them to appropriate Ethernet Flow Points (EFPs). This allows service providers to deploy simultaneously both the service-multiplexed and service-bundled services on a single port.

To set the EVC VLAN matching criteria attributes, perform the following steps.

Step 1 Check the Both Tags check box to enable service requests created with the policy to match both the inner and outer VLAN tags of the incoming frames.

If you do not check this check box, service requests created with the policy will match only the outer VLAN tag of the incoming frames.

Checking the Both Tags attribute causes the Inner VLAN Ranges attribute (covered in the next steps) to appear in the EVC Attribute window.

Step 2 Check the Inner VLAN Ranges check box to enable the range of inner VLAN tags to be specified during service request creation.

If the check box is unchecked, the range of inner VLAN tags are not allowed. In this case, the operator must specify discrete VLAN IDs during service request creation.

Step 3 Check the Outer VLAN Ranges check box to enable the range of outer VLAN tags to be specified during service request creation.

If the check box is unchecked, the range of outer VLAN tags are not allowed. In this case, the operator must specify discrete VLAN IDs during service request creation.

Step 4 Check the AutoPick Outer VLAN check box to have Prime Fulfillment autopick the outer VLAN ID from a previously created outer VLAN ID resource pool during service request creation.

If this check box is unchecked, the operator will be prompted to specify an outer VLAN ID during service request creation.

Note Use of the AutoPick Outer VLAN attribute requires that two elements have already been set up in Prime Fulfillment. One is an Interface Access Domain, which is a logical element that groups the physical ports of an N-PE device. The other is an EVC Outer VLAN resource pool, which is used by the Interface Access Domain. For instructions on how to set up these elements, see the sections Setting Up Resources, and Resource Pools.

Usage notes:

•AutoPick Outer VLAN can be used for interfaces that support EVC functionality.

•AutoPick Outer VLAN consumes a VLAN ID on the interface that supports EVC.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

Step 5 Continue with the steps contained in the next section, Setting the VLAN Rewrite Criteria Attributes.

Setting the VLAN Rewrite Criteria Attributes

Together with VLAN matching criteria, VLAN rewrite makes the EVC infrastructure very powerful and flexible. The following VLAN rewrite options are supported:

•Pop one or two tags.

•Push one or two tags.

•Translation (1:1, 2:1, 1:2, 2:2).

Be aware of the following considerations when setting the VLAN rewrite criteria attributes:

•Only one kind of rewrite can be done on every CE-facing EVC link.

•All VLAN rewrites are done using the symmetric keyword on the ingress traffic (for example, rewrite ingress tag pop 2 symmetric).

•For any service instance, only one type of rewrite option (pop, push, or translate) is allowed per instance. For example, if pop out is enabled, push inner, push outer, translate inner, and translate outer are not available.

To set the EVC VLAN rewrite criteria attributes, perform the following steps.

Step 1 Check the Pop Outer check box to pop the outer VLAN ID tag of the incoming frames that fulfill the match criteria.

If this check box is unchecked, the outer tag of the incoming traffic is not popped.

Step 2 Check the Pop Inner check box to pop the inner VLAN ID tag of the incoming frames that fulfill the match-criteria.

If this check box is unchecked, the inner tag is not popped. Note that, if Pop Inner is checked, Pop Outer is automatically checked.

Step 3 Check the Push Outer check box to impose an outer VLAN ID tag onto the incoming frames that fulfill the match criteria.

If this check box is unchecked, no outer tag is imposed on the incoming frames.

Usage notes:

•If Push Outer is checked, all service requests created with the policy push a dot1q outer tag on the incoming frames matching the match criteria. When creating the link during service creation, the operator can specify an outer tag with a value from 1 to 4096.

•This attribute is available regardless of the number of tags used in the match criteria. Whether the incoming traffic is double tagged or single tagged, if Push Outer is enabled, all corresponding service requests push an outer tag. All subsequent nodes consider only the outer-most two tags (if EVC-capable) or just one tag (not EVC-capable) and treat the inner-most tags transparently as payload.

•This VLAN ID is not derived from Prime Fulfillment-managed VLAN ID pools.

Step 4 Check the Push Inner check box to impose an inner VLAN ID tag onto the incoming frames that fulfill the match criteria.

This operation pushes both an inner and an outer tag onto the incoming packet, not just an inner tag. If this check box is unchecked, no inner tag is imposed on the incoming frames.

Usage notes:

•If Push Inner is checked, all service requests created with the policy push a dot1q inner tag on the incoming frames matching the match criteria. When creating the link during service creation, the operator can specify an inner tag with a value from 1 to 4096.

•If Push Inner is checked, Push Outer is automatically checked.

•This attribute is available regardless of the number of tags used in the match criteria. Regardless of whether the incoming traffic is double tagged or single tagged, if Push Inner is enabled, all corresponding service requests push an inner tag. All subsequent nodes consider only the outer-most two tags (if EVC-capable) or just one tag (not EVC-capable) and treat the inner-most tags transparently as payload.

•This VLAN ID is not derived from Prime Fulfillment-managed VLAN ID pools.

Step 5 Check the Translate Outer check box to allow the operator to specify a target outer VLAN ID during service request creation.

The outer tag of all the incoming frames that fulfill the match criteria are translated to this ID. If the check box is unchecked, no outer tag translation is performed. See Table 3-4.

Step 6 Check the Translate Inner check box to allow the operator to specify a target inner VLAN ID during service request creation.

The inner tag of all the incoming frames that fulfill the match criteria are translated to this ID. If the check box is unchecked, no inner tag translation is performed. See Table 3-4.

Note Table 3-4 summarizes the realization of different VLAN translations available in the EVC infrastructure. The second and third columns (Match Outer Tag and Match Inner Tag) refer to policy settings. The last two columns (Translate Outer Tag and Translate Inner Tag) indicate the VLAN translation that occurs on the incoming frames.

[

Step 7 Click Next.

The Interface Attribute window appears.

Step 8 Continue with the steps contained in the next section, Setting the Interface Attributes.

Setting the Interface Attributes

This step of creating the EVC ATM-Ethernet Interworking policy involves setting the interface attributes, as shown in the Interface Attribute window. The attributes you can configure in this window are grouped under the following categories:

•UNI Information

•VLAN

•Pseudowire

•ACL

•Security

•UNI Storm Control

•Protocol

In some cases, checking an attribute causes additional attributes to appear in the GUI. This is covered in the steps that follow.

Note If the CE is directly connected to an N-PE, only speed, duplex, UNI shutdown, and other generic options are presented. In this case, port security, storm control, L2 protocol tunneling, and other advanced features are not supported due to the current platform limitations. If these features are needed for a service, the service provider must deploy Layer 2 Ethernet access nodes beyond the EVC to support these requirements.

Note Attributes available in the Interface Attributes window dynamically change based on the choice made for the MPLS Core Connectivity Type (PSEUDOWIRE or LOCAL) in the Service Options window (see Setting the Service Options). For completeness, all attributes available for the different core types are documented in the following steps. Attributes apply to all core types, unless otherwise noted.

To set the EVC interface attributes, perform the following steps.

Step 1 Check the Standard UNI Port check box to enable port security.

This is the default. When you uncheck the check box, the port is treated as an uplink with no security features, and the window dynamically changes to eliminate items related to port security.

Note When the UNI is configured on an N-PE device running IOS XR, the Standard UNI Port attribute is not supported. All the CLIs related to Standard UNI Port and UNI Port Security are ignored in this case.

Step 2 Check the UNI Shutdown check box if you want to leave the UNI port shut during service activation, for example, when the service provider wants to deploy a service in the network but wants to activate it at a later time.

Step 3 Check the Keep Alive check box to configure keepalives on the UNI port.

By default, this check box is unchecked, which causes the command no keepalive to be provisioned on the UNI port. This prevents a CPE from sending keepalive packets to the U-PE, for security purposes. This attribute is editable, in order to support modification on a per-service request basis.

Step 4 Enter a Link Media (optional) of None, auto-select, rj45, or sfp.

Step 5 Enter a Link Speed (optional) of None, 10, 100, 1000, Auto, or nonegotiate.

Step 6 Enter a Link Duplex (optional) of None, Full, Half, or Auto.

Step 7 Choose an Encapsulation type.

The choices are:

•DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation. If the UNI belongs to a directly connected and EVC link, this setting signifies that the incoming frames are 802.1q encapsulated and that they match the VLAN ID configured for the link. This specific topology does not involve a trunk UNI as such.

•DOT1QTUNNEL—Configures the UNI as an 802.1q tunnel (also known as a dot1q tunnel or Q-in-Q) port.

•ACCESS—Configures the UNI as an access port.

Step 8 Specify the type of VLAN Translation for this policy by clicking the appropriate radio button.

The choices are:

•No—No VLAN translation is performed. (This is the default.)

•1:1—1:1 VLAN translation. Translates an incoming customer VLAN to another.

•2:1—2:1 VLAN translation. Converts both inner and outer VLANs to a single VLAN.

•1:2—1:2 VLAN translation. Pushes one more provider VLAN.

•2:2—2:2 VLAN translation. Translates both inner and outer VLANs to two other VLANs.

Note For more details on how VLAN translation is supported in EVC ATM-Ethernet services, see the coverage of the VLAN Translation attribute in Managing an EVC ATM-Ethernet Interworking Service Request.

Step 9 Check the Use PseudoWireClass check box to enable the selection of a pseudowire class.

This attribute is unchecked by default.

Usage notes:

•The pseudowire class name is used for provisioning pw-class commands on IOS XR devices. See Creating and Modifying Pseudowire Classes for additional information on pseudowire class support for IOS XR devices.

•If Use PseudoWireClass is checked, an additional attribute, PseudoWireClass, appears in the GUI. Click the Select button of PseudoWireClass attribute to choose a pseudowire class previously created in Prime Fulfillment.

•The Use PseudoWireClass attribute is only available if the MPLS core connectivity type was set as PSEUDOWIRE in the Service Options window (see Setting the Service Options).

•Use PseudoWireClass is only applicable for IOS XR devices.

Step 10 For L2VPN Group Name choose one of the following from the drop-down list:

•ISC

•VPNSC

Usage notes:

•This attribute is used for provisioning the L2VPN group name on IOS XR devices.

Note The choices in the drop-down list are derived from a configurable DCPL property. For information about how to define the L2VPN Group Name choices available in the drop-down list, see Defining L2VPN Group Names for IOS XR Devices.

•L2VPN Group Name is only applicable for IOS XR devices.

Step 11 Enter an E-Line Name to specify the point-to-point (p2p) E-line name.

Usage notes:

•If no value is specified for the E-Line Name in either the policy or the service request based on the policy, Prime Fulfillment autogenerates a default name as follows:

–For PSEUDOWIRE core connectivity type, the format is:

DeviceName--VC_ID

–For LOCAL core connectivity type, the format is:

DeviceName--VLAN_ID

If the default name is more than 32 characters, the device names are truncated.

•E-Line Name is only applicable for IOS XR devices.

Step 12 Check the PW Tunnel Selection check box if you want to be able to manually select the Traffic Engineering (TE) tunnel for the pseudowire connecting point-to-point N-PEs.

This attribute is unchecked by default.

Subsequently, when you create a service request based on this policy, you must specify the TE tunnel ID in a field provided. Prime Fulfillment uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs. This pseudowire class can be shared by more than one pseudowire, as long as the pseudowires share the same tunnel ID and remote loopback address. You are responsible to ensure that the tunnel interface and associated ID are configured. During service request creation when you specify the tunnel ID number, Prime Fulfillment does not check the validity of the value. That is, Prime Fulfillment does not verify the existence of the tunnel.

Step 13 Check the N-PE Pseudo-wire on SVI check box to have Prime Fulfillment generate forwarding commands under SVIs (switch virtual interfaces).

By default, this check box is not checked. In this case, Prime Fulfillment generates forwarding commands under the service instance.

For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (this is available in the policy workflow in the EVC Policy Editor - Service Options window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE Pseudo-wire on SVI is enabled.

Usage notes:

•Prime Fulfillment supports a hybrid configuration for EVC service requests. In a hybrid configuration, the forwarding commands (such as xconnect) for one side of an attachment circuit can be configured under a service instance, and the xconnect configuration for the other side of the attachment circuit can be configured under a switch virtual interface (SVI).

•For examples of these cases, see configlet examples EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) and EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI).

•N-PE Pseudo-wire on SVI is applicable for all connectivity types, but a hybrid SVI configuration is possible only for pseudowire connectivity.

•When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy and service request.

•The N-PE Pseudo-wire on SVI attribute is not supported for IOS XR devices. All the xconnect commands are configured on L2 subinterfaces/service instance.

•Table 3-5 shows various use cases for hybrid configuration for EVC service requests.

Step 14 Check the Use Existing ACL Name check box if you want to assign your own named access list to the port.

By default, this check box is not checked and Prime Fulfillment automatically assigns a MAC-based ACL on the customer facing UNI port, based on values you enter in UNI MAC addresses (below).

Step 15 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step).

Note Prime Fulfillment does not create this ACL automatically. The ACL must already exist on the device, or be added as part of a template, before the service request is deployed. Otherwise, deployment will fail.

Step 16 Enter one or more Ethernet MAC addresses in UNI MAC addresses.

This selection is present only if you uncheck the Use Existing ACL Name check box. Click the Edit button to bring up a pop-up window in which you enter MAC addresses to be allowed or denied on the port. You can also specify a range of addresses by setting a base MAC address and a filtered MAC address.

Step 17 Check the UNI Port Security check box if you to want to provision port security-related CLIs to the UNI port by controlling the MAC addresses that are allowed to go through the interface.

a. For Maximum Number of MAC address, enter the number of MAC addresses allowed for port security.

b. For Aging, enter the length of time the MAC address can stay on the port security table.

c. For Violation Action, choose what action will occur when a port security violation is detected:

•PROTECT—Drops packets with unknown source addresses until a sufficient number of secure MAC addresses are removed to drop below the maximum value.

•RESTRICT—Drops packets with unknown source addresses until a sufficient number of secure MAC addresses are removed to drop below the maximum value and causes the Security Violation counter to increment.

•SHUTDOWN—Puts the interface into the error-disabled state immediately and sends an SNMP trap notification.

d. In the Secure MAC Addresses field, enter one or more Ethernet MAC addresses.

Step 18 Check the Enable Storm Control check box to help prevent the UNI port from being disrupted by a broadcast, multicast, or unicast storm.

Enter a threshold value for each type of traffic. The value, which can be specified to two significant digits, represents the percentage of the total available bandwidth of the port. If the threshold of a traffic type is reached, further traffic of that type is suppressed until the incoming traffic falls below the threshold level.

Step 19 Check the Protocol Tunnelling check box if you want to define the Layer 2 Bridge Protocol Data Unit (BPDU) frames that can be tunneled over the core to the other end.

For each protocol that you choose, enter the shutdown threshold and drop threshold for that protocol:

a. Enable cdp—Enable Layer 2 tunnelling on Cisco Discover Protocol (CDP).

b. cdp shutdown threshold—Enter the number of packets per second to be received before the interface is shut down.

c. cdp drop threshold—Enter the number of packets per second to be received at which point the interface will start dropping CDP packets.

d. Enable vtp—Enable Layer 2 tunnelling on VLAN Trunk Protocol (VTP).

e. vtp shutdown threshold—Enter the number of packets per second to be received before the interface is shut down.

f. vtp drop threshold—Enter the number of packets per second to be received at which point the interface will start dropping VTP packets.

g. Enable stp—Enable Layer 2 tunnelling on Spanning Tree Protocol (STP).

h. stp shutdown threshold—Enter the number of packets per second to be received before the interface is shut down.

i. stp drop threshold—Enter the number of packets per second to be received at which point the interface will start dropping STP packets.

j. Recovery Interval—Enter the amount of time, in seconds, to wait before recovering a UNI port.

Step 20 Enter the MTU Size in bytes.

The maximum transmission unit (MTU) size is configurable and optional. The default size is 9216, and the range is 1500 to 9216. Prime Fulfillment does not perform an integrity check for this customized value. If a service request goes to the Failed Deploy state because this size is not accepted, you must adjust the size until the Service Request is deployed.

In Cisco Prime Fulfillment 1.0, different platforms support different ranges.

•For the 3750 and 3550 platforms, the MTU range is 1500 to 1546.

•For the Cisco 7600 Ethernet port, the MTU size is always 9216. Even with the same platform and same IOS release, different line cards support the MTU differently. For example, older line cards only take an MTU size of 9216 and newer cards support 1500 to 9216. However, Cisco Prime Fulfillment 1.0 uses 9216 in both cases.

•For the Cisco 7600 SVI (interface VLAN), the MTU size is 1500 to 9216.

Step 21 If you want to enable template association for this policy, click the Next button.

See the section "Enabling Template Association" section for information about this feature.

Note An additional window appears the policy workflow before the Template Association window. This window allows you to create user-defined attributes within the policy (and service requests based on the policy). For background information on how to use the additional information feature, see "Adding Additional Information to Services." If you are not using this feature, click Next to proceed to the Template Association window, or else click Finish to save the policy.

Step 22 To save the EVC policy, click Finish.

To create a service request based on an EVC ATM-Ethernet Interworking policy, see Managing an EVC ATM-Ethernet Interworking Service Request.

Enabling Template Association

The Prime Fulfillment template feature gives you a means to download free-format CLIs to a device. If you enable templates, you can create templates and data files to download commands that are not currently supported by Prime Fulfillment.

Step 1 To enable template association for the policy, click the Next button in the Interface Attribute window (before clicking Finish).

The Template Association window appears. In this window, you can enable template support and, optionally, associate templates and data files with the policy. For instructions about associating templates with policies and how to use the features in this window, see Using Templates with Service Requests.

Step 2 When you have completed setting up templates and data files for the policy, click Finish in the Template Association window to close it and return to the Policy Editor window.

Step 3 To save the EVC ATM-Ethernet Interworking policy, click Finish.

To create a service request based on an EVCATM-Ethernet Interworking policy, see Managing an EVC ATM-Ethernet Interworking Service Request.

Managing an EVC ATM-Ethernet Interworking Service Request

This section provides information on how to provision an EVC ATM-Ethernet Interworking service request. It contains the following subsections:

•Overview

•Creating an EVC Service Request

•Setting the Service Request Details

•Modifying the EVC Service Request

•Using Templates and Data Files with an EVC Ethernet Service Request

•Saving the EVC Service Request

Overview

An EVC ATM-Ethernet Interworking service request allows you to configure interfaces on an N-PE to support the EVC features described in Creating an EVC ATM-Ethernet Interworking Policy. To create an EVC ATM-Ethernet Interworking service request, an EVC ATM-Ethernet Interworking service policy must already be defined, as described in Creating an EVC ATM-Ethernet Interworking Policy. Based on the predefined EVC policy, an operator creates an EVC service request, with or without modifications to the policy, and deploys the service. One or more templates can also be associated to the N-PE as part of the service request.

ATM-Ethernet interworking is supported through the following configurations:

•ATM Transport Mode (VC)

–ATM-Ethernet Pseudowire

–ATM-ATM Local connect

–ATM-Ethernet Local connect

•ATM Transport Mode (VP)

–ATM-ATM Local connect

The following steps are involved in creating an EVC ATM-Ethernet Interworking service request:

•Choose an existing EVC ATM-Ethernet Interworking policy.

•Choose a VPN.

Note When working with VPN objects in the context of EVC policies and service requests, only the VPN name and customer attributes are relevant. Other VPN attributes related to MPLS and VPLS are ignored.

•Specify a bridge domain configuration (if applicable).

•Specify a service request description.

•Specify automatic or manual allocation of the VC ID or VPLS VPN ID.

•Add direct connect links (if applicable).

•Add links with L2 access nodes (if applicable).

•Choose the N-PE and UNI interface for links.

•For links with L2 access nodes, choose a Named Physical Circuit (NPC) if more than one NPC exists from the N-PE or the UNI interface.

•Edit the link attributes.

•Modify the service request.

•Save the service request.

For sample configlets for EVC ATM-Ethernet Interworking scenarios, see Sample Configlets.

Creating an EVC ATM-Ethernet Interworking Service Request

To create an EVC ATM-Ethernet Interworking service request, perform the following steps.

Step 1 Choose Operate > Service Requests > Service Request Manager.

The Service Request Manager window appears.

Step 2 Click Create.

The Service Request Editor window appears.

Step 3 From the Policy drop-down list, choose an EVC ATM-Ethernet Interworking policy from the policies previously created (see Creating an EVC ATM-Ethernet Interworking Policy).

The EVC Service Request Editor window appears. The new service request inherits all the properties of the chosen EVC ATM-Ethernet Interworking policy, such as all the editable and non-editable features and pre-set parameters.

Step 4 Continue with the steps contained in the next section, Setting the Service Request Details.

Setting the Service Request Details

After you have selected the EVC policy to be used as the basis of the service request, the EVC Service Request Editor window appears. It is divided into three main sections:

•Link Page

•Direct Connect Links (no NPCs)

•Links with L2 Access Nodes (involves NPCs)

This window enables you to specify options for the service request, as well as configure directly connected links and links with L2 access nodes. The options displayed in first section of the window change, depending on the MPLS Core Connectivity Type that was specified in the policy (pseudowire or local). For clarity, each of these scenarios is presented in a separate section below, to highlight the different window configurations and behavior of the displayed options.

Proceed to the appropriate section, as determined by the MPLS Core Connectivity Type for the policy:

•Pseudowire Core Connectivity

•Local Core Connectivity

Instructions for setting up direct connect links and links with L2 access nodes are presented in later sections.

Pseudowire Core Connectivity

This section covers the case in which the MPLS Core Connectivity Type for the EVC ATM-Ethernet Interworking policy is PSEUDOWIRE.

To set the attributes in the first section of the EVC Service Request Editor window, perform the following steps.

Note The Job ID and SR ID fields are read-only. When the service request is being created for the first time, the fields display a value of NEW. When an existing service request is being modified, the values of the fields indicate the respective IDs that the Prime Fulfillment database holds within the editing flow of the service request.

Note The Policy field is read-only. It displays the name of the policy on which the service request is based. Clicking on the read-only policy name displays a list of all the attribute values set within the policy.

Step 1 Click Select VPN to choose a VPN for use with this service request.

The Select VPN window appears with the VPNs defined in the system.

Note The same VPN can be used by service requests with LOCAL and PSEUDOWIRE core types. If a VPN for a service request is used with VPLS core type, the same VPN cannot be used for service requests with LOCAL or PSEUDOWIRE core type.

Step 2 Choose a VPN Name in the Select column.

Step 3 Click Select.

The EVC Service Request Editor window appears with the VPN name displayed.

Step 4 Check the AutoPick VC ID check box if you want Prime Fulfillment to choose a VC ID.

If you do not check this check box, you will be prompted to provide the ID in the VC ID field, as covered in the next step.

When AutoPick VC ID is checked, Prime Fulfillment allocates a VC ID for pseudowires from the Prime Fulfillment-managed VC ID resource pool. In this case, the text field for the VC ID option is non-editable.

Step 5 If AutoPick VC ID was unchecked, enter a VC ID in the VC ID field.

Usage notes:

•The AutoPick VC ID attribute appears during the creation of an EVC pseudowire service request.

•The VC ID value must be an integer value corresponding to a VC ID.

•When a VC ID is manually allocated, Prime Fulfillment verifies the VC ID to see if it lies within Prime Fulfillment's VC ID pool. If the VC ID is in the pool but not allocated, the VC ID is allocated to the service request. If the VC ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VC ID. If the VC ID lies outside of the Prime Fulfillment VC ID pool, Prime Fulfillment does not perform any verification about whether or not the VC ID allocated. The operator must ensure the VC ID is available.

•The VC ID can be entered only while creating a service. If you are editing the service request, the VC ID field is not editable.

Step 6 Check the Configure Bridge Domain check box to determine bridge domain characteristics.

The behavior of the Configure Bridge Domain option works in tandem with the choice you selected in the MPLS Core Connectivity Type option in the EVC policy, which in this case is pseudowire core connectivity. There are two cases:

•With EVC:

–If Configure With Bridge Domain is checked, the policy will configure pseudowires under SVIs associated to the bridge domain.

–If Configure With Bridge Domain is unchecked, the policy will configure pseudowires directly under the service instance. This will conserve the global VLAN.

•Without EVC:

–If Configure With Bridge Domain is checked, the policy will configure pseudowires under SVIs.

–If Configure With Bridge Domain is unchecked, the policy will configure pseudowires directly under subinterfaces.

Pseudowires can be configured either directly under service instance of the corresponding EVC-capable interface or under SVIs associated to the bridge domain.

Step 7 Check the Use Split Horizon check box to enable split horizon with bridge domain.

Usage notes:

•The Use Split Horizon attribute is disabled by default.

•The Use Split Horizon attribute can be used only when the Configure Bridge Domain check box is checked (enabled).

•When Use Split Horizon is enabled, the bridge domain command in the CLI will be generated with split horizon. When it is disabled, the bridge domain command will be generated without split horizon.

Step 8 Click the "Click here" link of the Description attribute to enter a description label for the service request.

This is useful for searching the Prime Fulfillment database for the particular service request.

A dialogue appears in which you can enter a description.

Step 9 To set up direct connect links, see the section Setting Direct Connect Links.

Step 10 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes.

Local Core Connectivity

This section covers the case in which the MPLS Core Connectivity Type for the EVC ATM-Ethernet Interworking policy is LOCAL.

To set the attributes in the first section of the EVC Service Request Editor window, perform the following steps.

Step 1 The Job ID and SR ID fields are read-only.

When the service request is being created for the first time, the fields display a value of NEW. When an existing service request is being modified, the values of the fields indicate the respective IDs that the Prime Fulfillment database holds within the editing flow of the service request.

Step 2 The Policy field is read-only.

It displays the name of the policy on which the service request is based.

Step 3 Click Select VPN to choose a VPN for use with this service request.

The Select VPN window appears with the VPNs defined in the system.

Note The same VPN can be used by service requests with LOCAL and PSEUDOWIRE core types. If a VPN for a service request is used with VPLS core type, the same VPN cannot be used for service requests with LOCAL or PSEUDOWIRE core type.

Step 4 Choose a VPN Name in the Select column.

Step 5 Click Select.

The EVC Service Request Editor window appears with the VPN name displayed.

Step 6 Check the Configure Bridge Domain check box to determine bridge domain characteristics.

Usage notes:

•If Configure Bridge Domain is checked, all links will have the same bridge domain ID allocated from the VLAN pool on the N-PE. All non-EVC links will have the Service Provider VLAN as the bridge domain ID. On the other hand, if no EVC links are added, the Service Provider VLAN will be allocated first and this will be used as the bridge domain ID when EVC links are added.

•If Configure Bridge Domain is unchecked, a maximum of two links that terminate on the same N-PE can be added. (This uses the connect command available in the EVC infrastructure.) This is only supported for ATM-ATM local connect.

Note See the following comments for details on how Prime Fulfillment autogenerates the connect name.

Because the device only accepts a maximum of 15 characters for the connect name, the connect name is generated using the following format:

CustomerNameTruncatedToMaxPossibleCharacters_ServiceRequestJobID

For example, if the customer name is NorthAmericanCustomer and the service request job ID is 56345, the autogenerated connect name would be NorthAmer_56345.

The CLI generated would be:

connect NorthAmer_56345 ATM7/0/5 11 ATM7/0/4 18

In this case, 11 and 18 are service instance VPIs.

•If the policy setting for Configure Bridge Domain is non-editable, the option in the service request will be read-only.

Step 7 Check the Use Split Horizon check box to enable split horizon with bridge domain.

Usage notes:

•The Use Split Horizon attribute is disabled by default.

•The Use Split Horizon attribute can be used only when the Configure Bridge Domain check box is checked (enabled).

•When Use Split Horizon is enabled, the bridge domain command in the CLI will be generated with split horizon. When it is disabled, the bridge domain command will be generated without split horizon.

Step 8 Click the "Click here" link of the Description attribute to enter a description label for the service request.

A dialogue appears in which you can enter a description.

Step 9 To set up direct connect links, see the section Setting Direct Connect Links.

Step 10 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes.

Setting up Links to the N-PE

The lower two sections of the EVC Service Request Editor window allow you to set up links to the N-PE. For direct connect links, the CE is directly connected to the N-PE, with no intermediate L2 access nodes. For links with L2 access nodes, there are intermediate devices present between the CE and NPE requiring NPCs to be created in Prime Fulfillment.

The Direct Connect Links section of the window is where you set up links that directly connect to the N-PE. No NPCs are involved. ATM links are supported for direct connect links.

The Links with L2 Access Nodes section is where you set up links with L2 (Ethernet) access nodes. NPCs are involved.

Note ATM interfaces cannot be in L2 access nodes.

See the appropriate section, depending on which type of link you are setting up:

•Setting Direct Connect Links

•Setting Links with L2 Access Nodes

Note Many of steps for setting up the two link types are the same. The basic workflow for setting up links, as well as the attributes to be set, are presented in the following section Setting Direct Connect Links. Even if you are setting up links with L2 access nodes, it will be helpful to refer to the information presented in that section, as the section on L2 access nodes only covers the unique steps for such links.

Setting Direct Connect Links

To set up the direct connect links, perform the following steps. Most of these steps apply to links with L2 access nodes also.

Step 1 Click Add to add a link.

A new numbered row for the link attributes appears.

Step 2 Click Select N-PE in N-PE column.

The Select PE Device window appears. This window displays the list of currently defined PEs.

a. The Show PEs with drop-down list shows PEs by Provider, PE Region Name, or by Device Name.

b. The Find button allows a search for a specific PE or a refresh of the window.

c. The Rows per page drop-down list allows the user to configure the number of entries displayed on the screen at one time.

Step 3 In the Select column, choose the PE device name for the link.

Step 4 Click Select.

The EVC Service Request Editor window reappears displaying the name of the selected PE in the NPE column.

Step 5 Choose the UNI interface from the drop-down list in the UNI column.

Note Prime Fulfillment only displays the available interfaces for the service, based on the configuration of the underlying interfaces, existing service requests that might be using the interface, and the customer associated with the service request. You can click the Details button to display a pop-up window with information on the available interfaces, such as interface name, customer name, VPN name, job ID, service request ID, service request type, translation type, and VLAN ID information.

Note When the UNI is configured on an N-PE device running IOS XR, the Standard UNI Port attribute is not supported. All the CLIs related to Standard UNI Port and UNI Port Security are ignored in this case.

Step 6 Check the EVC check box to mark the link for configuring service instance for the links.

Note The EVC check box is mentioned at this stage because the setting of the check box alters the behavior of the link editing function available in the Link Attributes column. This is covered in the next steps.

Note The EVC check box is unchecked by default. The default value for the check box can be changed by setting the value of the DCPL property Pr ovisioning\ProvDrv\CheckFlexUniCheckBox.

Editing the Link Attributes

The next steps document the use of the Edit link in the Link Attributes column. (In the case where the link attributes have already been set, this link changes from Edit to Change.) The link editing workflow changes depending on the status of the EVC check box for the link. If the EVC check box is checked, the editing workflow involves setting attributes in two windows, for two sets of link attributes:

•The EVC Details

•Standard UNI Details

If the EVC check box for the link is not checked, only the Standard UNI Details window is presented.

In the steps that follow, both scenarios covered.

Note If you are setting up and ATM link (by choosing an ATM interface as the UNI on the N-PE device, there is a different workflow. The check box in the EVC column dynamically disappears, and clicking the Edit link in the link attributes column brings up the ATM-Ethernet Attributes window. For information on using this window to set up an ATM link, see Setting the ATM Link Attributes.

Step 7 Click Edit in the Link Attributes column to specify the UNI attributes.

EVC Details Window

If the EVC check box is checked, the EVC Details window appears

All of the fields in the EVC Details window are enabled based on the policy settings. For example, if Both Tags is selected in the policy and is editable, then the Match Inner and Outer Tags check box will be selected and editable in this window. The behavior is similar for the other attributes in the EVC Details window

Step 8 Check the AutoPick Service Instance ID check box to specify that the service instance ID will be autogenerated and allocated to the link during service request creation.

If the check box is unchecked, you must specify the service instance ID (see the next step).

Usage notes:

•The service instance ID represents an Ethernet Flow Point (EFP) on an interface in the EVC infrastructure. The service instance ID is locally significant to the interface. This ID has to be unique only at the interface level. The ID must be a value from 1 to 8000.

•There are no resource pools available in Prime Fulfillment from which to allocate the service instance IDs.

•In the case of a manually provided service instance ID, it is the responsibility of the operator to maintain the uniqueness of the ID at the interface level.

•This attribute is not displayed for IOS XR devices.

Step 9 If the AutoPick Service Instance ID check box is not checked, enter an appropriate value for the service instance ID in the Service Instance ID field.

Step 10 Check the AutoPick Service Instance Name check box to specify that the service instance name will be autogenerated.

If the check box is unchecked, you can specify the service instance name (see the next step).

Usage notes:

•If the check box is checked, the Service Instance Name text field is disabled.

•The service instance name is autogenerated in the following pattern: CustomerName_ServiceRequestJobID.

•For example configlets, see EVC (No AutoPick Service Instance Name, No Service Instance Name), EVC (User-Provided Service Instance Name, Pseudowire Core Connectivity), and EVC (User-Provided Service Instance Name, Local Core Connectivity).

•This attribute is not displayed for IOS XR devices.

Step 11 If the AutoPick Service Instance Name check box is not checked, enter an appropriate value for the service instance ID in the Service Instance Name field.

Usage notes:

•The text string representing the service instance name must be 40 characters or less and contain no spaces. Other special characters are allowed.

•If AutoPick Service Instance Name is unchecked and no service instance name is entered in the text field, then Prime Fulfillment does not generate the global ethernet evc evcname command in the device configuration generated by the service request.

Step 12 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID for the service request during service request creation.

If this check box is unchecked, the you must specify a bridge domain VLAN ID (see the next step).

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

•This attribute is not displayed for IOS XR devices.

Step 13 If the AutoPick Bridge Domain/VLAN ID check box is unchecked, enter an appropriate value in the Bridge Domain/VLAN ID field.

Note This configuration applies in conjunction with the Configure Bridge Domain option in the EVC Service Request Editor window. If the option is not enabled in that window, then AutoPick Bridge Domain/VLAN ID check box is redundant and not required.

When a VLAN ID is manually allocated, Prime Fulfillment verifies the VLAN ID to see if it lies within Prime Fulfillment's VLAN ID pool. If the VLAN ID is in the pool but not allocated, the VLAN ID is allocated to the service request. If the VLAN ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VLAN ID. If the VLAN ID lies outside of the Prime Fulfillment VLAN ID pool, Prime Fulfillment does not perform any verification about whether the VLAN ID allocated. The operator must ensure the VLAN ID is available.

Step 14 Check the AutoPick Bridge Domain/VLAN ID Secondary N-PE check box to have Prime Fulfillment autopick the bridge domain VLAN ID for the secondary N-PE of a dual-homed ring during service request creation.

If this check box is unchecked, the you must specify a secondary bridge domain VLAN ID for the secondary N-PE (see the next step).

Usage notes:

•This attribute is only applicable in the case of a dual-homed ring (a ring that terminates on two different N-PEs). Prime Fulfillment supports having a separate bridge domain VLAN ID for the secondary N-PE.

•In a dual-homed ring, if the two N-PEs are in different access domains, Prime Fulfillment allocates the bridge domain VLAN IDs from both primary and secondary N-PE access domains. When both are in the same Access Domain, Prime Fulfillment allocates a common VLAN ID from the Access Domain to which these belong.

•AutoPick Bridge Domain/VLAN ID Secondary N-PE consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

•This attribute is not displayed for IOS XR devices.

Step 15 If the AutoPick Bridge Domain/VLAN ID Secondary N-PE check box is unchecked, enter an appropriate value in the Bridge Domain/VLAN ID Secondary N-PE field.

Step 16 Check the Match Inner and Outer Tags check box to enable service requests created with the policy to match both the inner and outer VLAN tags of the incoming frames.

If you do not check this check box, service requests created with the policy will match only the outer VLAN tag of the incoming frames.

Checking the Match Inner and Outer Tags attribute causes the Inner VLAN ID and Outer VLAN ID fields (covered in the next steps) to appear.

Step 17 If the Match Inner and Outer Tags check box is checked, enter the inner and outer VLAN tags in the Inner VLAN ID and Outer VLAN ID fields.

Usage notes:

•You can specify single values, single ranges, multiples values, multiple ranges, or combinations of these. Examples:

–10

–10, 15,17

–10-15

–10-15,17-20

–10,20-25

•If the Inner VLAN Ranges attribute is set to true in the policy, the Inner VLAN ID field can take a range of inner VLAN tags.

•If the Outer VLAN Ranges attribute is set to true in the policy, the Outer VLAN ID field can take a range of Outer VLAN tags.

Step 18 If the Match Inner and Outer Tags check box is unchecked, enter the outer VLAN tag in the Outer VLAN ID field.

Note The VLAN specified in Outer VLAN ID will be provisioned on the rest of the L2 access nodes (if the link has any), including the customer-facing UNI.

Note You may also have Prime Fulfillment autopick the outer VLAN ID as covered in the next step.

Step 19 Check the AutoPick Outer VLAN check box to have Prime Fulfillment autopick the outer VLAN ID from a previously created outer VLAN ID resource pool.

If this check box is unchecked, the operator will be prompted to specify an outer VLAN ID.

Note Use of the AutoPick Outer VLAN attribute requires that two elements have already been set up in Prime Fulfillment. One is an Interface Access Domain, which is a logical element that groups the physical ports of an N-PE device. The other is an EVC Outer VLAN resource pool, which is used by the Interface Access Domain. For instructions on how to set up these elements, see the sections Setting Up Resources, and Resource Pools.

Usage notes:

•AutoPick Outer VLAN can be used for interfaces that support EVC functionality

•AutoPick Outer VLAN consumes a VLAN ID on the interface that supports EVC.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

Step 20 In the VLAN Rewrite section of the window, choose a Rewrite Type from the drop-down list.

The choices are:

•Pop

•Push

•Translate

The subsequent attributes in the GUI change depending on the choice of Rewrite Type, as covered in the next steps.

Step 21 If Pop is the Rewrite Type, two check boxes appear:

a. Check the Pop Outer Tag check box to pop the outer VLAN ID tag of the incoming frames that fulfill the match criteria. If this check box is unchecked, the outer tag of the incoming traffic will not be popped.

b. Check the Pop Inner Tag check box to pop the inner VLAN ID tag of the incoming frames that fulfill the match-criteria. If this check box is unchecked, the inner tag will not be changed.

Note that if Pop Inner Tag is checked, Pop Outer Tag is automatically checked.

Step 22 If Push is the Rewrite Type, two text boxes appear:

a. In the text box Outer VLAN ID, enter an outer VLAN ID tag that will be imposed on the incoming frames that fulfill the match criteria. All service requests created with this setting push a dot1q outer tag on the incoming frames matching the match criteria. If a value is not provided, the push operation is ignored and not configured on the device.

b. In the text box Inner VLAN ID, enter an inner VLAN ID tag that will be imposed on the incoming frames that fulfill the match criteria. All service requests created with this setting push a dot1q inner tag on the incoming frames matching the match criteria. The Inner VLAN tag cannot be pushed without an Outer VLAN tag. That is, when pushing an Inner VLAN tag, the Outer VLAN tag also must be defined.

Step 23 If Translate is the Rewrite Type, a Translation Type drop-down list appears.

The choices available in this list vary depending on the setting of the Match Inner and Outer Tags attribute (set in a previous step).

a. If the Match Inner and Outer Tags check box is checked (true), choose a translation type of 1:1, 1:2, 2:1, or 2:2 from the Translation Type drop-down list.

–If you choose 1:1 or 2:1, enter a value in the Outer VLAN ID text box that appears. The outer tag of all the incoming frames that fulfill the match criteria will be translated to this ID.

–If you choose 1:2 or 2:2, enter values in the Outer VLAN ID and Inner VLAN ID text boxes that appear. The outer and inner tags of all the incoming frames that fulfill the match criteria will be translated to these IDs.

b. If the Match Inner and Outer Tags check box is unchecked (false), choose a translation type of 1:1 or 1:2 from the Translation Type drop-down list.

–If you choose 1:1, enter a value in the Outer VLAN ID text box that appears. The outer tag of all the incoming frames that fulfill the match criteria will be translated to this ID.

–If you choose 1:2, enter values in the Outer VLAN ID and Inner VLAN ID text boxes that appear. The outer and inner tags of all the incoming frames that fulfill the match criteria will be translated to these IDs.

Step 24 Clicked Next to save the settings in the EVC Details window.

The Standard UNI Details window appears.

Step 25 Continue with setting the standard UNI link attributes in the next steps.

Editing the Standard UNI Attributes

The following steps cover setting the attributes in the Standard UNI Details window. In the case of a link which is not set as an EVC link (by not checking the EVC check box in the Service Request Details window), editing the link attributes begins with this window.

Note The attributes that appear in the Standard UNI Details window are dynamically configured by Prime Fulfillment. Some of the attributes covered in the steps below might not appear in the window, depending on the policy and service request settings or the link type. For example, if the MPLS core connectivity type of the EVC policy is local, the pseudowire-related attributes will not appear. Also, setting the link as EVC or non-EVC will change the attributes that appear in the window. In addition, attributes are filtered based on device type (IOS or IOS XR). These cases are noted in the steps, for reference.

Step 26 The N-PE/U-PE Information and Interface Name fields display the PE device and interface name selected in previous steps.

These fields are read-only.

Step 27 Choose an Encapsulation type from the drop-down list.

The choices are:

•DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation. If the UNI belongs to a directly connected and EVC link, this setting signifies that the incoming frames are 802.1q encapsulated and that they match the VLAN ID configured for the link. This specific topology does not involve a trunk UNI as such.

•DOT1QTUNNEL—Configures the UNI as an 802.1q tunnel (also known as a dot1q tunnel or Q-in-Q) port.

•ACCESS—Configures the UNI as an access port.

This attribute allows you to deploy different types of UNI encapsulation on different links of a service.

Usage notes:

•In the case of direct connect links for which EVC is enabled (by checking the EVC check box in the EVC Service Request Editor window), the choices for the Encapsulation type are DOT1Q and DEFAULT.

Step 28 In the PE/UNI Interface Description field, enter a description for the interface, if desired.

Step 29 Check the UNI Shutdown check box if you want to leave the UNI port shut during service activation (for example, when the service provider wants to deploy a service in the network but wants to activate it at a later time).

Step 30 Specify the type of VLAN Translation for the service request by clicking the appropriate radio button.

The choices are:

•No—No VLAN translation is performed. (This is the default.)

•1:1—1:1 VLAN translation.

•2:1—2:1 VLAN translation.

•1:2—1:2 VLAN translation.

•2:2—2:2 VLAN translation.

Usage notes:

•The VLAN Translation attribute does not appear for direct connect links if the EVC check box is enabled. It does appear for the following combinations:

–Direct connect links with EVC check box disabled.

–L2 access nodes with EVC check box enabled or disabled.

•Choosing a selection other than No causes other fields to appear in the GUI, which you can set based on your configuration:

–CE VLAN—Provide a value between 1 and 4096.

–Auto Pick—Check this check box to have Prime Fulfillment autopick the outer VLAN from the VLAN resource pool.

–Outer VLAN—If Auto Pick is unchecked, provide a value between 1 and 4096.

–Select where 2:1 or 2:2 translation takes place—Specify the device where the 2;1 or 2:2 VLAN translation will take place. If you choose Auto, the VLAN translation takes place at the device closest to the UNI port.

•VLAN translation, and all standard UNI and port security attributes are applicable for links with L2 access. If the UNI is on an N-PE, these attributes will not appear.

•When the VLAN translation takes place on a U-PE or PE-AGG device, the VLAN translation command is configured on the NNI interface of the selected device. When the VLAN translation takes place on an NP-E, the VLAN translation command is configured on the UNI interface of the device.

•When there are two NNI interfaces in a ring-based environment, VLAN translation is applied for both of these NNI interfaces.

•1:1 and 2:1 VLAN translations are supported with the same syntax as for non-EVC (switchport-based N-PE syntax) terminating attachment circuits.

Step 31 Check the N-PE Pseudo-wire on SVI check box to have Prime Fulfillment generate forwarding commands under SVIs (switch virtual interfaces).

By default, this check box is not checked. In this case, Prime Fulfillment generates forwarding commands under the service instance.

For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (this is available in the service request workflow in the EVC Service Request Editor window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE Pseudo-wire on SVI is enabled.

Usage notes:

•For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (in the EVC Service Request Editor window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with scanned under SVI, even if N-PE pseudo-wire on SVI is enabled.

•Prime Fulfillment supports a hybrid configuration for EVC service requests. In a hybrid configuration, the forwarding commands (such as scanned) for one side of an attachment circuit can be configured under a service instance, and the xconnect configuration for the other side of the attachment circuit can be configured under a switch virtual interface (SVI).

•N-PE Pseudo-wire on SVI is applicable for all connectivity types (PSEUDOWIRE or LOCAL), but a hybrid SVI configuration is possible only for pseudowire connectivity.

•When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy and service request.

•For examples of these cases, see configlet examples EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) and EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI).

•For additional information on the N-PE Pseudo-wire on SVI attribute, see the corresponding coverage in the EVC policy section in the section Setting the Interface Attributes.

•The N-PE Pseudo-wire on SVI attribute is not supported for IOS XR devices. All the xconnect commands are configured on L2 subinterfaces/service instance.

Step 32 Check the Use Existing PW Class check box to enable the selection of a pseudowire class.

This attribute is unchecked by default.

Usage notes:

•If Use Existing PW Class is checked, an additional attribute, Existing PW Class Name, appears in the GUI. Enter the name of a pseudowire class which already exists in the device.

•If Use Existing PW Class is checked, the PW Tunnel Selection and Interface Tunnel attributes will disappear from the window. This is to prevent Prime Fulfillment from generating the pseudowire class.

•The Use PseudoWireClass attribute is only available if the MPLS core connectivity type was set as PSEUDOWIRE in the Service Options window (see Pseudowire Core Connectivity).

•Use PseudoWireClass is only applicable for IOS XR devices.

Step 33 Check the PW Tunnel Selection check box if you want to be able to manually select the Traffic Engineering (TE) tunnel for the pseudowire connecting point-to-point N-PEs.

Usage notes:

•Checking the PW Tunnel Selection check box activates the Interface Tunnel attribute field (see the next step).

•This attribute only appears if the MPLS core connectivity type is set as pseudowire in the EVC policy.

Step 34 If you checked the PW Tunnel Selection check box, enter the TE tunnel ID in the Interface Tunnel text field.

Prime Fulfillment uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs. This pseudowire class can be shared by more than one pseudowire, as long as the pseudowires share the same tunnel ID and remote loopback address. During service request creation, Prime Fulfillment does not check the validity of the tunnel ID number. That is, Prime Fulfillment does not verify the existence of the tunnel.

Step 35 Check the Use PseudoWireClass check box to enable the selection of a pseudowire class.

This attribute is unchecked by default.

Usage notes:

•The pseudowire class name is used for provisioning pw-class commands on IOS XR devices. See Creating and Modifying Pseudowire Classes for additional information on pseudowire class support for IOS XR devices.

•If Use PseudoWireClass is checked, an additional attribute, PseudoWireClass, appears in the GUI. Click the Select button of PseudoWireClass attribute to choose a pseudowire class previously created in Prime Fulfillment.

•The Use PseudoWireClass attribute is only available if the MPLS core connectivity type was set as PSEUDOWIRE in the Service Options window (see Setting the Service Options).

•Use PseudoWireClass is only applicable for IOS XR devices.

Step 36 Check the AutoPick Bridge Group Name check box to have Prime Fulfillment autopick the bridge group name during service request creation.

If this check box is unchecked, you are prompted to specify a bridge group name during service request creation (see the next step).

Usage notes:

•This attribute only displays for IOS XR devices.

•If the AutoPick Bridge Group Name check box is unchecked, enter an bridge group name in the Bridge Group Name text field.

Step 37 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID during service request creation.

If this check box is unchecked, you are prompted to specify a VLAN ID during service request creation (see the next step).

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

•The AutoPick Bridge Domain/VLAN ID attribute appears for both Cisco 7600 and ASR 9000 devices. It will be displayed only for non-EVC links.

Step 38 If the AutoPick Bridge Domain/VLAN ID check box is unchecked, enter an ID number in the Bridge Domain/VLAN ID text field.

Usage notes:

•If AutoPick Bridge Domain/VLAN ID is checked, this field is non-editable.

•When a VLAN ID is manually allocated, Prime Fulfillment verifies the VLAN ID to see if it lies within Prime Fulfillment's VLAN ID pool. If the VLAN ID is in the pool but not allocated, the VLAN ID is allocated to the service request. If the VLAN ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VLAN ID. If the VLAN ID lies outside of the Prime Fulfillment VLAN ID pool, Prime Fulfillment does not perform any verification about whether the VLAN ID allocated. The operator must ensure the VLAN ID is available.

•The Bridge Domain/VLAN ID text field appears for both Cisco 7600 and ASR 9000 devices. It will be displayed only for non-EVC links.

Step 39 For L2VPN Group Name choose one of the following from the drop-down list:

•ISC

•VPNSC

Usage notes:

•This attribute is used for provisioning the L2VPN group name on IOS XR devices.

Note The choices in the drop-down list are derived from a configurable DCPL property. For information about how to define the L2VPN Group Name choices available in the drop-down list, see Defining L2VPN Group Names for IOS XR Devices.

•L2VPN Group Name is only applicable for IOS XR devices.

Step 40 Enter an E-Line Name to specify the point-to-point (p2p) E-line name.

Usage notes:

•If no value is specified for the E-Line Name, Prime Fulfillment autogenerates a default name as follows:

–For PSEUDOWIRE core connectivity type, the format is:

DeviceName--VC_ID

–For LOCAL core connectivity type, the format is:

DeviceName--VLAN_ID

If the default name is more than 32 characters, the device names are truncated.

•E-Line Name is only applicable for IOS XR devices.

Step 41 Click OK to save the Standard UNI settings and return to the EVC SR window.

The value in the Link Attributes column now displays as "Changed," signifying that the link settings have been updated. You can edit the link attributes now or at a future time by clicking on the Changed link and modifying the settings in the Standard UNI Details window.

See Modifying the EVC Service Request, for details on editing the link attributes.

Step 42 To add another link click the Add button and set the attributes for the new link as in the previous steps in this section.

Step 43 To delete a link, check the check box in the first column of the row for that link and click the Delete button.

Step 44 If you want to set up links with L2 access nodes for this service request, see Setting Links with L2 Access Nodes.

Step 45 When you have completed setting the attributes in the EVC Service Request Editor window, click the Save button at the bottom of the window to save the settings and create the EVC service request.

If any attributes are missing or incorrectly set, Prime Fulfillment displays a warning in the lower left of the window. Make any corrections or updates needed (based on the information provided by Prime Fulfillment), and click the Save button.

For information on modifying an EVC service request see the section Modifying the EVC Service Request. For additional information about saving an EVC service request, see Saving the EVC Service Request.

Setting the ATM Link Attributes

This section describes how to set up a direct connect link as an ATM link.

To set up the ATM link, perform the following steps.

Step 1 In the Direct Connect Links section of the EVC Service Request Editor window, specify the device for which you would like to set up an ATM link.

Step 2 Choose an ATM interface for the UNI.

Note ATM interfaces are displayed in the drop-down list in the UNI column only if the EVC service request is based on an ATM-Ethernet Interworking policy type.

When you choose an ATM interface, the check box in the EVC column dynamically disappears from the GUI.

Step 3 In the Link Attributes column, click the Edit link of the device on which you want to add an ATM link.

The ATM UNI Details window appears.

All of the fields in the ATM UNI Details window are enabled based on the policy settings.

Step 4 Choose the Transport Mode from the drop-down list.

The choices are:

•VP—Virtual path mode. This is the default.

•VC—Virtual circuit mode.

Step 5 Choose the ATM Encapsulation from the drop-down list.

•AAL5SNAP

Step 6 To specify the ATM virtual channel descriptor (VCD)/subinterface number, enter a value in the ATM VCD/Sub-Interface # field.

The value can be from 1 to 2147483647.

Step 7 To specify the ATM virtual path identifier (VPI), enter a value in the ATM VPI field.

The value can be from 0 to 255.

Step 8 To specify the ATM virtual channel identifier (VCI), a value in the ATM VCI field.

The value can be from 32 to 65535.

Step 9 Check the UNI Shutdown check box if you want to leave the UNI port shut during service activation (for example, when the service provider wants to deploy a service in the network but wants to activate it at a later time).

Step 10 Check the Use Existing PW Class check box to enable the selection of a pseudowire class.

This attribute is unchecked by default.

Usage notes:

•If Use Existing PW Class is checked, an additional attribute, Existing PW Class Name, appears in the GUI. Enter the name of a pseudowire class which already exists in the device.

•If Use Existing PW Class is checked, the PW Tunnel Selection and Interface Tunnel attributes will disappear from the window. This is to prevent Prime Fulfillment from generating the pseudowire class.

•The Use PseudoWireClass attribute is only available if the MPLS core connectivity type was set as PSEUDOWIRE in the Service Options window (see Pseudowire Core Connectivity).

•Use PseudoWireClass is only applicable for IOS XR devices.

Step 11 Check the N-PE Pseudo-wire on SVI check box to have Prime Fulfillment generate forwarding commands under SVIs (switch virtual interfaces).

By default, this check box is not checked. In this case, Prime Fulfillment generates forwarding commands under the service instance.

For an EVC link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (this is available in the service request workflow in the EVC Service Request Editor window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE Pseudo-wire on SVI is enabled.

Usage notes:

•For an ATM link, the attribute N-PE Pseudo-wire on SVI is dependent on the value of the attribute Configure with Bridge Domain (in the EVC Service Request Editor window). N-PE Pseudo-wire on SVI, if enabled, will be reflected only when Configure with Bridge Domain is set to true. Otherwise, the service request will not be created with xconnect under SVI, even if N-PE pseudo-wire on SVI is enabled.

•Prime Fulfillment supports a hybrid configuration for EVC service requests. In a hybrid configuration, the forwarding commands (such as xconnect) for one side of an attachment circuit can be configured under a service instance, and the xconnect configuration for the other side of the attachment circuit can be configured under a switch virtual interface (SVI).

•N-PE Pseudo-wire on SVI is applicable for all connectivity types (PSEUDOWIRE or LOCAL), but a hybrid SVI configuration is possible only for pseudowire connectivity.

•When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy and service request.

•For examples of these cases, see configlet examples EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) and EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI).

•For additional information on the N-PE Pseudo-wire on SVI attribute, see the corresponding coverage in the EVC policy section in the section Setting the Interface Attributes.

•The N-PE Pseudo-wire on SVI attribute is not supported for IOS XR devices. All the xconnect commands are configured on L2 subinterfaces/service instance.

Step 12 Check the PW Tunnel Selection check box if you want to be able to manually select the Traffic Engineering (TE) tunnel for the pseudowire connecting point-to-point N-PEs.

Usage notes:

•Checking the PW Tunnel Selection check box activates the Interface Tunnel attribute field (see the next step).

•This attribute only appears if the MPLS core connectivity type is set as pseudowire in the EVC policy.

Step 13 If you checked the PW Tunnel Selection check box, enter the TE tunnel ID in the Interface Tunnel text field.

Prime Fulfillment uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs. This pseudowire class can be shared by more than one pseudowire, as long as the pseudowires share the same tunnel ID and remote loopback address. During service request creation, Prime Fulfillment does not check the validity of the tunnel ID number. That is, Prime Fulfillment does not verify the existence of the tunnel.

Step 14 Check the AutoPick Bridge Domain/VLAN ID check box to have Prime Fulfillment autopick the VLAN ID during service request creation.

If this check box is unchecked, you are prompted to specify a VLAN ID during service request creation (see the next step).

Usage notes:

•AutoPick Bridge Domain/VLAN ID consumes a global VLAN ID on the device.

•The bridge domain VLAN ID is picked from the existing Prime Fulfillment VLAN pool.

Step 15 If the AutoPick Bridge Domain/VLAN ID check box is unchecked, enter an ID number in the Bridge Domain/VLAN ID text field.

Usage notes:

•If AutoPick Bridge Domain/VLAN ID is checked, this field is non-editable.

•When a VLAN ID is manually allocated, Prime Fulfillment verifies the VLAN ID to see if it lies within Prime Fulfillment's VLAN ID pool. If the VLAN ID is in the pool but not allocated, the VLAN ID is allocated to the service request. If the VLAN ID is in the pool and is already in use, Prime Fulfillment prompts you to allocate a different VLAN ID. If the VLAN ID lies outside of the Prime Fulfillment VLAN ID pool, Prime Fulfillment does not perform any verification about whether the VLAN ID allocated. The operator must ensure the VLAN ID is available.

Step 16 Click OK to save the ATM UNI Details settings and return to the EVC Service Request Editor window.

The value in the Link Attributes column now displays as "Changed," signifying that the link settings have been updated. You can edit the link attributes now or at a future time by clicking on the Changed link and modifying the settings in the Standard UNI Details window.

See Modifying the EVC Service Request for details on editing the link attributes.

Step 17 To add another link click the Add button and set the attributes for the new link as in the previous steps in this section.

Step 18 To delete a link, check the check box in the first column of the row for that link and click the Delete button.

Step 19 If you want to set up links with L2 access nodes for this service request, see Setting Links with L2 Access Nodes.

Step 20 When you have completed setting the attributes in the EVC Service Request Editor window, click the Save button at the bottom of the window to save the settings and create the EVC service request.

If any attributes are missing or incorrectly set, Prime Fulfillment displays a warning in the lower left of the window. Make any corrections or updates needed (based on the information provided by Prime Fulfillment), and click the Save button.

For information on modifying an EVC service request see the section Modifying the EVC Service Request. For additional information about saving an EVC service request, see Saving the EVC Service Request.

Setting Links with L2 Access Nodes

The Links with L2 Access Nodes section of the EVC Service Request Editor window allows you to set up links with L2 (Ethernet) access nodes. These are similar to direct connect links, except that they have L2/Ethernet access nodes beyond the N-PE (towards the CE). Therefore, NPCs are involved.

Note ATM links are not supported in L2 access nodes. ATM links must be set up as direct connect links. For more information, see Setting the ATM Link Attributes.