Cisco Systems OL-21636-01 User Manual

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Text Part Number: OL-21636-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at

www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership

relationship between Cisco and any other company. (1005R)

IMPLIED, INCLUDING, WITHOUT

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

About This Guide xi

CHAPTER

1 Getting Started 1-1

Overview 1-1

Installing ISC and Configuring the Network 1-1

Configuring the Network to Support Layer 2 Services 1-2

Setting Up Basic ISC Services 1-2

Setting Up Providers, Customers, and Devices 1-2 Setting Up the N-PE Loopback Address 1-3 Setting Up ISC Resources for L2VPN and VPLS Services 1-3 Setting Up NPCs 1-3 Setting Up VPNs 1-3

Working with L2VPN and VPLS Policies and Service Requests 1-4

A Note on Terminology Conventions 1-4

2 Setting Up the ISC Services 2-1

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

Configuring Device Settings to Support ISC 2-2

Configuring Switches in VTP Transparent Mode 2-2 Setting the Loopback Addresses on N-PE Devices 2-2 Setting Up Devices for IOS XR Support 2-3

OL-21636-01

Defining a Service Provider and Its Regions 2-3

Defining Customers and Their Sites 2-4

Defining VPNs 2-4

Creating Access Domains 2-4

Creating VLAN Pools 2-5

Creating a VC ID Pool 2-7

Creating Named Physical Circuits 2-8

Creating NPCs Through an NPC GUI Editor 2-8 Creating a Ring-Only NPC 2-9 Terminating an Access Ring on Two N-PEs 2-10 Creating NPC Links Through the Autodiscovery Process 2-10

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

iii

Contents

Creating and Modifying Pseudowire Classes for IOS XR Devices 2-10

Creating a Pseudowire Class 2-11 Modifying a Pseudowire Class Object 2-12 Configuring the Transport Mode When Pseudowire Classes are Not Supported 2-13

Defining L2VPN Group Names for IOS XR Devices 2-14

CHAPTER

3 Creating a FlexUNI/EVC Ethernet Policy 3-1

Overview of FlexUNI/EVC Support in ISC 3-1

FlexUNI/EVC Features 3-2 Platform Support for FlexUNI/EVC in ISC 6.0 3-3

IOS Platform Support 3-3

IOS XR Platform Support 3-4 Device Roles with FlexUNI/EVC 3-5 Topology Overview for FlexUNI/EVC 3-5

CE Directly Connected and FlexUNI 3-5

CE Directly Connected and No FlexUNI 3-5

CE Not Directly Connected and FlexUNI 3-5

CE Not Directly Connected and No FlexUNI 3-6 A Note on Checking of Configurations 3-6

Defining the FlexUNI/EVC Ethernet Policy 3-6

Setting the Service Options 3-8

Setting the FlexUNI Attributes 3-10

Setting the Service Attributes 3-11 Setting the VLAN Matching Criteria Attributes 3-13 Setting the VLAN Rewrite Criteria Attributes 3-14

CHAPTER

Setting the Interface Attributes 3-16

Enabling Template Association 3-23

4 Managing a FlexUNI/EVC Ethernet Service Request 4-1

Introducing FlexUNI/EVC Service Requests 4-1

Creating a FlexUNI/EVC Service Request 4-2

Setting the Service Request Details 4-2

Pseudowire Core Connectivity 4-3 VPLS Core Connectivity 4-5 Local Core Connectivity 4-7 Setting up Links to the N-PE 4-9

Setting Direct Connect Links 4-10

Setting Links with L2 Access Nodes 4-20

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Modifying the FlexUNI/EVC Service Request 4-21

Using Templates and Data Files with a FlexUNI/EVC Ethernet Service Request 4-22

Saving the FlexUNI/EVC Service Request 4-23

Contents

CHAPTER

5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy 5-1

Overview 5-1

Defining the FlexUNI/EVC ATM-Ethernet Interworking Policy 5-2

Setting the Service Options 5-4

Setting the ATM Interface Attributes 5-6

Setting the FlexUNI Attributes 5-7

Setting the Service Attributes 5-8 Setting the VLAN Matching Criteria Attributes 5-10 Setting the VLAN Rewrite Criteria Attributes 5-10

Setting the Interface Attributes 5-12

Enabling Template Association 5-19

6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request 6-1

Overview 6-1

Creating a FlexUNI/EVC ATM-Ethernet Interworking Service Request 6-2

Setting the Service Request Details 6-3

Pseudowire Core Connectivity 6-3 Local Core Connectivity 6-6 Setting up Links to the N-PE 6-8

Setting Direct Connect Links 6-8 Setting the ATM Link Attributes 6-18 Setting Links with L2 Access Nodes 6-22

CHAPTER

OL-21636-01

Modifying the FlexUNI/EVC Service Request 6-23

Using Templates and Data Files with a FlexUNI/EVC Service Request 6-24

Saving the FlexUNI/EVC Service Request 6-24

7 Creating an L2VPN Policy 7-1

Defining an L2VPN Policy 7-1

Defining an Ethernet ERS (EVPL) Policy with a CE 7-3

Defining an Ethernet ERS (EVPL) Policy without a CE 7-9

Defining an Ethernet EWS (EPL) Policy with a CE 7-15

Defining an Ethernet EWS (EPL) Policy without a CE 7-22

Defining a Frame Relay Policy with a CE 7-28

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

Contents

Defining a Frame Relay Policy without a CE 7-31

Defining an ATM Policy with a CE 7-33

Defining an ATM Policy without a CE 7-36

CHAPTER

8 Managing an L2VPN Service Request 8-1

Introducing L2VPN Service Requests 8-1

Creating an L2VPN Service Request 8-2

Creating an ERS (EVPL), ATM, or Frame Relay L2VPN Service Request with a CE 8-2 Creating an EWS (EPL) L2VPN Service Request with a CE 8-8 Creating an ERS (EVPL), ATM, or Frame Relay L2VPN Service Request without a CE 8-11 Creating an EWS (EPL) L2VPN Service Request without a CE 8-16

Modifying the L2VPN Service Request 8-20

Saving the L2VPN Service Request 8-26

9 Creating a VPLS Policy 9-1

Defining a VPLS Policy 9-1

Defining an MPLS/ERMS (EVP-LAN) Policy with a CE 9-3

Defining an MPLS/ERMS (EVP-LAN) Policy without a CE 9-7

Defining an MPLS/EMS (EP-LAN) Policy with a CE 9-11

Defining an MPLS/EMS (EP-LAN) Policy without a CE 9-16

Defining an Ethernet/ERMS (EVP-LAN) Policy with a CE 9-22

CHAPTER

Defining an Ethernet/ERMS (EVP-LAN) Policy without a CE 9-27

Defining an Ethernet/EMS (EP-LAN) Policy with a CE 9-32

Defining an Ethernet/EMS (EP-LAN) Policy without a CE 9-37

10 Managing a VPLS Service Request 10-1

Introducing VPLS Service Requests 10-1

Creating a VPLS Service Request 10-2

Creating a VPLS Service Request with a CE 10-2

Creating a VPLS Service Request without a CE 10-6

Modifying the VPLS Service Request 10-10

Using the Bridge Domain ID Attribute 10-13

Saving the VPLS Service Request 10-14

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Contents

CHAPTER

11 Deploying, Monitoring, and Auditing Service Requests 11-1

Deploying Service Requests 11-1

Pre-Deployment Changes 11-1 Service Deployment 11-2 Verifying Service Requests 11-3 Service Request States 11-4 Viewing Service Request Details 11-7

Links 11-8 History 11-9 Configlets 11-9

Monitoring Service Requests 11-10

Auditing Service Requests 11-12

12 Using Autodiscovery for L2 Services 12-1

13 Generating L2 and VPLS Reports 13-1

Overview 13-1

Accessing L2 and VPLS Reports 13-1

APPENDIX

L2 and VPLS Reports 13-2

L2 End-to-End Wire Report 13-3 L2 PE Service Report 13-6 L2 VPN Report 13-7 VPLS Attachment Circuit Report 13-8 VPLS PE Service Report 13-10 VPLS VPN Report 13-11

Creating Custom L2 and VPLS Reports 13-11

A Sample Configlets A-1

Overview A-2

ERS (EVPL) (Point-to-Point) A-4

ERS (EVPL) (Point-to-Point, UNI Port Security) A-5

ERS (EVPL) (1:1 VLAN Translation) A-7

ERS (EVPL) (2:1 VLAN Translation) A-8

ERS (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) A-9

ERS (EVPL) (NBI Enhancements for L2VPN, IOS Device) A-10

OL-21636-01

ERS (EVPL) or EWS (EPL) (IOS XR Device) A-11

ERS (EVPL) and EWS (EPL) (Local Connect on E-Line) A-14

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

vii

Contents

ERS (EVPL), EWS (EPL), ATM, or Frame Relay (Additional Template Variables for L2VPN, IOS and IOS XR Device) A-15

EWS (EPL) (Point-to-Point) A-16

EWS (EPL) (Point-to-Point, UNI Port Security, BPDU Tunneling) A-17

EWS (EPL) (Hybrid) A-19

EWS (EPL) (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) A-22

EWS (EPL) (NBI Enhancements for L2VPN, IOS Device) A-23

ATM over MPLS (VC Mode) A-24

ATM over MPLS (VP Mode) A-25

ATM (Port Mode, Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) A-26

Frame Relay over MPLS A-27

Frame Relay (DLCI Mode) A-28

VPLS (Multipoint, ERMS/EVP-LAN) A-29

VPLS (Multipoint, EMS/EP-LAN), BPDU Tunneling) A-30

FlexUNI/EVC (Pseudowire Core Connectivity, UNI Port Security) A-31

FlexUNI/EVC (Pseudowire Core Connectivity, UNI, without Port Security, with Bridge Domain) A-32

FlexUNI/EVC (Pseudowire Core Connectivity, UNI, and Pseudowire Tunneling) A-33

FlexUNI/EVC (VPLS Core Connectivity, UNI Port Security) A-34

FlexUNI/EVC (VPLS Core Connectivity, no UNI Port Security) A-35

FlexUNI/EVC (Local Connect Core Connectivity, UNI Port Security) A-36

FlexUNI/EVC (Local Connect Core Connectivity, UNI, no Port Security, Bridge Domain) A-38

FlexUNI/EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) A-39

FlexUNI/EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI) A-40

FlexUNI/EVC (AutoPick Service Instance Name) A-41

FlexUNI/EVC (No AutoPick Service Instance Name, No Service Instance Name) A-42

FlexUNI/EVC (User-Provided Service Instance Name, Pseudowire Core Connectivity) A-43

FlexUNI/EVC (User-Provided Service Instance Name, Local Core Connectivity) A-44

FlexUNI/EVC (User-Provided Service Instance Name, VPLS Core Connectivity) A-45

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Point-to-Point Circuit) A-46

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) A-47

FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) A-48

viii

FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Multipoint Circuit) A-49

FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Multipoint Circuit) A-50

FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) A-51

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit) A-52

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) A-53

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Contents

FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) A-54

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, with Bridge Domain) A-55

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, with Bridge Domain) A-56

FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, no Bridge Domain) A-57

APPENDIX

B Working with Templates and Data Files B-1

Overview B-1

Summary of Template Manager Features B-1 Template and Data File Workflow B-3

Using Templates with ISC Policies B-4

Overview of Template Support in ISC Policies B-4 Associating Templates and Data Files to a Policy B-5 Selectively Determining Templates for U-PE and PE-AGG Device Roles B-9

Using Templates with Service Requests B-10

Overview of Template Use in Service Requests B-10

Associating Templates to a Service Request B-11 Associating Subtemplates During Service Provisioning B-11 Creating Data Files During Service Request Creation B-12 Using Negate Templates to Decommission Template Configurations B-13

Using Templates and Data Files with Service Requests B-14

Choosing a Template in the Service Request Workflow B-14 Creating a Data File in the Service Request Workflow B-16 Decommissioning Service Requests with Added Templates B-18 Viewing Templates from the Service Requests Window B-18

APPENDIX

OL-21636-01

C Setting Up VLAN Translation C-1

VLAN Translation Overview C-1

Setting Up VLAN Translation C-1

Creating a Policy C-2 Creating a Service Request C-3

No VLAN Translation C-3 1:1 VLAN Translation C-3

2:1 VLAN Translation C-4 Modifying a Service Request C-5 Deleting a Service Request C-5

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

Contents

Platform-Specific Usage Notes C-6

VLAN Translation on the 3750 C-6 VLAN Translation on the 7600 C-6 Failed Service Requests When Hardware Does Not Support VLAN Translation C-6

APPENDIX

D Terminating an Access Ring on Two N-PEs D-1

Overview D-1

Setting Up an NPC Access Ring with Two N-PEs D-3

Using N-PE Redundancy in FlexUNI/EVC Service Requests D-3

Additional Network Configurations and Sample Configlets D-5

Example 1: Pseudowire Connectivity (A) D-5 Example 2: Pseudowire Connectivity (B) D-6 Example 3: Pseudowire Connectivity (C) D-8 Example 4: VPLS Connectivity D-9

E ISC Layer 2 VPN Concepts E-1

Layer 2 Terminology Conventions E-1

MEF Terminology Conventions E-1 Mapping MEF Terminologies to Network Technologies E-3 ISC Terminology and Supported Network Types E-4

L2VPN Service Provisioning E-5

Point-to-Point Ethernet (EWS and ERS) (EPL and EVPL) E-5 ATM over MPLS (ATMoMPLS) E-8 Frame Relay over MPLS (FRoMPLS) E-9

NDEX

VPLS Service Provisioning E-10

Multipoint EWS (EP-LAN) for an MPLS-Based Provider Core E-11 Multipoint ERS (EVP-LAN) for an MPLS-Based Provider Core E-11 Topology for MPLS-Based VPLS E-11

VPLS for an Ethernet-Based (L2) Provider Core E-13

Multipoint EWS (EP-LAN) for an Ethernet-Based Provider Core E-13 Multipoint ERS (EVP-LAN) for an Ethernet-Based Provider Core E-13 Topology for Ethernet-Based VPLS E-13

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

About This Guide

This preface contains the following sections:

• Objective, page xi

• Audience, page xi

• Organization, page xi

• Related Documentation, page xii

• Obtaining Documentation and Submitting a Service Request, page xiv

Objective

The Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0 contains information about creating L2VPN or VPLS policies and creating and deploying L2VPN or VPLS services using the Cisco IP Solution Center (ISC).

Audience

This guide is designed for service provider network managers and operators who are responsible for provisioning L2VPN or VPLS for their customers. Network managers and operators should be familiar with the following topics:

• Basic concepts and terminology used in internetworking.

• Layer 2 Virtual Private Network (L2VPN), Virtual Private LAN Service (VPLS), VPN,

• Network topologies and protocols.

Organization

This guide is organized as follows:

• Chapter 1, “Getting Started,” provides information on getting started tasks for using the L2VPN

Multiprotocol Label Switching (MPLS), and terms and technology.

component of the Cisco IP Solution Center (ISC).

OL-21636-01

• Chapter 2, “Setting Up the ISC Services,” provides information on setting up the ISC service.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

About This Guide

• Chapter 3, “Creating a FlexUNI/EVC Ethernet Policy,” provides information on creating a

FlexUNI/EVC policy.

• Chapter 4, “Managing a FlexUNI/EVC Ethernet Service Request,” provides information on

creating, deploying, monitoring, and saving FlexUNI/EVC service requests.

• Chapter 5, “Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy,” provides information on

creating a FlexUNI/EVC ATM-Ethernet Interworking policy.

• Chapter 6, “Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request,” provides

information on creating, deploying, monitoring, and saving FlexUNI/EVC ATM-Ethernet Interworking service requests.

• Chapter 7, “Creating an L2VPN Policy,” provides information on creating an L2VPN policy.

• Chapter 8, “Managing an L2VPN Service Request,” provides information on creating, deploying,

monitoring, and saving a L2VPN service requests.

• Chapter 9, “Creating a VPLS Policy,” provides information on creating a VPLS policy.

• Chapter 10, “Managing a VPLS Service Request,” provides information on creating, deploying,

monitoring, and saving VPLS service requests.

• Chapter 11, “Deploying, Monitoring, and Auditing Service Requests,” provides information on how

to deploy, manage and audit service requests, and how to access task logs.

• Chapter 12, “Using Autodiscovery for L2 Services,” provides an overview of L2 service discovery.

• Chapter 13, “Generating L2 and VPLS Reports,” provides information on how to set up, run, and

format L2 and VPLS reports.

• Appendix A, “Sample Configlets,” provides sample configlets for various network scenarios.

• Appendix B, “Working with Templates and Data Files,” provides information about using templates

and data files in ISC policies and service requests.

• Appendix C, “Setting Up VLAN Translation,” provides information on how to set up VLAN

translation for L2VPN ERS services.

• Appendix D, “Terminating an Access Ring on Two N-PEs,” describes how to terminate an access

ring on two N-PEs.

• Appendix E, “ISC Layer 2 VPN Concepts,” provides an overview of the major concepts that

structure the ISC L2VPN or VPLS service.

• Index

Overview

CHA PTER

Getting Started

This chapter provides a road map to help you get started using the L2VPN component in ISC 6.0. It contains the following sections:

• Overview, page 1-1

• Installing ISC and Configuring the Network, page 1-1

• Configuring the Network to Support Layer 2 Services, page 1-2

• Setting Up Basic ISC Services, page 1-2

• Working with L2VPN and VPLS Policies and Service Requests, page 1-4

• A Note on Terminology Conventions, page 1-4

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

Installing ISC and Configuring the Network

Before you can use the L2VPN module in ISC to provision L2VPN or VPLS services, you must first install ISC and do the basic network configuration required to support ISC. Details on these steps are provided in the ISC installation and general network configuration requirements.

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

Cisco IP Solution Center Installation Guide, 6.0. See that guide for information about

OL-21636-01

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

1-1

Chapter 1 Getting Started

Configuring the Network to Support Layer 2 Services

In addition to basic network configuration required for ISC, you must perform the following network configuration steps to support Layer 2 services. Information on doing these steps is not provided in the ISC 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 ISC Services

After the basic network configuration tasks are completed to support ISC and L2 services, you use ISC to define elements in the ISC 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 ISC tasks are covered in the

6.0. You can also find a summary of some important ISC set up tasks in this guide in Chapter 2, “Setting

Up the ISC Services.” The information below is a checklist of basic ISC services you must set up before

provisioning L2 services.

Cisco IP Solution Center Infrastructure Reference,

Setting Up Providers, Customers, and Devices

Perform the following steps to set up providers, customers, and devices in the ISC repository. These are global resources that can be used by all ISC 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 the

Reference, 6.0. See also Defining a Service Provider and Its Regions, page 2-3.

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 the

Solution Center Infrastructure Reference, 6.0. See also Defining Customers and Their Sites,

page 2-4.

3. Import or add raw devices. Every network element that ISC manages must be defined as a device

in the ISC repository. An element is any device from which ISC can collect information. In most cases, devices are Cisco IOS routers and switches. You can set up devices in ISC manually, through autodiscovery, or through importing device configuration files. For detailed steps for importing, adding, and collecting configurations for devices, see the

Reference, 6.0. See also Chapter 12, “Using Autodiscovery for L2 Services.”

4. Assign devices roles as PE or CE. After devices are created in ISC, 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 ISC inventory manager. To set device attributes, see the

IP Solution Center Infrastructure Reference, 6.0.

Cisco IP Solution Center Infrastructure

Cisco IP

Cisco IP Solution Center Infrastructure

Cisco

1-2

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Chapter 1 Getting Started

Setting Up the N-PE Loopback Address

Within ISC, you must set the loopback address on the N-PE device(s). For details about this procedure, see

Setting the Loopback Addresses on N-PE Devices, page 2-2.

Setting Up ISC Resources for L2VPN and VPLS Services

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

1. Create access domain(s). For L2VPN and VPLS, you create an access domain if you provision an

Ethernet-based service and want ISC 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 ISC. 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 the

Cisco IP Solution Center Infrastructure Reference, 6.0. See also Creating Access Domains,

page 2-4.

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 ISC 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 the

Center Infrastructure Reference, 6.0. See also Creating VLAN Pools, page 2-5.

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 the

Infrastructure Reference, 6.0. See also Creating a VC ID Pool, page 2-7.

Setting Up Basic ISC Services

Cisco IP Solution

Cisco IP Solution Center

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 the

Named Physical Circuits, page 2-8.

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 the

page 2-4.

Cisco IP Solution Center Infrastructure Reference, 6.0. See also Creating

Cisco IP Solution Center Infrastructure Reference, 6.0. See also Defining VPNs,

OL-21636-01

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

1-3

Chapter 1 Getting Started

Working with L2VPN and VPLS Policies and Service Requests

After you have set up providers, customers, devices, and resources in ISC, you are ready to create 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 Appendix E, “ISC Layer 2 VPN

Concepts”

2. Set up a FlexUNI, L2VPN, or VPLS policy. See the appropriate chapter, depending on the type of

policy you want to create:

–

Chapter 3, “Creating a FlexUNI/EVC Ethernet Policy.”

–

Chapter 5, “Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy.”

–

Chapter 7, “Creating an L2VPN Policy.”

–

Chapter 9, “Creating a VPLS Policy.”

3. Provision the FlexUNI, L2VPN, or VPLS service request. See the appropriate chapter, depending

on the type service request you want to provision:

–

Chapter 4, “Managing a FlexUNI/EVC Ethernet Service Request.”

–

Chapter 6, “Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request.”

–

Chapter 8, “Managing an L2VPN Service Request.”

–

Chapter 10, “Managing a VPLS Service Request.”

4. Deploy the service request. See Chapter 11, “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 Chapter 11, “Deploying, Monitoring, and Auditing Service

Requests.”

–

Audit service requests. See Chapter 11, “Deploying, Monitoring, and Auditing Service

Requests.”

–

Run L2 and VPLS reports. See Chapter 13, “Generating L2 and VPLS Reports.”

A Note on Terminology Conventions

The ISC GUI and this 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 ISC to conform with current MEF conventions. For reference, the equivalent terms used by the MEF forum are summarized in

Table 1-1.

1-4

See Layer 2 Terminology Conventions, page E-1 for more information on terminology conventions and how these align with underlying network technologies.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Chapter 1 Getting Started

A Note on Terminology Conventions

Ta b l e 1-1 Ethernet Service Terminology Mappings

Term Used in ISC GUI and This User Guide Current MEF Equivalent Term

L2VPN over MPLS Core

Ethernet Wire Service (EWS) Ethernet Private Line (EPL)

Ethernet Relay Service (ERS) Ethernet Virtual Private Line (EVPL)

ATM over MPLS (ATMoMPLS) —

Frame Relay over MPLS (FRoMPLS) —

VPLS Over MPLS Core

Ethernet Wire Service (EWS) or Ethernet Multipoint Service (EMS)

Ethernet Relay Service (ERS) or Ethernet Relay Multipoint Service (ERMS)

VPLS over Ethernet Core

Ethernet Wire Service (EWS) Ethernet Private LAN (EP-LAN)

Ethernet Relay Service (ERS) Ethernet Virtual Private LAN (EVP-LAN)

Ethernet Private LAN (EP-LAN)

Ethernet Virtual Private LAN (EVP-LAN)

OL-21636-01

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

1-5

A Note on Terminology Conventions

Chapter 1 Getting Started

1-6

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

CHA PTER

Setting Up the ISC Services

To create L2VPN, VPLS, and FlexUNI/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 chapter contains the basic steps to set up the Cisco IP Solution Center (ISC) services for an L2VPN services. It contains the following sections:

• Creating Target Devices and Assigning Roles (N-PE or U-PE), page 2-1

• Configuring Device Settings to Support ISC, page 2-2

• Defining a Service Provider and Its Regions, page 2-3

• Defining Customers and Their Sites, page 2-4

• Defining VPNs, page 2-4

• Creating Access Domains, page 2-4

• Creating VLAN Pools, page 2-5

• Creating a VC ID Pool, page 2-7

• Creating Named Physical Circuits, page 2-8

• Creating and Modifying Pseudowire Classes for IOS XR Devices, page 2-10

• Defining L2VPN Group Names for IOS XR Devices, page 2-14

Note This chapter presents high-level information on ISC services that are relevant to L2VPN. For more

detailed information on setting up these and other basic ISC services, see the

Infrastructure Reference, 6.0.

Cisco IP Solution Center

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

Every network element that ISC manages must be defined as a device in the system. An element is any device from which ISC 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 the

Infrastructure Reference, 6.0.

Cisco IP Solution Center

OL-21636-01

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

2-1

Configuring Device Settings to Support ISC

Two device settings must be configured to support the use of ISC 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 ISC 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, ISC 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

Chapter 2 Setting Up the ISC Services

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. You set the PE loopback address in the Edit PE device window. Access the Edit PE device window in ISC by doing the following steps.

Step 1 Choose Service Inventory > Inventory and Connection Manager.

Step 2 Choose PE Devices in the Selection window.

Step 3 Choose a specific device and click the Edit button.

To prevent a wrong loopback address being entered into the system, the loopback IP address field on the GUI is read-only. You choose the loopback address with the help of a separate pop-up window, which you access by clicking the Select button. This ensures that you choose only a valid loopback address defined on the device.

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).

2-2

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Chapter 2 Setting Up the ISC Services

Setting Up Devices for IOS XR Support

L2VPN in ISC 6.0 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.)

Defining a Service Provider and Its Regions

• 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 ISC as an IOS XR device, as follows:

a. Create the Cisco device by choosing Service Inventory > Inventory and Connection Manager >

Devices > Create. The Create Cisco Device window appears.

b. 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 the Cisco

IP Solution Center Infrastructure Reference, 6.0.

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

Sample configlets for IOS XR devices are provided in Appendix A, “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.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

2-3

Defining Customers and Their Sites

For detailed steps to define the provider administrative domain, see the Cisco IP Solution Center

Infrastructure Reference, 6.0.

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 the

Cisco IP Solution Center Infrastructure Reference, 6.0.

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.

To create a VPN, perform the following steps.

Chapter 2 Setting Up the ISC Services

Step 1 Choose Service Inventory > Inventory and Connection Manager.

Step 2 Click VPNs in the left column.

The VPNs window appears.

For detailed steps to create VPNs, see the Cisco IP Solution Center Infrastructure Reference, 6.0.

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 ISC 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 ISC. 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.

2-4

• 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.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Chapter 2 Setting Up the ISC Services

To create an Access Domain, perform the following steps.

Step 1 Choose Service Inventory > Inventory and Connection Manager.

Step 2 Click Access Domains in the left column.

The Access Domains window appears.

The Access Domains window contains the following:

• Access Domain Name—Lists the names of access domains. The first character must be a letter. The

name can contain letters, numbers, and these punctuation characters: period, underscore, and dash. Limit: 80 characters. You can sort the list by access domain name.

• Provider Name—Lists the names of providers. Must begin with a letter. Can contain letters,

numbers, and these punctuation characters: period, underscore, and dash. Limited to 80 characters. You can sort the list by provider name.

• From the Access Domains window, you can create, edit, or delete access domains using the

following buttons:

Creating VLAN Pools

–

Create—Click to create new access domain. Enabled only if you do not select an access domain.

–

Edit—Click to edit the selected access domain (select by checking the corresponding box). Enabled only if you select a a single access domain.

–

Delete—Click to delete the selected access domain (select by checking the corresponding box). Enabled only if you select one or more access domains.

Creating VLAN Pools

For L2VPN and VPLS, you create a VLAN pool so that ISC 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, ISC 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 an ISC service, ISC warns you if the VLAN ID is outside

the valid range of the defined VLAN pool. If so, ISC 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.

OL-21636-01

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.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

2-5

Creating VLAN Pools

Step 1 Choose Service Inventory.

Step 2 Choose Inventory and Connection Manager.

Step 3 Choose Resource Pools.

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

Step 5 Click Create.

Step 6 Enter a VLAN Pool Start number.

Step 7 Enter a VLAN Pool Size number.

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

Chapter 2 Setting Up the ISC Services

• Have created an access domain for the VLAN pool. See Creating Access Domains, page 2-4.

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

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

The Resource Pools window appears.

The Create VLAN Pool window appears.

Access Domain field.

The Access Domain for New VLAN Pool 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 VLAN Pool window appears.

Step 9 Click Save.

The updated VLAN Resource Pools 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, page 2-4.) The VLAN pool status automatically sets to “Allocated” on the Resource Pools window when

you save your work.

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

2-6

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Chapter 2 Setting Up the ISC Services

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 an ISC service, ISC warns you if the VC ID is outside the valid

range of the defined VC ID pool. If so, ISC 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.)

Creating a VC ID Pool

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

Perform the following steps for all L2VPN and VPLS services.

Step 1 Choose Service Inventory.

Step 2 Choose Inventory and Connection Manager.

Choose Resource Pools.

The Resource Pools window appears.

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

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

Step 4 Click Create.

The Create VC ID Pool window appears.

Step 5 Enter a VC pool start number.

Step 6 Enter a VC pool size number.

Step 7 Click Save.

OL-21636-01

The updated VC ID Resource Pools window appears.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

2-7

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 an NPC GUI

Editor, page 2-8.

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

the Autodiscovery Process, page 2-10.

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.

Chapter 2 Setting Up the ISC Services

• 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.

• Click Insert Device to insert the device.

Creating NPCs Through an NPC GUI Editor

2-8

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

Step 1 Choose Service Inventory > Inventory and Connection Manager > 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.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

Chapter 2 Setting Up the ISC Services

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 the Cisco IP Solution Center Infrastructure Reference, 6.0.

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

Step 2 Click Create.

Creating Named Physical Circuits

The Create a Named Physical Circuit 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 Circuit 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 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 Service Inventory > Inventory and Connection Manager > Named Physical Circuits.

OL-21636-01

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

2-9

Creating and Modifying Pseudowire Classes for IOS XR Devices

Step 2 Click Create.

The Create a Named Physical Circuit 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 Create a Named Physical Circuit window appears showing the Ring-Only NPC.

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

Chapter 2 Setting Up the ISC Services

Terminating an Access Ring on Two N-PEs

ISC 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 ISC, see Appendix D, “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 ISC database. NPCs are further abstracted from the discovered connectivity.

For detailed steps to create NPCs using autodiscovery, see the Cisco IP Solution Center Infrastructure

Reference, 6.0.

Creating and Modifying Pseudowire Classes for IOS XR Devices

2-10

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.

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

OL-21636-01

+ 368 hidden pages

Cisco Systems OL-21636-01 User Manual

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0

CONTENTS

About This Guide

Overview

Getting Started

Installing ISC and Configuring the Network

Configuring the Network to Support Layer 2 Services

Setting Up Basic ISC Services

Setting Up Providers, Customers, and Devices

Setting Up the N-PE Loopback Address

Setting Up ISC Resources for L2VPN and VPLS Services

Setting Up NPCs

Setting Up VPNs

Working with L2VPN and VPLS Policies and Service Requests

A Note on Terminology Conventions

Setting Up the ISC Services

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

Configuring Device Settings to Support ISC

Configuring Switches in VTP Transparent Mode

Setting the Loopback Addresses on N-PE Devices

Setting Up Devices for IOS XR Support

Defining a Service Provider and Its Regions

Defining Customers and Their Sites

Defining VPNs

Creating Access Domains

Creating VLAN Pools

Creating a VC ID Pool

Creating Named Physical Circuits

Creating NPCs Through an NPC GUI Editor

Creating a Ring-Only NPC

Creating and Modifying Pseudowire Classes for IOS XR Devices

Terminating an Access Ring on Two N-PEs

Creating NPC Links Through the Autodiscovery Process