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.
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.
C O N T E N T S About This Guide CHAPTER 1 Getting Started Overview xi 1-1 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 Setting Up NPCs 1-3 Setting Up VPNs 1-3 Working with L2VPN and VPLS Policies and Service Requests A Note on Terminology Conventions CHAPTER 2
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 Defining L2VPN Group Names for IOS XR Devices CHAPTER 3 Creating a FlexUNI/EVC Ethernet Policy 2-13 2-14 3-1 Overview of FlexUNI/EVC Support in ISC 3-1 FlexUNI/EVC Features 3-2 Platform Support for FlexUNI/EVC in ISC 6.
Contents Modifying the FlexUNI/EVC Service Request 4-21 Using Templates and Data Files with a FlexUNI/EVC Ethernet Service Request Saving the FlexUNI/EVC Service Request CHAPTER 5 4-23 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Overview 4-22 5-1 5-1 Defining the FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Service Options 5-2 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 Cr
Contents Defining a Frame Relay Policy without a CE Defining an ATM Policy with a CE 7-33 Defining an ATM Policy without a CE CHAPTER 7-36 Managing an L2VPN Service Request 8 7-31 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 (
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 Auditing Service Requests 11-10 11-12 CHAPTER 12 Using Autodiscovery for L2 Services CHAPTER 13 Generating L2 and VPLS Reports Overview 12-1 13-1 13-1 Accessing L2 and V
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) EWS (EPL) (Hybrid) A-17 A-19 EWS (EPL) (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) EWS (EPL) (NBI Enhancements for L2VPN, IOS Device) ATM over MPLS (VC Mode) A-24 ATM over MPLS (VP Mode) A-25 A-22 A-23 ATM (Port Mode, Pseudowire Class, E-Line, L2VPN Group Name, IOS XR
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 Overv
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 APPENDIX D Terminating an Access Ring on Two N-PEs Overview D-1 D-1 Setting Up an NPC Access Ring with Two N-PEs APPENDIX E C-6 D-3 Using N-PE Redundancy in FlexUNI/EVC Service Requests D-3 Additional Network Configurations and Sample Configlets Example 1: Pseudowire Connectivity (A) D-5 Example 2: Pseudowire Connec
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).
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.
About This Guide General documentation (in suggested reading order) • Cisco IP Solution Center Getting Started and Documentation Guide, 6.0. http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/6.0/roadmap/docguide.html • Release Notes for Cisco IP Solution Center, 6.0. http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/6.0/release/notes/relnotes.html • Cisco IP Solution Center Installation Guide, 6.0. http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/6.
About This Guide Note All documentation might be upgraded over time. All upgraded documentation will be available at the same URLs specified in this document. Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.
CH A P T E R 1 Getting Started This chapter provides a road map to help you get started using the L2VPN component in ISC 6.0.
Chapter 1 Getting Started Configuring the Network to Support Layer 2 Services 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.
Chapter 1 Getting Started Setting Up Basic ISC Services 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.
Chapter 1 Getting Started Working with L2VPN and VPLS Policies and Service Requests 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.
Chapter 1 Getting Started A Note on Terminology Conventions Table 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 Private LAN (EP-LAN)
Chapter 1 Getting Started A Note on Terminology Conventions Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 2 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.
Chapter 2 Setting Up the ISC Services Configuring Device Settings to Support ISC Configuring Device Settings to Support ISC Two device settings must be configured to support the use of ISC in the network: Note • Switches in the network must be operating in VTP transparent mode. • Loopback addresses must be set on N-PE devices. These are the two minimum device settings required for ISC to function properly in the network.
Chapter 2 Setting Up the ISC Services Defining a Service Provider and Its Regions 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.
Chapter 2 Setting Up the ISC Services 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.
Chapter 2 Setting Up the ISC Services Creating VLAN Pools 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.
Chapter 2 Setting Up the ISC Services Creating VLAN Pools • 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. Step 1 Choose Service Inventory. Step 2 Choose Inventory and Connection Manager. Step 3 Choose Resource Pools. The Resource Pools window appears.
Chapter 2 Setting Up the ISC Services Creating a VC ID Pool 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.
Chapter 2 Setting Up the ISC Services Creating Named Physical Circuits 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.
Chapter 2 Setting Up the ISC Services Creating Named Physical Circuits 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.
Chapter 2 Setting Up the ISC Services 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.
Chapter 2 Setting Up the ISC Services Creating and Modifying Pseudowire Classes for IOS XR 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 ISC Traffic Engineering Management (TEM) application, if it is being used.
Chapter 2 Setting Up the ISC Services Creating and Modifying Pseudowire Classes for IOS XR Devices Step 5 In the Description field, enter a meaningful description of less than 128 characters. This field is optional. Step 6 Choose the MPLS encapsulation type from the Encapsulation drop-down list. Note Step 7 Choose the transport mode from the TransportMode drop-down list. The choices are: • Ethernet • Vlan • NONE (default) Note Step 8 Currently, the only encapsulation type supported is MPLS.
Chapter 2 Setting Up the ISC Services Creating and Modifying Pseudowire Classes for IOS XR Devices Step 2 Select the pseudowire class object you want to modify, and click Edit. The Edit PseudoWire Class 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.
Chapter 2 Setting Up the ISC Services Defining L2VPN Group Names for IOS XR Devices Perform the following steps. Step 1 In ISC, 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. ISC then generates VLAN transport mode configuration for the pseudowire.
CH A P T E R 3 Creating a FlexUNI/EVC Ethernet Policy This chapter contains an overview of FlexUNI/EVC support in ISC, as well as the basic steps to create a FlexUNI/EVC Ethernet policy.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Overview of FlexUNI/EVC Support in ISC Services leveraging the FlexUNI/EVC infrastructure are varied in nature, and there is not always a clear delineation between different services. This is because FlexUNI/EVC provides great flexibility in the way these services can be delivered. This can make it challenging to define the services. For example, a traditional ERS could be delivered in several ways by variations of the Class on the platform.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Overview of FlexUNI/EVC Support in ISC – VPLS – Local (local connects) • Flexible VLAN handling mechanism that deals with up to two levels of VLAN tags: – VLAN matching for service classification. This provides the ability to match both outer and inner VLAN tags, or the ability to match a range of inner VLAN tags. – VLAN manipulations, such as pop outer tag, pop inner tag, push outer tag, push inner tag, and VLAN translations (1:1, 2:1, 1:2, 2:2).
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Overview of FlexUNI/EVC Support in ISC Example 2 As far as Layer 2 access nodes are concerned, configurations on the UNI/NNI of a U-PE and/or PE-AGG are not influenced by the FlexUNI/EVC capability on the N-PE. However, if a selected named physical circuit (NPC) with N-PE interface is configured with FlexUNI/EVC, it cannot be provisioned for traditional configuration. An error will be generated while saving the service request.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Overview of FlexUNI/EVC Support in ISC Device Roles with FlexUNI/EVC Presently, ISC has U-PE, PE-AGG and N-PE devices. The basic PE device role association of ISC continues for FlexUNI/EVC policy and service requests. In this release of ISC, there are no changes made to the PE role assignment. A device having FlexUNI/EVC capabilities will not call for a change in the existing role assignment in ISC.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Defining the FlexUNI/EVC Ethernet Policy • Ethernet U-PE and/or PE-AGGs. • N-PE with FlexUNI-capable interface on the CE-facing side. All service-specific parameters, such as port-security, L2 Protocol Tunneling, storm control, and so on, are applicable to the UNI (Standard UNI) in such links. The U-PE and/or PE-AGG configurations will also have no change in CLIs. However, the EVC commands are applicable only on the N-PE (on the CE-facing interface).
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Defining the FlexUNI/EVC Ethernet Policy Figure 3-1 EVC Policy Editor - Service Type Step 4 Enter a Policy Name for the FlexUNI/EVC policy. Step 5 Choose the Policy Owner for the FlexUNI/EVC policy. There are three types of FlexUNI/EVC policy ownership: • Customer ownership • Provider ownership • Global ownership—Any service operator can make use of this policy.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Service Options Setting the Service Options This section describes how to set the service options for the FlexUNI/EVC Ethernet policy, as shown in Figure 3-2. Figure 3-2 EVC Policy Editor - Service Options Window The Editable check box gives you the option of making a field editable.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Service Options • If the check box is unchecked, zero or more links can use the FlexUNI/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 FlexUNI/EVC support being added in the future.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the FlexUNI Attributes Note Step 4 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the FlexUNI Attributes Figure 3-3 EVC Policy Editor - FlexUNI Attribute Window FlexUNI 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 FlexUNI service attributes, perform the following steps.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the FlexUNI Attributes 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the FlexUNI Attributes manually-specified VLAN is already in use in the access domain delimited by the FlexUNI, ISC 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the FlexUNI Attributes Checking the Both Tags attribute causes the Inner VLAN Ranges attribute (covered in the next steps) to appear in the FlexUNI 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the FlexUNI Attributes Step 4 • 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 FlexUNI-capable) or just one tag (not FlexUNI-capable) and treat the inner-most tags transparently as payload.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes The EVC Policy Editor - Interface Attribute window appears, as shown in Figure 3-3. Step 8 Continue with the steps contained in the next section, Setting the Interface Attributes, page 3-16. Setting the Interface Attributes This step of creating the FlexUNI/EVC Ethernet policy involves setting the interface attributes, as shown in the EVC Policy Editor - Interface Attribute window in Figure 3-4.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes Figure 3-4 EVC Policy Editor - Interface Attributes Window To set the FlexUNI/EVC interface attributes, perform the following steps. Step 1 Choose an Encapsulation type. The choices are: Step 2 • DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation. If the UNI belongs to a directly connected and FlexUNI link, this setting signifies that the incoming frames are 802.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes Step 4 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes Figure 3-5 Step 11 UNI Port Security Check the Enable Storm Control check box (see Figure 3-6) 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes Step 13 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.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes Table 3-2 Use Bridge Domain FlexUNI N-PE Pseudowire on SVI True True True True False Step 14 Use Cases for Hybrid Configuration for FlexUNI /EVC Service Requests True True False N/A CLIs Generated • xconnect under VLAN interface. • Service instance under main interface. • xconnect under service instance. • Service instance under main interface. • xconnect under service instance.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Setting the Interface Attributes 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. ISC uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Enabling Template Association Step 20 • 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, page 3-8). • E-Line Name is only applicable for IOS XR devices. If you would like to enable template association for this policy, click the Next button. See the section Enabling Template Association, page 3-23 for information about this feature.
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy Enabling Template Association Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 4 Managing a FlexUNI/EVC Ethernet Service Request This chapter provides information on how to provision a FlexUNI/EVC Ethernet service request.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Creating a FlexUNI/EVC Service Request • 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details 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).
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details 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 ISC database holds within the editing flow of the service request. Note The Policy field is read-only.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details 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 FlexUNI/EVC policy, which in this case is pseudowire core connectivity.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Figure 4-2 EVC Service Request Details Window for VPLS Core Connectivity Perform the following steps to set the attributes in the first section of the Service Request Details window: 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details 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. Step 7 • When AutoPick VPLS VPN ID is checked, ISC allocates a VPLS VPN ID from the ISC-managed VC ID resource pool. In this case, the text field for the VPLS VPN ID option is non-editable.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Figure 4-3 EVC Service Request Details Window for Local Core Connectivity Perform the following steps to set the attributes in the first section of the Service Request Details window: 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details • 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-FlexUNI links will have the Service Provider VLAN as the bridge domain ID. On the other hand, if no FlexUNI links are added, the Service Provider VLAN will be allocated first and this will be used as the bridge domain ID when FlexUNI links are added.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details See the appropriate section, depending on which type of link you are setting up: Note • Setting Direct Connect Links, page 4-10 • Setting Links with L2 Access Nodes, page 4-20 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, page 4-10.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details 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 FlexUNI check box for the link.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Step 9 • 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. 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Step 14 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Step 19 Step 20 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Figure 4-5 is an example of a direct connect link for a Cisco 7600 device running IOS with pseudowire core connectivity, configure bridge domain enabled, and the FlexUNI check box checked.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Figure 4-7 Step 23 Standard UNI Details Window (Cisco ASR 9000, Configure Bridge Domain not Enabled) 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 24 Choose an Encapsulation type from the drop-down list. The choices are: • DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Note For detailed coverage of setting up VLAN translation, see Appendix C, “Setting Up VLAN Translation.” This attribute is not displayed for IOS XR devices. Step 28 Check the N-PE Pseudo-wire on SVI check box to have ISC generate forwarding commands under SVIs (switch virtual interfaces). By default, this check box is not checked. In this case, ISC generates forwarding commands under the service instance.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Step 30 If you checked the PW Tunnel Selection check box, enter the TE tunnel ID in the Interface Tunnel text field. Usage notes: • ISC 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details 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: Step 35 • The AutoPick Bridge Domain Name attribute appears only for Cisco ASR 9000 devices.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Setting the Service Request Details Usage notes: • If no value is specified for the E-Line Name, ISC 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Modifying the FlexUNI/EVC Service Request • Choosing the UNI interface. • Setting the link as a FlexUNI link. • Editing the standard and FlexUNI link attributes. The main difference in setting up links with L2 access does is specifying the NPC details.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Using Templates and Data Files with a FlexUNI/EVC Ethernet Service Request Step 4 Modify any of the attributes, as desired. See the sections start with “Setting the Service Request Details” section on page 4-2 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Saving the FlexUNI/EVC Service Request Figure 4-8 Sample Templates Association Window As shown in Figure 4-8, the 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.
Chapter 4 Managing a FlexUNI/EVC Ethernet Service Request Saving the FlexUNI/EVC Service Request Step 2 If, however, the FlexUNI 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 FlexUNI/EVC Ethernet service request, see Deploying Service Requests, page 11-1.
CH A P T E R 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy This chapter contains an overview of FlexUNI/EVC ATM-Ethernet Interworking support in ISC, as well as the basic steps to create a FlexUNI/EVC ATM-Ethernet Interworking policy.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Defining the FlexUNI/EVC ATM-Ethernet Interworking Policy • Supported platforms: – ATM interworking is supported on the Cisco 7600 with ES-20 cards. – ASR 9000 device is supported for IOS XR 3.7.3 and IOS XR 3.9. Because there are no ATM interfaces on the Cisco ASR 9000, ISC does not support interworking on the ASR 9000 for ATM interfaces. Only Ethernet interfaces are supported.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Defining the FlexUNI/EVC ATM-Ethernet Interworking Policy Figure 5-1 EVC Policy Editor - Service Type Step 4 Enter a Policy Name for the FlexUNI/EVC ATM-Ethernet Interworking policy. Step 5 Choose the Policy Owner for the FlexUNI/EVC policy. There are three types of FlexUNI/EVC policy ownership: • Customer ownership • Provider ownership • Global ownership—Any service operator can make use of this policy.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Service Options Setting the Service Options This section describes how to set the service options for the FlexUNI/EVC policy, as shown in Figure 5-2. Figure 5-2 EVC Policy Editor - Service Options Window The Editable check box gives you the option of making a field editable.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Service Options • If the check box is unchecked, zero or more links can use the FlexUNI/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 FlexUNI/EVC support being added in the future.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the ATM Interface Attributes Note Step 4 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.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the FlexUNI Attributes Figure 5-3 EVC Policy Editor - ATM Interface Attributes Window To set the ATM interface attributes, perform the following steps. Step 7 Choose the Transport Mode from the drop-down list. The choices are: Step 8 • VP—Virtual path mode. This is the default. • VC—Virtual circuit mode. Choose the ATM Encapsulation from the drop-down list. • Step 9 AAL5SNAP Click Next.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the FlexUNI Attributes Figure 5-4 EVC Policy Editor - FlexUNI Attribute Window FlexUNI 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 FlexUNI service attributes, perform the following steps.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the FlexUNI Attributes Step 2 Check the AutoPick Service Instance Name check box to have ISC 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.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the FlexUNI Attributes Step 6 Continue with the steps contained in the next section, Setting the VLAN Matching Criteria Attributes, page 5-10. Setting the VLAN Matching Criteria Attributes Prior to the introduction of the FlexUNI capability, service providers could either deploy service-multiplexed services (ERS/ERMS or EVPL/EVCS) or service-bundled services on a single port.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the FlexUNI Attributes • 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 FlexUNI VLAN rewrite criteria attributes, perform the following steps.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes 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 5-1.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes 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, page 5-4). 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.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes 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.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes d. In the Secure MAC Addresses field, enter one or more Ethernet MAC addresses. Figure 5-6 Step 11 UNI Port Security Check the Enable Storm Control check box (see Figure 5-7) 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.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes Step 13 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.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes Table 5-2 Use Bridge Domain FlexUNI N-PE Pseudowire on SVI True True True True False Step 14 Use Cases for Hybrid Configuration for FlexUNI /EVC Service Requests True True False N/A CLIs Generated • xconnect under VLAN interface. • Service instance under main interface. • xconnect under service instance. • Service instance under main interface. • xconnect under service instance.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Setting the Interface Attributes 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. ISC uses the tunnel information to create and provision a pseudowire class that describes the pseudowire connection between two N-PEs.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Enabling Template Association See the section Enabling Template Association, page 5-19 for information about this feature. Step 21 To save the FlexUNI/EVC policy, click Finish. To create a service request based on a FlexUNI/EVC ATM-Ethernet Interworking policy, see Chapter 6, “Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request.
Chapter 5 Creating a FlexUNI/EVC ATM-Ethernet Interworking Policy Enabling Template Association Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request This chapter provides information on how to provision a FlexUNI/EVC ATM-Ethernet Interworking service request.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Creating a FlexUNI/EVC ATM-Ethernet Interworking Service Request • Note Choose a VPN. When working with VPN objects in the context of FlexUNI/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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Setting the Service Request Details After you have selected the FlexUNI/EVC policy to be used as the basis of the service request, the EVC Service Request Editor window appears.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Figure 6-1 EVC Service Request Details Window for Pseudowire Core Connectivity Perform the following steps to set the attributes in the first section of the Service Request Details window: 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details 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, ISC allocates a VC ID for pseudowires from the ISC-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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details 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, page 6-8. Step 10 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes, page 6-22.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Step 10 To set up links with L2 access nodes, see the section Setting Links with L2 Access Nodes, page 6-22. 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Figure 6-3 FlexUNI Details Window All of the fields in the FlexUNI 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Step 11 • For example configlets, see FlexUNI/EVC (No AutoPick Service Instance Name, No Service Instance Name), page A-42, FlexUNI/EVC (User-Provided Service Instance Name, Pseudowire Core Connectivity), page A-43, and FlexUNI/EVC (User-Provided Service Instance Name, Local Core Connectivity), page A-44. • This attribute is not displayed for IOS XR devices.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details – 10, 15,17 – 10-15 – 10-15,17-20 – 10,20-25 • Step 16 Note Step 17 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 Match Inner and Outer Tags check box is unchecked, enter the outer VLAN tag in the Outer VLAN ID field.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details – 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Figure 6-5 is an example of a direct connect link for a Cisco ASR 9000 running IOS XR with pseudowire core connectivity, configure bridge domain enabled, and the FlexUNI check box checked.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details The choices are: • DOT1QTRUNK—Configures the UNI as a trunk with 802.1q encapsulation. If the UNI belongs to a directly connected and FlexUNI 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Step 29 • 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Step 33 • 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 ISC.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Note • Step 37 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, page 2-14. L2VPN Group Name is only applicable for IOS XR devices. Enter an E-Line Name to specify the point-to-point (p2p) E-line name.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Step 1 In the Direct Connect Links section of the FlexUNI(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 FlexUNI/EVC service request is based on an ATM-Ethernet Interworking policy type.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details 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).
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details • Step 12 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. 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.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Setting the Service Request Details Step 19 If you want to set up links with L2 access nodes for this service request, see Setting Links with L2 Access Nodes, page 6-22. Step 20 When you have completed setting the attributes in the FlexUNI(EVC) Service Request Editor window, click the Save button at the bottom of the window to save the settings and create the FlexUNI/EVC service request.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Modifying the FlexUNI/EVC Service Request Step 3 For details about editing link attributes, adding or deleting links, or using the FlexUNI check box, see the corresponding steps in the section Setting Direct Connect Links, page 6-8.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Using Templates and Data Files with a FlexUNI/EVC Service Request Using Templates and Data Files with a FlexUNI/EVC Service Request ISC 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 ISC Template Manager functionality. Templates can be associated at the policy level on a per-device role basis.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Saving the FlexUNI/EVC Service Request If the FlexUNI/EVC service request is successfully created, you will see the service request list window, similar to what appears in Figure 6-9. Figure 6-9 FlexUNI/EVC Service Request Created The newly created FlexUNI/EVC service request is added with the state of REQUESTED, as shown in the figure.
Chapter 6 Managing a FlexUNI/EVC ATM-Ethernet Interworking Service Request Saving the FlexUNI/EVC Service Request Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 7 Creating an L2VPN Policy This chapter covers the basic steps to create an L2VPN policy.
Chapter 7 Creating an L2VPN Policy Defining an L2VPN Policy • Frame Relay over MPLS (FRoMPLS) • ATM over MPLS (ATMoMPLS) To define an L2VPN policy in ISC, perform the following steps. Step 1 Choose Service Design > Policies. The Policies window appears. Step 2 Click Create. Step 3 Choose L2VPN (P2P) Policy. When you choose L2VPN (P2P) Policy, the L2VPN (Point to Point) Policy Creation window appears. Step 4 Choose L2VPN on MPLS Core. The window in Figure 7-1 appears.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy with a CE Step 8 Choose the Service Type of the L2VPN policy. There are four service types for L2VPN policies: • L2VPN ERS (EVPL) • L2VPN EWS (EPL) • Frame Relay • ATM Subsequent sections of this chapter cover setting up the policies for each of these services.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy with a CE Step 1 Click Next. The window in Figure 7-3 appears. 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 L2VPN policy can modify the editable parameter during L2VPN service request creation. Figure 7-3 Step 2 Ethernet ERS (EVPL) with CE Policy Attributes Check the Standard UNI Port check box to enable port security.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy with a CE • Ethernet • FastEthernet • GE-WAN • GigabitEthernet • TenGigabitEthernet • TenGigE The value defined here functions as a filter to restrict the interface types an operator can see during L2VPN service request creation. Step 4 Enter an Interface Format as the slot number/port number for the CE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0).
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy with a CE Step 12 Enter a VLAN NAME (optional) to specify a name to describe the VLAN. The name must be one token (no spaces allowed.) The limit for the VLAN name is 32 characters. The name has to be unique. Step 13 Check the Use PseudoWireClass check box to enable the selection of a pseudowire class. This attribute is only applicable for IOS XR devices.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy with a CE Step 21 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 22 Choose a UNI Port Type.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy with a CE Figure 7-5 Step 25 Enable Storm Control Check the N-PE Pseudo-wire On SVI check box to configure the pseudowire connection on the switched virtual interface of the OSM card. This check box is checked by default. If the check box is not checked, the pseudowire will be provisioned on the subinterface of the PFC card, if it is available. This option is only available for C76xx devices.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy without a CE Step 29 Click Finish. Defining an Ethernet ERS (EVPL) Policy without a CE This section describes defining an Ethernet ERS (EVPL) policy without a CE present. Figure 7-6 is an example of the first page of this policy. Figure 7-6 Ethernet ERS (EVPL) Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-7 appears.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy without a CE Figure 7-7 Step 2 Ethernet ERS (EVPL) without CE Policy Attributes Choose a N-PE/U-PE Interface Type from the drop-down list. You can choose a particular interface as a CE, N-PE, or U-PE interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy without a CE Note Step 4 The Standard UNI Port attribute will be unavailable within service requests based on this policy if the UNI is on an N-PE device running IOS XR. Enter an Interface Format as the slot number/port number for the PE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0).
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy without a CE Step 13 Choose an L2VPN Group Name from the drop-down list. The choices are: • ISC • VPNSC This attribute is used for provisioning the L2VPN group name on IOS XR devices. Note Step 14 The choices in the drop-down list are derived from a configurable DCPL property.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy without a CE The choices are: • Access Port • Trunk with Native VLAN Note Step 23 Enter a UNI Port Type only if the encapsulation type is DEFAULT. Check the UNI Port Security check box (see Figure 7-8) 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.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet ERS (EVPL) Policy without a CE Step 25 Check the N-PE Pseudo-wire On SVI check box to configure the pseudowire connection on the switched virtual interface of the OSM card. This check box is checked by default. If the check box is not checked, the pseudowire will be provisioned on the subinterface of the PFC card, if it is available. This option is only available for C76xx devices.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE Defining an Ethernet EWS (EPL) Policy with a CE This section describes defining an Ethernet EWS (EPL) policy with CE present. Figure 7-10 is an example of the first page of this policy. Figure 7-10 Ethernet EWS (EPL) Policy with a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-11 appears. The Editable check box gives you the option of making a field editable.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE Figure 7-11 Step 2 Ethernet EWS (EPL) with CE Policy Attributes 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.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE Step 3 Choose an Interface Type from the drop-down list. You can choose a particular interface on a U-PE or N-PE interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.) • Port-Channel (A bundle of ports that share the same characteristics—this gives the service provider the ability to aggregate bandwidth and protection.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE Step 10 Check the VLAN ID AutoPick check box if you want ISC to choose a VLAN ID. If you do not check this check box, you will be prompted to provide the VLAN in a Provider VLAN ID field during service activation. Step 11 Check the VC ID AutoPick check box if you want ISC to choose a VC ID. If you do not check this check box, you will be prompted to provide the VC ID in a VC ID field during service activation.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE Step 20 Check the Use Existing ACL Name check box if you want assign your own named access list to the port. By default, this check box is not checked and ISC automatically assigns a MAC-based ACL on the customer facing UNI port, based on values you enter in UNI MAC addresses (below). Step 21 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step).
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE Figure 7-13 Step 25 Enable Storm Control Check the Protocol Tunnelling check box (see Figure 7-14) 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. Figure 7-14 Protocol Tunnelling For each protocol that you choose, enter the shutdown threshold and drop threshold for that protocol: Step 26 a.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy with a CE This check box is checked by default. If the check box is not checked, the pseudowire will be provisioned on the subinterface of the PFC card, if it is available. This option is only available for C76xx devices. Note Step 27 The N-PE Pseudo-wire On SVI attribute will be unavailable within service requests based on this policy for devices running IOS XR. Enter the MTU Size in bytes.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy without a CE Defining an Ethernet EWS (EPL) Policy without a CE This section describes how to define an Ethernet EWS (EPL) policy without a CE present. Figure 7-15 is an example of the first page of this policy. Figure 7-15 Ethernet EWS (EPL) Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-16 appears. The Editable check box gives you the option of making a field editable.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy without a CE Figure 7-16 Step 2 Ethernet EWS (EPL) without CE Policy Attributes Choose a N-PE/U-PE Interface Type from the drop-down list. You can choose a particular interface as a CE, N-PE, or U-PE interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy without a CE Step 3 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 The Standard UNI Port attribute will be unavailable within service requests based on this policy if the UNI is on an N-PE device running IOS XR.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy without a CE Step 10 Check the VLAN ID AutoPick check box if you want ISC to choose a VLAN ID. If you do not check this check box, you will be prompted to provide the VLAN in a Provider VLAN ID field during service activation. Step 11 Check the VC ID AutoPick check box if you want ISC to choose a VC ID. If you do not check this check box, you will be prompted to provide the VC ID in a VC ID field during service activation.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy without a CE Step 20 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step). Note Step 21 ISC 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. Enter one or more Ethernet MAC addresses in UNI MAC addresses.
Chapter 7 Creating an L2VPN Policy Defining an Ethernet EWS (EPL) Policy without a CE Figure 7-18 Step 24 Enable Storm Control Check the Protocol Tunnelling check box (see Figure 7-14) 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. Figure 7-19 Protocol Tunnelling For each protocol that you check, enter the shutdown threshold and drop threshold for that protocol: Step 25 a.
Chapter 7 Creating an L2VPN Policy Defining a Frame Relay Policy with a CE This check box is checked by default. If the check box is not checked, the pseudowire will be provisioned on the subinterface of the PFC card, if it is available. This option is only available for C76xx devices. Note Step 26 The N-PE Pseudo-wire On SVI attribute will be unavailable within service requests based on this policy for devices running IOS XR. Enter the MTU Size in bytes.
Chapter 7 Creating an L2VPN Policy Defining a Frame Relay Policy with a CE Note Frame Relay policies are not supported for devices running IOS XR. Figure 7-20 Frame Relay Policy with a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-21 appears. 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 L2VPN policy can modify the editable parameter during L2VPN service request creation.
Chapter 7 Creating an L2VPN Policy Defining a Frame Relay Policy with a CE Step 3 • Serial • MFR • POS • Hssi • BRI Enter an Interface Format as the slot number/port number for the CE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0). This is especially useful to specify here if you know that the link will always go through a particular interface’s slot/port location on all or most of the network devices in the service.
Chapter 7 Creating an L2VPN Policy Defining a Frame Relay Policy without a CE Defining a Frame Relay Policy without a CE This section describes how to define a Frame Relay policy without a CE present. Figure 7-22 is an example of the first page of this policy. Figure 7-22 Frame Relay Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-23 appears. The Editable check box gives you the option of making a field editable.
Chapter 7 Creating an L2VPN Policy Defining a Frame Relay Policy without a CE Step 2 Choose the N-PE/U-PE Interface Type for the CE from the drop-down list. The choices are: Step 3 • ANY • Serial • MFR • POS • Hssi • BRI Enter an Interface Format as the slot number/port number for the PE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0).
Chapter 7 Creating an L2VPN Policy Defining an ATM Policy with a CE Defining an ATM Policy with a CE This section describes how to define an ATM policy with CE present. Figure 7-24 is an example of the first page of this policy. Figure 7-24 ATM Policy with a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-25 appears. The Editable check box gives you the option of making a field editable.
Chapter 7 Creating an L2VPN Policy Defining an ATM Policy with a CE Step 2 Choose the Transport Mode from the drop-down list. The choices are: • VP—Virtual path mode. This is the default. • VC—Virtual circuit mode. • PORT—Port mode. (Only supported for the IOS XR 3.7 platform.) Note Step 3 If you choose PORT as the transport mode, the attributes ATM VCD/Sub-interface # and ATM VPI will be disabled in the Link Attributes window of the service request based on this policy.
Chapter 7 Creating an L2VPN Policy Defining an ATM Policy with a CE This attribute is used for provisioning the L2VPN group name on IOS XR devices. Note Step 9 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, page 2-14. Enter an E-Line Name to specify the point-to-point (p2p) E-line name.
Chapter 7 Creating an L2VPN Policy Defining an ATM Policy without a CE Defining an ATM Policy without a CE This section describes how to define an ATM policy without a CE present. Figure 7-26 is an example of the first page of this policy. Figure 7-26 ATM Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 7-27 appears. The Editable check box gives you the option of making a field editable.
Chapter 7 Creating an L2VPN Policy Defining an ATM Policy without a CE Step 2 Choose the Transport Mode from the drop-down list. The choices are: • VP—Virtual path mode. This is the default. • VC—Virtual circuit mode. • PORT—Port mode. (Only supported for the IOS XR 3.7 platform.) Note Step 3 If you choose PORT as the transport mode, the attributes ATM VCD/Sub-interface # and ATM VPI will be disabled in the Link Attributes window of the service request based on this policy.
Chapter 7 Creating an L2VPN Policy Defining an ATM Policy without a CE Note Step 9 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, page 2-14. Enter an E-Line Name to specify the point-to-point (p2p) E-line name. This attribute is only applicable for IOS XR devices.
CH A P T E R 8 Managing an L2VPN Service Request This chapter covers the basic steps to provision an ERS (EVPL), EWS (EPL), ATM, or Frame Relay L2VPN service.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request The following steps are involved in creating a service request for Layer 2 connectivity between customer sites: • Choose a CE Topology for ERS (EVPL)/Frame Relay/ATM services. • Choose the endpoints (CE and PE) that must be connected. For each end-to-end Layer 2 connection, ISC creates an end-to-end wire object in the repository for the service request. • Choose a CE or PE interface.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-1 L2VPN Service Request Editor Perform the following steps. Step 1 Choose a Topology from the drop-down list. If you choose Full Mesh, each CE will have direct connections to every other CE. If you choose Hub and Spoke, then only the Hub CE has connection to each Spoke CE and the Spoke CEs do not have direct connection to each other.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Step 3 Click Select CE in the CE column. The CPE for Attachment Circuit window appears. (See Figure 8-3.) This window displays the list of currently defined CEs. a. From the Show CPEs with drop-down list, you can display CEs by Customer Name, by Site, or by Device Name. b. You can use the Find button to either search for a specific CE, or to refresh the display. c.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Note ISC 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.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-6 NPCs Created For ERS (EVPL), ATM, and Frame Relay, the End-to-End Wire Editor window appears. (See Figure 8-7.) Figure 8-7 Step 11 End-to-End Wire Editor The VPN for this service request appears in the VPN field. If there is more than one VPN, click Select VPN to choose a VPN. The VPN for L2VPN service request window appears. Step 12 Choose a VPN Name and click Select.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-8 Step 14 Step 15 End-to-End Wire Created Specify remaining items in the End-to-End-Wire Editor window as necessary for your configuration: • You can choose any of the blue highlighted values to edit the End-to-End Wire. • You can edit the AC link attributes to change the default policy settings. After you edit these fields, the blue link changes from Default to Changed.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Creating an EWS (EPL) L2VPN Service Request with a CE This section includes detailed steps for creating an L2VPN service request with a CE present for EWS (EPL). If you are creating an L2VPN service request for an ERS (EVPL), ATM, or Frame Relay policy, go to Creating an ERS (EVPL), ATM, or Frame Relay L2VPN Service Request with a CE, page 8-2. Perform the following steps.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-10 Step 6 End-To-End Wire Editor • You can enter a description for the service request in the first Description field. The description will show up in this window and also in the Description column of the Service Requests window. The maximum length for this field is 256 characters. • You can enter a description for each end-to-end wire in the Description field provided for each wire.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-12 CPE for Attachment Circuit This window displays the list of currently defined CEs. a. From the Show CPEs with drop-down list, you can display CEs by Customer Name, by Site, or by Device Name. b. You can use the Find button to either search for a specific CE, or to refresh the display. c. You can set the Rows per page to 5, 10, 20, 30, 40, or All. Step 8 In the Select column, choose a CE for the L2VPN link.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Step 13 Click AC1 Link Attributes and edit the attributes if desired. For more information, see the section Modifying the L2VPN Service Request, page 8-20. Step 14 Click OK. Step 15 Repeat Steps 6 through 14 for AC2. Step 16 Click OK. You see a window like Figure 8-14. Figure 8-14 Step 17 Attachment Circuits Selected Click Save. The EWS (EPL) service request is created and saved in ISC.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-15 Step 2 L2VPN Service Request Editor Choose a Topology from the drop-down list. If you choose Full Mesh, each CE will have direct connections to every other CE. If you choose Hub and Spoke, then only the Hub CE has connection to each Spoke CE and the Spoke CEs do not have direct connection to each other.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-17 Select PE Device This window displays the list of currently defined PEs. a. The Show PEs with drop-down list shows PEs by customer name, by site, 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 page to be set to 5, 10, 20, 30, 40, or All.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Note Step 9 ISC 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.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Step 13 After you specify all the PEs, ISC creates the links between PEs based on the Topology that you chose. Step 14 Click OK. For ERS (EVPL), ATM, and Frame Relay, the End-to-End-Wire Editor window appears. (See Figure 8-21.) Figure 8-21 Step 15 End-to-End Wire Editor The VPN for this service request appears in the Select VPN field. If there is more than one VPN, click Select VPN to choose a VPN.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Step 17 When you are finished editing the end-to-end wires, click Save. The service request is created and saved into ISC. Creating an EWS (EPL) L2VPN Service Request without a CE This section includes detailed steps for creating an L2VPN service request without a CE present for EWS (EPL).
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-23 Step 5 End-To-End Wire Editor Click Add AC in the Attachment Circuit (AC1) column. The Attachment Tunnel Editor window appears. (See Figure 8-24.) Figure 8-24 Step 6 Select the PE for the Attachment Circuit Click Select N-PE/PE-AGG/U-PE. The Select PE Device window appears. (See Figure 8-25.) Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Figure 8-25 PE for Attachment Circuit This window displays the list of currently defined PEs. a. From the Show PEs with drop-down list, you can display PEs by Customer Name, by Site, or by Device Name. b. You can use the Find button to either search for a specific PE, or to refresh the display. c. You can set the Rows per page to 5, 10, 20, 30, 40, or All. Step 7 In the Select column, choose a PE for the L2VPN link.
Chapter 8 Managing an L2VPN Service Request Creating an L2VPN Service Request Step 10 If the PE role type is N-PE, the columns Circuit Selection and Circuit Details are disabled. In this case, skip to Step 13. Step 11 If the PE role type is U-PE, click Select one circuit in the Circuit Selection column. The Select NPC window appears. (See Figure 8-27.
Chapter 8 Managing an L2VPN Service Request Modifying the L2VPN Service Request Figure 8-29 Step 15 Attachment Circuit Selected Click AC1 Link Attributes and edit the attributes, if desired. For more information, see the section Modifying the L2VPN Service Request, page 8-20. Step 16 Repeat Steps 5 through 14 for AC2. Step 17 Specify remaining items in the End-to-End-Wire Editor window, as necessary for your configuration.
Chapter 8 Managing an L2VPN Service Request Modifying the L2VPN Service Request Figure 8-30 L2VPN Service Activation Step 2 Check a check box for a service request. Step 3 Click Edit. The End-to-End-Wire Editor window appears. (See Figure 8-31.) Figure 8-31 Step 4 End-to-End Wire Editor Modify any of the attributes, as desired: • The VPN for this service request appears in the Select VPN field. If this request has more than one VPN, click Select VPN to choose a VPN.
Chapter 8 Managing an L2VPN Service Request Modifying the L2VPN Service Request • If the policy was set up for you to define a VC ID manually, enter it into the empty VC ID field. If policy was set to “auto pick” the VC ID, ISC will supply a VC ID, and this field will not be editable. In the case where you supply the VC ID manually, if the entered value is in the provider’s range, ISC validates if the entered value is available or allocated.
Chapter 8 Managing an L2VPN Service Request Modifying the L2VPN Service Request Figure 8-32 Link Attributes Window Step 6 Edit any of the link attributes, as desired. Step 7 To add a template and data file to an attachment circuit, choose a Device Name, and click Add under Templates. The Add/Remove Templates window appears. (See Figure 8-33.) Note To add a template to an attachment circuit, you must have already created the template.
Chapter 8 Managing an L2VPN Service Request Modifying the L2VPN Service Request The Template Data File Chooser window appears. (See Figure 8-34.) Figure 8-34 Step 9 Template Datafile Chooser In the left pane, navigate to and select a template. The associated data files are listed in rows in the main window, as shown in Figure 8-34. Step 10 Check the data file that you want to add and click Accept. The Add/Remove Templates window appears with the template displayed. (See Figure 8-35.
Chapter 8 Managing an L2VPN Service Request Modifying the L2VPN Service Request Figure 8-36 Note Step 15 Link Attributes with Template Added For more information about using templates and data files in service requests, see Appendix B, “Working with Templates and Data Files.” Click OK. The Service Request Editor window appears showing the default for AC1 changed. (See Figure 8-37.) Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
Chapter 8 Managing an L2VPN Service Request Saving the L2VPN Service Request Figure 8-37 Step 16 Service Request Editor with Link Attributes Changed. When you are finished editing the end-to-end wires, click Save. Saving the L2VPN Service Request To save an L2VPN service request, perform the following steps. Step 1 When you are finished with Link Attributes for all the Attachment Circuits, click Save to finish the L2VPN service request creation.
CH A P T E R 9 Creating a VPLS Policy This chapter contains the basic steps to create a VPLS policy.
Chapter 9 Creating a VPLS Policy Defining a VPLS Policy A policy is a template of most of the parameters needed to define a VPLS service request. After you define it, a VPLS policy can be used by all the VPLS service requests that share a common set of characteristics. You create a new VPLS policy whenever you create a new type of service or a service with different parameters. VPLS policy creation is normally performed by experienced network engineers.
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy with a CE There are two core types for VPLS policies: Step 8 • MPLS—running on an IP network • Ethernet—all PEs are on an Ethernet provider network Choose the Service Type of the VPLS policy. There are two service types for VPLS policies: Step 9 • Ethernet Relay Multipoint Service (ERMS). (The MEF name for ERMS is EVP-LAN.) • Ethernet Multipoint Service (EMS). (The MEF name for EMS is EP-LAN.
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy with a CE Figure 9-3 Step 2 MPLS/ERMS (EVP-LAN) with a CE Policy Attributes Choose an Interface Type from the drop-down list. You can choose a particular interface on a CE, N-PE, PE-AGG, or U-PE interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy with a CE This is especially useful to specify here if you know that the link will always go through a particular interface’s slot/port location on all or most of the network devices in the service. Step 4 Choose a CE Encapsulation type. The choices are: • DOT1Q • DEFAULT If DEFAULT is the CE encapsulation type, ISC shows another field for the UNI port type. Step 5 Check the Standard UNI Port check box to enable port security.
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy with a CE Step 17 Check the Use Existing ACL Name check box if you want assign your own named access list to the port. By default, this check box is not checked and ISC automatically assigns a MAC-based ACL on the customer facing UNI port, based on values you enter in UNI MAC addresses (below). Step 18 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step).
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy without a CE Figure 9-5 Step 23 Enable Storm Control Click the Next button, if you want to enable template support for the policy. The Template Association window appears. In this window, you can enable template support and, optionally, associate templates and data files with the policy.
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy without a CE Step 1 Click Next. The window in Figure 9-7 appears. 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 VPLS policy can modify the editable parameter during VPLS service request creation. Figure 9-7 Step 2 MPLS/ERMS (EVP-LAN) without a CE Policy Attributes Choose an Interface Type from the drop-down list.
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy without a CE 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 4 Enter an Interface Format as the slot number/port number for the CE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0).
Chapter 9 Creating a VPLS Policy Defining an MPLS/ERMS (EVP-LAN) Policy without a CE Step 17 Check the Use Existing ACL Name check box if you want assign your own named access list to the port. By default, this check box is not checked and ISC automatically assigns a MAC-based ACL on the customer facing UNI port, based on values you enter in UNI MAC addresses (below). Step 18 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step).
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy with a CE Figure 9-9 Step 23 Enable Storm Control Click the Next button, if you want to enable template support for the policy. The Template Association window appears. In this window, you can enable template support and, optionally, associate templates and data files with the policy.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy with a CE Perform the following steps. Step 1 Click Next. The window in Figure 9-11 appears. 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 VPLS policy can modify the editable parameter during VPLS service request creation.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy with a CE The value defined here functions as a filter to restrict the interface types an operator can see during VPLS service request creation. If defined as ANY, the operator can see all interface types. Step 3 Enter an Interface Format as the slot number/port number for the CE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0).
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy with a CE The name must be one token (no spaces allowed.) The limit for the VLAN name is 32 characters. The name has to be unique. Two VLANs cannot share the same name. Step 16 Enter the System MTU in bytes. The maximum transmission unit (MTU) size is configurable and optional. ISC does not perform an integrity check for this customized value.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy with a CE Figure 9-12 Step 21 UNI Port Security Check the Enable Storm Control check box (see Figure 9-13) 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.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy without a CE Step 23 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. Tunnel VTP—Enable Layer 2 tunnelling on VLAN Trunk Protocol (VTP). e. VTP threshold—Enter the number of packets per second to be received before the interface is shut down. f.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy without a CE Figure 9-15 MPLS/EMS (EP-LAN) Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 9-16 appears. The Editable check box gives you the option of making a field editable. If you check Editable check box, the service operator who is using this VPLS policy can modify the editable parameter during VPLS service request creation.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy without a CE Figure 9-16 Step 2 MPLS/EMS (EP-LAN) without a CE Policy Attributes Choose an Interface Type from the drop-down list. You can choose a particular interface on a N-PE, U-PE, or PE-AGG interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy without a CE Step 4 Enter an Interface Format as the slot number/port number for the PE interface (for example, 1/0 indicates that the interface is located at slot 1, port 0). This is especially useful to specify here if you know that the link will always go through a particular interface’s slot/port location on all or most of the network devices in the service. Step 5 Choose a N-PE/U-PE Encapsulation type.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy without a CE The maximum transmission unit (MTU) size is configurable and optional. ISC 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. ISC supports, ranges for different platforms, as specified below. The range is 1500 to 9216.
Chapter 9 Creating a VPLS Policy Defining an MPLS/EMS (EP-LAN) Policy without a CE Figure 9-17 Step 21 UNI Port Security Check the Enable Storm Control check box (see Figure 9-18) 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.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy with a CE Step 23 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. Tunnel VTP—Enable Layer 2 tunnelling on VLAN Trunk Protocol (VTP). e. VTP threshold—Enter the number of packets per second to be received before the interface is shut down. f.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy with a CE Figure 9-20 Ethernet/ERMS (EVP-LAN) Policy with a CE Perform the following steps. Step 1 Click Next. The window in Figure 9-21 appears. 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 VPLS policy can modify the editable parameter during VPLS service request creation.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy with a CE Figure 9-21 Step 2 Ethernet ERMS (EVP-LAN) with a CE Policy Attributes Choose an Interface Type from the drop-down list. You can choose a particular interface on a CE, N-PE, U-PE, or PE-AGG interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy with a CE Step 4 Choose a CE Encapsulation type. The choices are: • DOT1Q • DEFAULT If DEFAULT is the CE encapsulation type, ISC shows another field for the UNI port type. Step 5 Check the Standard UNI Port check box to enable port security. This is the default.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy with a CE Step 17 Check the Use Existing ACL Name check box if you want assign your own named access list to the port. By default, this check box is not checked and ISC automatically assigns a MAC-based ACL on the customer facing UNI port, based on values you enter in UNI MAC addresses (below). Step 18 Enter a Port-Based ACL Name (if you checked the Use Existing ACL Name check box, as mentioned in the previous step).
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy without a CE Figure 9-23 Step 23 Enable Storm Control Click the Next button, if you want to enable template support for the policy. The Template Association window appears. In this window, you can enable template support and, optionally, associate templates and data files with the policy.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 9-25 appears. 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 VPLS policy can modify the editable parameter during VPLS service request creation.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy without a CE The value defined here functions as a filter to restrict the interface types an operator can see during VPLS service request creation. If defined as ANY, the operator can see all interface types. Step 3 Check the Standard UNI Port check box to enable port security. This is the default.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy without a CE Step 16 Enter a VLAN NAME (optional) to specify a name to describe the VLAN. The name must be one token (no spaces allowed.) The limit for the VLAN name is 32 characters. The name has to be unique. Two VLANs cannot share the same name. Step 17 Check the Use Existing ACL Name check box if you want assign your own named access list to the port.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/ERMS (EVP-LAN) Policy without a CE 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.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy with a CE Defining an Ethernet/EMS (EP-LAN) Policy with a CE This section describes defining a VPLS policy with an Ethernet core type and an EMS (EP-LAN) service type with a CE present. Figure 9-28 is an example of the first page of this policy. Figure 9-28 Ethernet/EMS (EP-LAN) Policy with CE Present Perform the following steps. Step 1 Click Next. The window in Figure 9-29 appears.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy with a CE Figure 9-29 Step 2 Ethernet/EMS (EP-LAN) with a CE Policy Attributes Choose an Interface Type from the drop-down list. You can choose a particular interface on a CE, N-PE, U-PE, or PE-AGG interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy with a CE Step 4 Choose a CE Encapsulation type. The choices are: Note Step 5 • DOT1Q • DEFAULT When creating a service request based on the Ethernet/EMS (EP-LAN) with CE policy, the Encapsulation attribute is ignored. Therefore, setting this value has no effect. Check the Standard UNI Port check box to enable port security. This is the default.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy with a CE The maximum transmission unit (MTU) size is configurable and optional. The default size is 9216, and the range is 1500 to 9216. ISC 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 ISC 6.0, different platforms support different ranges.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy with a CE Figure 9-30 Step 21 UNI Port Security Check the Enable Storm Control check box (see Figure 9-31) 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.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE Step 23 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. Tunnel VTP—Enable Layer 2 tunnelling on VLAN Trunk Protocol (VTP). e. VTP threshold—Enter the number of packets per second to be received before the interface is shut down. f.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE Figure 9-33 Ethernet/EMS (EP-LAN) Policy without a CE Perform the following steps. Step 1 Click Next. The window in Figure 9-34 appears. 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 VPLS policy can modify the editable parameter during VPLS service request creation.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE Figure 9-34 Step 2 Ethernet/EMS (EP-LAN) without CE Policy Attributes Choose an Interface Type from the drop-down list. You can choose a particular interface on a CE, N-PE, U-PE, or PE-AGG interface based on the service provider’s POP design. The interfaces are: • ANY (Any interface can be chosen.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE This is especially useful to specify here if you know that the link will always go through a particular interface’s slot/port location on all or most of the network devices in the service. Step 5 Choose a N-PE/U-PE Encapsulation type. The choices are: Note • DOT1Q • DEFAULT When creating a service request based on the Ethernet/EMS (EP-LAN) without CE policy, the Encapsulation attribute is ignored.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE Step 17 • For the 3750 and 3550 platforms, the MTU range is 1500-1546. • For the 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-9216. However, ISC uses 9216 in both cases.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE 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.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE Step 23 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. Click the Next button, if you want to enable template support for the policy. The Template Association window appears.
Chapter 9 Creating a VPLS Policy Defining an Ethernet/EMS (EP-LAN) Policy without a CE Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 10 Managing a VPLS Service Request This chapter contains the basic steps to provision a VPLS service.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request Creating a VPLS Service Request To create a VPLS service request, perform the following steps. Step 1 Choose Service Inventory > Inventory and Connection Manager > Service Requests. The Service Requests window appears. Step 2 Click Create. Step 3 Choose VPLS from the drop-down list. VPLS service requests must be associated with a VPLS policy.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request with a CE Step 2 Click Select VPN to choose a VPN for use with this CE. The Select VPN window appears with the VPNs defined in the system. Only VPNs with the same service type (ERMS/EVP-LAN or EMS/EP-LAN) as the policy you chose appear. (See Figure 10-2.) Figure 10-2 Note Select a VPN The VC ID is mapped from the VPN ID. By default, ISC will “auto pick” this value. However, you can set this manually, if desired.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request with a CE Step 6 You can enter a description for the service request in the first Description field. The description will show up in this window and also in the Description column of the Service Requests window. The maximum length for this field is 256 characters. Step 7 Click Select CE in the CE column. The Select CPE Device window appears. (See Figure 10-4.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request with a CE Note Step 11 When you provision an ERMS (EVP-LAN) service (and when you choose a UNI for a particular device), ISC determines if there are other services using the same UNI. If so, a warning message is displayed. If you ignore the message and save the service request, all of the underlying service requests lying on the same UNI are synchronized with the modified shared attributes of the latest service request.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request without a CE Step 17 Continue to specify additional CEs, as in previous steps, if desired. Step 18 Click OK. Step 19 Click Save. The service request is created and saved into ISC. Creating a VPLS Service Request without a CE This section includes detailed steps for creating a VPLS service request without a CE present.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request without a CE Figure 10-8 Note Select a VPN The VC ID is mapped from the VPN ID. By default, ISC will “auto pick” this value. However, you can set this manually, if desired. This is done by editing the associated VPN configuration. The Edit VPN window has an Enable VPLS check box. When you check this check box, you can manually enter a VPN ID in a field provided.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request without a CE Figure 10-10 Select PE Device This window displays the list of currently defined PEs. a. The Show PEs with drop-down list shows PEs by customer name, by site, 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 page to be set to 5, 10, 20, 30, 40, or All.
Chapter 10 Managing a VPLS Service Request Creating a VPLS Service Request without a CE Note Step 11 When you provision an ERMS (EVP-LAN) service (and when you choose a UNI for a particular device), ISC determines if there are other services using the same UNI. If so, a warning message is displayed. If you ignore the message and save the service request, all of the underlying service requests lying on the same UNI are synchronized with the modified shared attributes of the latest service request.
Chapter 10 Managing a VPLS Service Request Modifying the VPLS Service Request Note For information on the Bridge Domain ID attribute, which shows up in some VPLS service request scenarios, see Modifying the VPLS Service Request, page 10-10. Step 16 Continue to specify additional PEs, as in previous steps, if desired. Step 17 Click Save. The VPLS service request is created and saved into ISC.
Chapter 10 Managing a VPLS Service Request Modifying the VPLS Service Request Figure 10-14 Step 4 Specify remaining items in the End-to-End-Wire Editor window, as necessary for your configuration: • Choose any of the blue highlighted values to edit the VPLS links. • Click Add Link to add a VPLS link. • Click Delete Link to delete a VPLS link.
Chapter 10 Managing a VPLS Service Request Modifying the VPLS Service Request Note Step 8 To add a template to a link, you must have already created the template. For detailed steps to create templates, see the Cisco IP Solution Center Infrastructure Reference, 6.0. For more information on how to use templates and data files in service requests, see Appendix B, “Working with Templates and Data Files.” Click Add. The Template Data File Chooser window appears.
Chapter 10 Managing a VPLS Service Request Using the Bridge Domain ID Attribute Using the Bridge Domain ID Attribute The Bridge Domain ID attribute appears in the Link Attributes window of some VPLS service request scenarios, as shown in Figure 10-15. Figure 10-15 Bridge Domain ID Attribute To use the Bridge Domain ID attribute, enter an ID number in the Bridge Domain ID text field to enable bridge domain functionality for the VPLS service request. Acceptable values are 1 to 4294967295.
Chapter 10 Managing a VPLS Service Request Saving the VPLS Service Request Saving the VPLS Service Request To save a VPLS service request, perform the following steps. Step 1 When you are finished with Link Attributes for all the Attachment Circuits, click Save to finish the VPLS service request creation. If the VPLS service request is successfully created, you will see the service request list window. (See Figure 10-16.
CH A P T E R 11 Deploying, Monitoring, and Auditing Service Requests This chapter describes how to deploy, monitor and audit L2VPN, VPLS or FlexUNI/EVC service requests, and how to access task logs. It contains the following sections: • Deploying Service Requests, page 11-1 • Monitoring Service Requests, page 11-10 • Auditing Service Requests, page 11-12 Deploying Service Requests To apply L2VPN, VPLS, or FlexUNI policies to network devices, you must deploy the service request.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests Figure 11-1 Step 5 Step 6 Change DCPL Parameter Choose one of the following: • prune to have ISC create the minimum VLAN list. This is the default. • abort to have ISC stop the L2VPN or VPLS service request provisioning with the error message: trunk allowed vlan list is absent on ERS UNI. • nochange to have ISC allow all VLANs. Click Set Property.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests Figure 11-2 Schedule Service Activation Step 4 Choose a schedule for the activation of the service. Step 5 After you schedule the service request, click Save. After you schedule the service request, you can monitor the service request that is being deployed. See Verifying Service Requests, page 11-3 and Monitoring Service Requests, page 11-10 for more information.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests • View service request details—From the Service Requests Details window, you can view the link endpoints and the configlets for this service request. For more information, See Viewing Service Request Details, page 11-7. • Task Logs—Access the task logs from the Monitoring tab to help you troubleshoot a failed service request or to view more details about a service request.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests Table 11-1 Summary of Cisco IP Solution Center Service Request States Service Request Type Description Broken The router is correctly configured but the service is unavailable (due to a broken cable or Layer 2 problem, for example).
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests Table 11-1 Summary of Cisco IP Solution Center Service Request States (continued) Service Request Type Description Pending A service request moves to Pending when the Provisioning Driver determines that the request looks consistent and was able to generate the required configuration updates for this request.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests Viewing Service Request Details The service request details include the link endpoints for the service request, the history, and the configlet generated during the service request deployment operation. Use the service request details to help you troubleshoot a problem or error with the service request or to check the commands in the configlet.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests Links The service request link details include the link endpoints, PE secured interface, VLAN ID, and whether a CE is present. To see this information, perform the following steps. Step 1 Click Links on the Service Request Details window. (See Figure 11-4.) The Service Request Links window appears. (See Figure 11-5.) Figure 11-5 Step 2 Service Request Links Choose a link and click Details.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Deploying Service Requests History To view history information about the service request, perform the following steps. Step 1 Click History on the Service Request Details window. (See Figure 11-4.) The Service Request State Change Report window appears. (See Figure 11-7.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Monitoring Service Requests Step 3 Click View Configlet. The Configlet for Device window appears. (See Figure 11-9.) Figure 11-9 L2VPN or VPLS Configlet Example The device configlet shows all commands downloaded to the device configuration during the service request deployment operation. Step 4 Click OK to exit.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Monitoring Service Requests Figure 11-10 Step 2 Tasks Window Click Find to refresh the window. The task that is executing will be the first in the list of tasks that being performed in ISC. Step 3 Choose the task you want to monitor and click Logs. The Task Logs window appears. (See Figure 11-11.) Figure 11-11 Step 4 Task Logs Choose the run-time task that you want to monitor and click View Log.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Auditing Service Requests Figure 11-12 Step 5 Task Logs Choose the log level from the drop-down list and click Filter. The log levels are All, Severe, Warning, Info, Config, Fine, Finer, and Finest. Step 6 Click Return to Logs. Step 7 Click Close in the Task Logs window. Auditing Service Requests Each time a service request is deployed in the Cisco IP Solution Center (ISC), a configuration audit occurs.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Auditing Service Requests Step 1 Choose Service Inventory > Inventory and Connection Manager > Service Requests. The Service Requests window appears. Step 2 Choose an service request for the configuration audit. Step 3 Click Details. The Service Request Details window appears. Step 4 Click Audit. Step 5 Click Config. The Service Request Audit window appears. Figure 11-13 shows an example of a successful configuration audit.
Chapter 11 Deploying, Monitoring, and Auditing Service Requests Auditing Service Requests Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 12 Using Autodiscovery for L2 Services All discovery steps are integrated in a discovery workflow, controlled from the ISC GUI. This is accessed in ISC through Service Inventory > Discovery. The following discovery features are supported: • File-based device discovery is supported. • Rules-based device role assignment is supported. • Discovery progress messages and logs are viewable in the GUI to keep track of various discovery stages.
Chapter 12 Using Autodiscovery for L2 Services Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
CH A P T E R 13 Generating L2 and VPLS Reports This chapter provides information on generating L2 and VPLS reports. It contains the following sections: • Overview, page 13-1 • Accessing L2 and VPLS Reports, page 13-1 • L2 and VPLS Reports, page 13-2 • Creating Custom L2 and VPLS Reports, page 13-11 Overview The ISC reporting GUI is used across multiple ISC modules, including L2 and VPLS.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports Figure 13-1 Reports Window Step 2 Click the L2 folder to display the available L2 and VPLS reports. Step 3 Click the icon of a report to bring up the window associated with that report. Details on each of the reports are provided in L2 and VPLS Reports, page 13-2.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports L2 End-to-End Wire Report An L2 end-to-end wire is a point-to-point connection containing two attachment circuits. The L2 EndtoEndWire report displays the services that are running on L2 end-to-end connections. You can use this report to view all the services and respective attachment circuit attributes for each connection. Click the L2 EndtoEndWire Report icon to bring up the window for this report. (See Figure 13-2.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports – INVALID – LOST – PENDING – REQUESTED – WAIT_DEPLOY • AC1-ID—First attachment circuit (AC1) identification number. • AC2-ID—Second attachment circuit (AC2) identification number. Output Values: • EndToEndWire ID—End-to-end wire identification number. • Customer Name—Name of the customer. • VPN—Name of the VPN. • VC ID—Virtual circuit identification number. • SR ID—Service request identification number.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports • AC1-CDP Drop Threshold—Cisco Discovery Protocol drop threshold (in packets/second) for the first attachment circuit (AC1). • AC1-VTP Drop Threshold—VLAN Trunk Protocol drop threshold (in packets/second) for the first attachment circuit (AC1). • AC1-UNI Recovery Interval—Recovery interval (in seconds) of the UNI port for the first attachment circuit (AC1). • AC1-UNI Speed—UNI port speed for the first attachment circuit (AC1).
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports • AC2-UNI PortSecurity—Status of UNI port security for the second attachment circuit (AC2). • AC2-UNI Duplex—Duplex status (none, full, half, or auto) of the UNI port for the second attachment circuit (AC2). • AC2-Maximum MAC Address—Maximum MAC addresses allowed on the UNI port for the second attachment circuit (AC2).
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports L2 VPN Report The L2 VPN Report provides a way to track a VLAN ID and/or VC ID back to the VPN and customer without having to iterate through every link and every VPN service. Given a VLAN ID or VC ID, the respective customer and VPN details are displayed in the report. Click the L2 VPN Report icon to bring up the window for this report. (See Figure 13-4.) Figure 13-4 L2 VPN Report Filter Values: • VLAN ID—VLAN identification number.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports VPLS Attachment Circuit Report The VPLS Attachment circuit report displays details of attachment circuits for a given customer VPN. Click the VPLS Attachment Circuit Report icon to bring up the window for this report. (See Figure 13-5.) Figure 13-5 VPLS Attachment Circuit Report Filter Values: • SR ID—Service request identification number. • SR Job ID—Service request job identification number. • SR State—Service request state.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports – VPLS_EWS_NO_CE • VLAN ID—VLAN identification number. • AccessDomain—Access domain name. Output Values: • VPLS Link ID—VPLS link identification number. • SR ID—Service request identification number • SR Job ID—Service request job identification number. • SR State—Service request state. Note The SR State output does not list service requests in the CLOSED state.
Chapter 13 Generating L2 and VPLS Reports L2 and VPLS Reports VPLS PE Service Report The VPLS PE Service report allows you to choose PEs and display their roles (for example, N-PE, U-PE or PE-AGG) and the VPLS services that are running on them. Click the VPLS PE Service Report icon to bring up the window for this report. (See Figure 13-6.) Figure 13-6 VPLS PE Service Report Filter Values: • PE Role—PE device role (N-PE, U-PE, or PE-AGG). • PE Name—PE device name.
Chapter 13 Generating L2 and VPLS Reports Creating Custom L2 and VPLS Reports VPLS VPN Report The VPLS VPN report provides a way to track a VLAN ID and/or VFI Name back to the VPN and customer without having to iterate through every link and every VPN service. Given a VLAN ID or VFI name, the respective customer and VPN details are displayed in the report. Click the VPLS VPN Report icon to bring up the window for this report. (See Figure 13-7.
Chapter 13 Generating L2 and VPLS Reports Creating Custom L2 and VPLS Reports Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
A P P E N D I X A Sample Configlets This appendix provides sample configlets for L2VPN and Metro Ethernet service provisioning in ISC.
Appendix A Sample Configlets Overview • FlexUNI/EVC (Pseudowire Core Connectivity, UNI, and Pseudowire Tunneling), page A-33 • FlexUNI/EVC (VPLS Core Connectivity, UNI Port Security), page A-34 • FlexUNI/EVC (VPLS Core Connectivity, no UNI Port Security), page A-35 • FlexUNI/EVC (Local Connect Core Connectivity, UNI Port Security), page A-36 • FlexUNI/EVC (Local Connect Core Connectivity, UNI, no Port Security, Bridge Domain), page A-38 • FlexUNI/EVC (Pseudowire Core Connectivity, Bridge Domai
Appendix A Sample Configlets Overview • Service • Feature • Devices configuration (network role, hardware platform, relationship of the devices and other relevant information) • Sample configlets for each device in the configuration • Comments Note The configlets generated by ISC are only the delta between what needs to be provisioned and what currently exists on the device. This means that if a relevant CLI is already on the device, it does not show up in the associated configlet.
Appendix A Sample Configlets ERS (EVPL) (Point-to-Point) ERS (EVPL) (Point-to-Point) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL) (point-to-point). • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BXL. Interface(s): FA8/17. – The U-PE is a Cisco 3750ME with 12.2(25)EY1, no port security. Interface(s): FA1/0/4 – FA1/0/23. – L2VPN point-to-point.
Appendix A Sample Configlets ERS (EVPL) (Point-to-Point, UNI Port Security) ERS (EVPL) (Point-to-Point, UNI Port Security) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL) (point-to-point) with UNI port security. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, OSM. Interface(s): FA2/18. – The U-PE is a Cisco 3550 with IOS 12.2(25)SEC2. Port security is enabled. Interface(s): FA3/31– FA3/23. – L2VPN point-to-point.
Appendix A Sample Configlets ERS (EVPL) (Point-to-Point, UNI Port Security) • Various UNI port security commands are provisioned. • A user-defined PACL entry is added to the default PACL. Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
Appendix A Sample Configlets ERS (EVPL) (1:1 VLAN Translation) ERS (EVPL) (1:1 VLAN Translation) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL) with 1:1 VLAN translation. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BXL Interface(s): FA8/34. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY1. VLAN translation on the NNI port (uplink). Interface(s): FA1/0/8 – GI1/1/1. – L2VPN point-to-point.
Appendix A Sample Configlets ERS (EVPL) (2:1 VLAN Translation) ERS (EVPL) (2:1 VLAN Translation) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL) with VLAN 2:1 translation.Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BXL Interface(s): FA8/34. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY1. VLAN translation on the NNI port (uplink). Interface(s): FA1/0/5 – GI1/1/1. – L2VPN point-to-point.
Appendix A Sample Configlets ERS (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) ERS (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL). • Device configuration: – The N-PE is a CRS-1 with IOS XR 3.6.1 or later. – UNI on N-PE. – UNI on U-PE.
Appendix A Sample Configlets ERS (EVPL) (NBI Enhancements for L2VPN, IOS Device) ERS (EVPL) (NBI Enhancements for L2VPN, IOS Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL). • Device configuration: – The N-PE is a 12.2(18)SXF with IOS. – The U-PE is a 12.2(25)EY4with IOS. – UNI on N-PE. – UNI on U-PE.
Appendix A Sample Configlets ERS (EVPL) or EWS (EPL) (IOS XR Device) ERS (EVPL) or EWS (EPL) (IOS XR Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL) or EWS (EPL). • Device configuration(s): – The N-PE is a CRS-1 with IOS XR 3.4.2. – UNI on N-PE. ERS (EVPL) only. – U-PE. EWS (EPL) or ERS (EVPL). Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
Appendix A Sample Configlets ERS (EVPL) or EWS (EPL) (IOS XR Device) Configlets N-PE GigabitEthernet0/0/0/1.
Appendix A Sample Configlets ERS (EVPL) or EWS (EPL) (IOS XR Device) • With respect to the XML schemas, different versions of IOS XR generate different XML configlets. However the configurations will be almost identical, except for changes in the XML schema. • There are different cases to consider. For example, when a service request is decommissioned or modified, the XML configuration will slightly differ. Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
Appendix A Sample Configlets ERS (EVPL) and EWS (EPL) (Local Connect on E-Line) ERS (EVPL) and EWS (EPL) (Local Connect on E-Line) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL) and EWS (EPL). • Device configuration: – The N-PE is a CRS-1 with IOS XR 3.6 or later. – The U-PE is a 12.2(18)SXF with IOS. Configlets U-PE N-PE interface GigabitEthernet0/0/0/2.559 dot1q vlan 559 l2transport ! interface GigabitEthernet0/0/0/4.
Appendix A Sample Configlets ERS (EVPL), EWS (EPL), ATM, or Frame Relay (Additional Template Variables for L2VPN, IOS and IOS XR Device) ERS (EVPL), EWS (EPL), ATM, or Frame Relay (Additional Template Variables for L2VPN, IOS and IOS XR Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ERS (EVPL), EWS (EPL), ATM and Frame Relay. • Device configuration: – The N-PE is a 12.2(18)SXF with IOS for ERS (EVPL), EWS (EPL), Frame Relay service. – The N-PE is a CRS-1 with IOS XR 3.
Appendix A Sample Configlets EWS (EPL) (Point-to-Point) EWS (EPL) (Point-to-Point) Configuration • Service: L2VPN/Metro Ethernet. • Feature: EWS (EPL) (point-to-point). • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BXL. Interface(s): FA8/17. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY1. No port security, no tunneling. Interface(s): FA1/0/20 – FA1/0/23. – L2VPN point-to-point. – Q-in-Q UNI.
Appendix A Sample Configlets EWS (EPL) (Point-to-Point, UNI Port Security, BPDU Tunneling) EWS (EPL) (Point-to-Point, UNI Port Security, BPDU Tunneling) Configuration • Service: L2VPN/Metro Ethernet. • Feature: EWS (EPL) (point-to-point) with Port security, BPDU tunneling. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BXL. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY1. No port security, with tunneling. – L2VPN point-to-point. – Q-in-Q UNI.
Appendix A Sample Configlets EWS (EPL) (Point-to-Point, UNI Port Security, BPDU Tunneling) Configlets U-PE N-PE system mtu 1522 ! vlan 775 exit ! system mtu 1522 ! vlan 775 exit ! interface FastEthernet1/0/19 no cdp enable no keepalive switchport switchport access vlan 775 switchport mode dot1q-tunnel switchport nonegotiate switchport port-security maximum 34 switchport port-security aging time 32 switchport port-security violation shutdown switchport port-security l2protocol-tunnel cdp l2protocol-tun
Appendix A Sample Configlets EWS (EPL) (Hybrid) EWS (EPL) (Hybrid) Configuration • Service: L2VPN/Metro Ethernet. • Feature: EWS (EPL) hybrid. One side is EWS (EPL) UNI; the other side is ERS (EVPL) NNI. • Device configuration: – The N-PE is a Cisco 7600 with 12.2(18)SXF, Sup720-3BXL. Interface(s): FA8/17. – The U-PE is a Cisco 3750ME with 12.2(25)EY1. No port security, with tunneling. Interface(s): FA1/0/20 – FA1/0/23. – L2VPN point-to-point. – Q-in-Q UNI.
Appendix A Sample Configlets EWS (EPL) (Hybrid) Configlets (EWS) U-PE N-PE system mtu 1522 ! vlan 775 exit ! system mtu 1522 ! vlan 775 exit ! interface FastEthernet1/0/19 no cdp enable no keepalive switchport switchport access vlan 775 switchport mode dot1q-tunnel switchport nonegotiate switchport port-security maximum 34 switchport port-security aging time 32 switchport port-security violation shutdown switchport port-security l2protocol-tunnel cdp l2protocol-tunnel stp l2protocol-tunnel vtp l2proto
Appendix A Sample Configlets EWS (EPL) (Hybrid) Configlets (ERS) U-PE N-PE system mtu 1522 vlan 775 exit ! interface FastEthernet8/17 switchport trunk allowed vlan 1,451,653,659,766-768,772,773-775,878 ! interface Vlan775 no ip address description L2VPN EWS xconnect 99.99.8.
Appendix A Sample Configlets EWS (EPL) (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) EWS (EPL) (Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: EWS (EPL). • Device configuration: – The N-PE is a CRS-1 with IOS XR 3.6.1 or later. – UNI on U-PE.
Appendix A Sample Configlets EWS (EPL) (NBI Enhancements for L2VPN, IOS Device) EWS (EPL) (NBI Enhancements for L2VPN, IOS Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: EWS (EPL). • Device configuration: – The N-PE is a 12.2(18)SXF with IOS. – The U-PE is a 12.2(25)EY4with IOS. – UNI on N-PE. – UNI on U-PE.
Appendix A Sample Configlets ATM over MPLS (VC Mode) ATM over MPLS (VC Mode) Configuration • Service: L2VPN. • Feature: ATM over MPLS (ATMoMPLS, a type of AToM) in VC mode. • Device configuration: – The N-PE is a Cisco 7200 with IOS 12.0(28)S. – No CE. – No U-PE. – L2VPN point-to-point (ATMoMPLS). – C7200 (ATM2/0). Configlets Comments U-PE N-PE (None) interface ATM2/0.34234 point-to-point pvc 213/423 l2transport encapsulation aal5 xconnect 99.99.4.
Appendix A Sample Configlets ATM over MPLS (VP Mode) ATM over MPLS (VP Mode) Configuration • Service: L2VPN. • Feature: ATM over MPLS (ATMoMPLS, a type of AToM) in VP mode. • Device configuration: – The N-PE is a Cisco 7200 with IOS 12.0(28)S. Interface(s): ATM2/0. – No CE. – No U-PE. – L2VPN point-to-point (ATMoMPLS).
Appendix A Sample Configlets ATM (Port Mode, Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) ATM (Port Mode, Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) Configuration • Service: L2VPN/Metro Ethernet. • Feature: ATM. • Device configuration: – The N-PE is a CRS-1 with IOS XR 3.7 or later for ATM service (port mode only). – UNI on N-PE.
Appendix A Sample Configlets Frame Relay over MPLS Frame Relay over MPLS Configuration • Service: L2VPN. • Feature: Frame Relay over MPLS (FRoMPLS, a type of AToM). • Device configuration: – The N-PE is a Cisco 7200 with IOS 12.0(28)S. Interface(s): ATM2/0. – No CE. – No U-PE. – L2VPN point-to-point (ATMoMPLS). Configlets Comments U-PE N-PE (None) interface Serial1/1 exit ! connect C1_89001 Serial1/1 135 l2transport xconnect 99.99.4.
Appendix A Sample Configlets Frame Relay (DLCI Mode) Frame Relay (DLCI Mode) Configuration • Service: L2VPN over a L2TPv3 core. • Feature: FR in DLCI mode. • Device configuration: – The N-PE is a Cisco 7200 with IOS 12.0(28)S. Interface(s): ATM2/0. – No CE. – No U-PE. – L2VPN point-to-point (ATMoMPLS).
Appendix A Sample Configlets VPLS (Multipoint, ERMS/EVP-LAN) VPLS (Multipoint, ERMS/EVP-LAN) Configuration • Service: L2VPN/Metro Ethernet. • Feature: VPLS (multipoint) ERMS (EVP-LAN). • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BX.L Interface(s): FA2/18. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY1. No port security, no tunneling. Interface(s): FA1/0/21 – FA1/0/23. – VPLS Multipoint VPN with VLAN 767.
Appendix A Sample Configlets VPLS (Multipoint, EMS/EP-LAN), BPDU Tunneling) VPLS (Multipoint, EMS/EP-LAN), BPDU Tunneling) Configuration • Service: L2VPN/Metro Ethernet. • Feature: VPLS (multipoint) EMS (EP-LAN) with BPDU tunneling. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(18)SXF, Sup720-3BXL. Interface(s): FA2/18. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY1. No port security, no tunneling. Interface(s): FA1/0/12 – FA1/0/23. – VPLS Multipoint VPN, with VLAN 767.
Appendix A Sample Configlets FlexUNI/EVC (Pseudowire Core Connectivity, UNI Port Security) FlexUNI/EVC (Pseudowire Core Connectivity, UNI Port Security) Configuration • Service: FlexUNI (EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with pseudowire core connectivity, with UNI port security. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33)SRB3. Interface(s): GI2/0/0. – The U-PE is a Cisco 3750ME with IOS 12.2(25)EY2. Port security is enabled. Interface(s): FA1/14– FA3/23.
Appendix A Sample Configlets FlexUNI/EVC (Pseudowire Core Connectivity, UNI, without Port Security, with Bridge Domain) FlexUNI/EVC (Pseudowire Core Connectivity, UNI, without Port Security, with Bridge Domain) Configuration • Service: FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with pseudowire core connectivity, with UNI, without port security, and with bridge domain. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33)SRB3. Interface(s): GI2/0/0.
Appendix A Sample Configlets FlexUNI/EVC (Pseudowire Core Connectivity, UNI, and Pseudowire Tunneling) FlexUNI/EVC (Pseudowire Core Connectivity, UNI, and Pseudowire Tunneling) Configuration • Service: FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with pseudowire core connectivity, with UNI, with pseudowire tunneling. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GI4/0/0 <–> GI2/0/0.
Appendix A Sample Configlets FlexUNI/EVC (VPLS Core Connectivity, UNI Port Security) FlexUNI/EVC (VPLS Core Connectivity, UNI Port Security) Configuration • Service: FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with VPLS core connectivity, with UNI port security. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GI4/0/1. – The U-PE is a Cisco 3750ME with IOS 12.2(25) EY2. Port security is enabled. Interface(s): FA1/14– FA3/23.
Appendix A Sample Configlets FlexUNI/EVC (VPLS Core Connectivity, no UNI Port Security) FlexUNI/EVC (VPLS Core Connectivity, no UNI Port Security) Configuration • Service: FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with VPLS core connectivity, without UNI port security. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GI4/0/1. – The U-PE is a Cisco 3750ME with IOS 12.2(25) EY2. Interface(s): FA1/14– FA3/23.
Appendix A Sample Configlets FlexUNI/EVC (Local Connect Core Connectivity, UNI Port Security) FlexUNI/EVC (Local Connect Core Connectivity, UNI Port Security) Configuration • Service: FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with local connect core connectivity, with UNI port security. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s):GI2/0/0. – The U-PE is a Cisco 3750ME with IOS 12.2(25) EY2. Port security is enabled.
Appendix A Sample Configlets FlexUNI/EVC (Local Connect Core Connectivity, UNI Port Security) • The rewrite operation translates two tags to a single tag. • Two service instances are connected through the connect command. Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
Appendix A Sample Configlets FlexUNI/EVC (Local Connect Core Connectivity, UNI, no Port Security, Bridge Domain) FlexUNI/EVC (Local Connect Core Connectivity, UNI, no Port Security, Bridge Domain) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with local connect core connectivity, with UNI, without port security, and with bridge domain. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s):GI2/0/0. – The U-PE is a Cisco 3750ME with IOS 12.
Appendix A Sample Configlets FlexUNI/EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) FlexUNI/EVC (Pseudowire Core Connectivity, Bridge Domain, Pseudowire on SVI) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with pseudowire core connectivity, with bridge domain, and with Pseudowire on SVI enabled on the N-PE. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet7/0/0.
Appendix A Sample Configlets FlexUNI/EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI) FlexUNI/EVC (Pseudowire Core Connectivity, no Bridge Domain, no Pseudowire on SVI) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with pseudowire core connectivity, bridge domain disables, and with Pseudowire on SVI disabled on the N-PE. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet7/0/0.
Appendix A Sample Configlets FlexUNI/EVC (AutoPick Service Instance Name) FlexUNI/EVC (AutoPick Service Instance Name) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with AutoPick Service Instance Name enabled and the Service Instance Name input field left blank. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet7/0/2. – The U-PE is a Cisco 3750ME with IOS 12.2(25) EY2. Interface(s): FastEthernet1/0/14.
Appendix A Sample Configlets FlexUNI/EVC (No AutoPick Service Instance Name, No Service Instance Name) FlexUNI/EVC (No AutoPick Service Instance Name, No Service Instance Name) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with AutoPick Service Instance Name not enabled and the Service Instance Name input field left blank. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet7/0/2. – The U-PE is a Cisco 3750ME with IOS 12.
Appendix A Sample Configlets FlexUNI/EVC (User-Provided Service Instance Name, Pseudowire Core Connectivity) FlexUNI/EVC (User-Provided Service Instance Name, Pseudowire Core Connectivity) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with pseudowire core connectivity and user-provided service instance name. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet7/0/0. – The U-PE is a Cisco 3750ME with IOS 12.2(25) EY2.
Appendix A Sample Configlets FlexUNI/EVC (User-Provided Service Instance Name, Local Core Connectivity) FlexUNI/EVC (User-Provided Service Instance Name, Local Core Connectivity) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with local core connectivity and a user-provided service instance name. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet1/0/6, GigabitEthernet1/0/7. – The U-PE is a Cisco 3750ME with IOS 12.
Appendix A Sample Configlets FlexUNI/EVC (User-Provided Service Instance Name, VPLS Core Connectivity) FlexUNI/EVC (User-Provided Service Instance Name, VPLS Core Connectivity) Configuration • FlexUNI(EVC)/Metro Ethernet. • Feature: FlexUNI/EVC with VPLS core connectivity and user-provided service instance name. • Device configuration: – The N-PE is a Cisco 7600 with IOS 12.2(33) SRB3. Interface(s): GigabitEthernet7/0/0. – The U-PE is a Cisco 3750ME with IOS 12.2(25) EY2.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Point-to-Point Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Point-to-Point Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity with an end-to-end circuit with multiple links.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity with a multipoint circuit.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with local core connectivity with a point-to-point circuit. The circuit terminates on different ATM interfaces on the same local N-PE.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Multipoint Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Multipoint Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with local core connectivity for multiple links that terminate on the same local N-PE. Link #1 terminates on an ATM interface, and link #2 terminates on an Ethernet interface.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Multipoint Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Multipoint Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with local core connectivity. Multiple links terminate on the same local N-PE.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with local core connectivity. A point-to-point circuit terminates on different ATM interfaces on same local N-PE. • Device configuration: – The N-PE 1 is a Cisco 7600 with IOS 12.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity for end-to-end circuit with multiple links. One link terminates on ATM interface on N-PE 1, and other link terminates on an Ethernet interface on N-PE 2.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity with an end-to-end circuit with multiple links.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) FlexUNI/EVC (ATM-Ethernet Interworking, Local Core Connectivity, Point-to-Point Circuit) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with local core connectivity for point-to-point circuit. The circuit terminates on the same, local N-PE 1.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, with Bridge Domain) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, with Bridge Domain) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity for end-to-end circuit with multiple links with bridge domain enabled.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, with Bridge Domain) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, with Bridge Domain) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity for end-to-end circuit with multiple links. Bridge domain is enabled.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, no Bridge Domain) FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, no Bridge Domain) Configuration • FlexUNI(EVC)/ATM-Ethernet Interworking. • Feature: FlexUNI/EVC for ATM-Ethernet interworking with pseudowire core connectivity for end-to-end circuit with multiple links. Bridge domain is disabled.
Appendix A Sample Configlets FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, End-to-End Circuit, no Bridge Domain) Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
A P P E N D I X B Working with Templates and Data Files This appendix describes how to use templates and data files with ISC policies and service requests.
Appendix B Working with Templates and Data Files Overview Template Attributes The ISC template mechanism allows you to differentiate templates by specifying (optional) attributes on a template, including: • Device type • Line card type • Port type • Software version (IOS or IOS XR) These attributes are set through a drop-down list when setting up the template in Template Manager.
Appendix B Working with Templates and Data Files Overview Template Support for IOS and IOS XR The template mechanism is supported for both IOS and IOS XR devices. For IOS XR devices, the configlet generated from templates/data files contains CLI commands and not XML statements. For IOS XR devices, template support is provided as CLI commands. For IOS devices, the operator can download a template configlet using the device console. Note Note the following known issue in the case of IOS XR devices.
Appendix B Working with Templates and Data Files Using Templates with ISC Policies • Create a super template and attach subtemplates to it. These basic Template Manager functions are documented in the Cisco IP Solution Center Infrastructure Reference, 6.0. See that guide for more information on these tasks. Policy-Level Template Functions • Create a policy and enable template support for the policy. • Associate templates and (optionally) data files to the policy, if desired.
Appendix B Working with Templates and Data Files Using Templates with ISC Policies request creation, templates are only available if the device type matches the role type specified for the template within the policy or role type along with (or without) the presence of UNI interface in the policy. Associating Templates and Data Files to a Policy This section describes how to associate templates and data files to an ISC policy. These features also apply in the case of editing a policy.
Appendix B Working with Templates and Data Files Using Templates with ISC Policies Figure B-2 Step 2 Template Association Window with Template Enable Checked Click the Add button to add a row in which to specify associated templates/data files. A new row appears in the GUI, providing fields to set the role type, specify templates/data files, and specify if the template/data file is editable within service requests based on the policy.
Appendix B Working with Templates and Data Files Using Templates with ISC Policies Step 5 Note Click the Add button to select a template/data file to associate with the policy. If the device role is specified as U-PE or PE-AGG, templates can be selectively added based on whether the device has a UNI interface. For details on this feature, see Selectively Determining Templates for U-PE and PE-AGG Device Roles, page B-9.
Appendix B Working with Templates and Data Files Using Templates with ISC Policies Figure B-5 Step 7 Note Template Datafile Chooser Window with Template and Data File Listed Check the check box to the left of a data file name and click the Accept button. You can select only the template or both template and data file at this stage, depending on your needs, and whether or not a data file exists for the template.
Appendix B Working with Templates and Data Files Using Templates with ISC Policies The Template Association window appears with the template(s)/data file(s) listed as active link(s). If you have added more than one template/data file, they appear in a comma-separated list of links. You can click on any link to return to the Add/Remove Templates window, in order to edit/update the template/data file information.
Appendix B Working with Templates and Data Files Using Templates with Service Requests • This features is not applicable for device roles other than U-PE and PE-AGG. In Figure B-7 the N-PE role only displays a single Add link in the Template/Data File column. • For backward compatibility, when editing or viewing old and existing policies, for U-PE and PE-AGG devices, associated templates/data files will display under the All other Devices option.
Appendix B Working with Templates and Data Files Using Templates with Service Requests Associating Templates to a Service Request The template mechanism in ISC provides a way to add additional configuration information to a device configuration generated by a service request. To use the template mechanism, the policy on which the service request is based must have been set to enable templates. Optionally, templates and data files to be used by the service request can be specified in the policy.
Appendix B Working with Templates and Data Files Using Templates with Service Requests Table B-1 Default SubTemplate Matching Criteria Matching Order Role Type Device Type Line Card Port Type Software Version 1 Exact Match Exact Match Exact Match Exact Match Exact Match 2 Exact Match Exact Match Exact Match Exact Match Previous Highest 3 Exact Match Exact Match Exact Match No Values Exact Match 4 Exact Match Exact Match Exact Match No Values Previous Highest 5 Exact Match
Appendix B Working with Templates and Data Files Using Templates with Service Requests The service request workflow supports dynamic creation of data files as follows: • If a template is marked as non-editable in the policy on which the service request is based, the operator cannot edit it during service request creation. However, the name of template and data files are still visible, even though they cannot be modified.
Appendix B Working with Templates and Data Files Using Templates with Service Requests • If you change the template associated with a service request, the negate template automatically changes to the negate template of the newly selected template. In this case, ISC executes the negate template of the previously associated template, as well as the newly associated template.
Appendix B Working with Templates and Data Files Using Templates with Service Requests Note There is no choice of options to selectively determine templates for U-PE and PE-AGG devices during the service request workflow. Templates are automatically copied from the policy, based on the presence of a UNI interface on the devices functioning in U-PE and PE-AGG roles. See the section Selectively Determining Templates for U-PE and PE-AGG Device Roles, page B-9, for more information on this feature.
Appendix B Working with Templates and Data Files Using Templates with Service Requests Figure B-8 Sample Templates Association Window with Templates/Data Files Selected If multiple templates/data files are selected for a device, they appear as a comma-separated list, as shown in the figure. Step 8 Click the Finish button to create the service request with the template/data file selections you chose.
Appendix B Working with Templates and Data Files Using Templates with Service Requests The template is listed in the right side of the GUI, along with any data files that are associated with it. This example uses the AccessList1 template in the Examples directory, as shown in Figure B-9. Figure B-9 Step 4 Templates Datafile Chooser Window with No Data File Listed Click the Create Data File button to create a data file dynamically in the workflow.
Appendix B Working with Templates and Data Files Using Templates with Service Requests When the data file is saved, the Template Datafile Chooser window appears with the newly created data file listed. Decommissioning Service Requests with Added Templates This section describes how to decommission ISC service requests that have added templates.
Appendix B Working with Templates and Data Files Using Templates with Service Requests Figure B-11 Note Service Requests Window with Data Files Column You can use the Show Services with field to search for service requests that have a specific data or template file. Choose Data File Name or Template Name from the drop-down list and enter a search string in the matching field. The matching field is not case-sensitive and supports wildcards (*).
Appendix B Working with Templates and Data Files Using Templates with Service Requests Figure B-12 Service Request Details Window The Associated data file(s) row displays a link for each data file associated with the service request, as shown in the figure. Step 3 Click a data file link to display the configlet for the template. Step 4 After viewing the configlet, click OK to close the configlet display window. Step 5 Click OK to close the Service Request Details window.
A P P E N D I X C Setting Up VLAN Translation This appendix describes how to set up VLAN translation for L2VPN ERS (EVPL) services. It contains the following sections: Note • VLAN Translation Overview, page C-1 • Setting Up VLAN Translation, page C-1 • Platform-Specific Usage Notes, page C-6 For helpful information to be aware of before you create policies and services using VLAN translation, review Platform-Specific Usage Notes, page C-6.
Appendix C Setting Up VLAN Translation Setting Up VLAN Translation • Modifying a Service Request, page C-5 • Deleting a Service Request, page C-5 Creating a Policy VLAN translation is specified during policy creation for L2VPN for ERS (EVPL) (with and without a CE). The L2VPN (Point to Point) Editor window contains a new option called VLAN Translation. (See Figure C-1.
Appendix C Setting Up VLAN Translation Setting Up VLAN Translation Creating a Service Request When you create a service request based on an L2VPN ERS (EVPL) policy, the VLAN options can be changed if they were set to be editable in the policy. You can overwrite the policy information for the VLAN translation type and the place where translation occurs.
Appendix C Setting Up VLAN Translation Setting Up VLAN Translation In the empty field, you must enter which CE VLAN is to be translated from. The VLAN number must be a number from 1 to 4096. The PE VLAN that the CE VLAN is to be translated to can be “auto picked” or manually entered. Check the VLAN ID AutoPick check box above (on the Link Attributes window) to have PE VLAN automatically assigned. (See Figure C-4.
Appendix C Setting Up VLAN Translation Setting Up VLAN Translation • “B”—The PE VLAN that is the outer VLAN of the Q-in-Q port. You specify this in the “Outer VLAN” field. You can choose this VLAN manually by entering a value, or you can choose the AutoPick check box to have one automatically assigned. • “C”—The PE VLAN that the “A” and “B” VLANs are translated to. You specify this in the “VLAN and Other Information” section above (on the Link Attributes window). (See Figure C-4 and Figure C-5.
Appendix C Setting Up VLAN Translation Platform-Specific Usage Notes • The CE VLAN becomes available to be translated again. • The “translated to” PE VLAN is released. • If the link being deleted is the last “CE-PE” pair on this UNI port, and there is no EWS (EPL) service on this port, then this port is set to new. In addition, the outer VLAN is released. Platform-Specific Usage Notes VLAN translation is available on 7600 and 3750 ME platforms.
A P P E N D I X D Terminating an Access Ring on Two N-PEs This appendix describes how to terminate an access ring on two N-PEs for redundancy in case an access link goes down.
Appendix D Terminating an Access Ring on Two N-PEs Overview Figure D-1 N-PE Redundancy, Starting at the U-PE N-PE-1 MPLS Core 204824 U-PE Figure D-2 N-PE and PE-AGG Redundancy, Starting at the U-PE PE-AGG-1 N-PE-1 MPLS Core 204825 U-PE PE-AGG-2 N-PE-2 The first topology (N-PE redundancy starting at the U-PE, as shown in Figure D-1) provides the model of fault recovery for the N-PE device. As shown in the diagram, there are two different outgoing interfaces starting from the U-PE device.
Appendix D Terminating an Access Ring on Two N-PEs Setting Up an NPC Access Ring with Two N-PEs • Note For the Cisco ASR 9000 platform, IOS XR version 3.7.3 and 3.9.0 are supported. Check the on-line version of Release Notes for Cisco IP Solution Center, 6.0, for the most current information on device and platform support, in case updates have occurred since the publication of this guide. The implementation of this feature is covered in more detail in the following sections.
Appendix D Terminating an Access Ring on Two N-PEs Using N-PE Redundancy in FlexUNI/EVC Service Requests Figure D-4 FlexUNI/EVC Service Request Editor Page, with N-PE Redundancy Option Usage notes: • The service is configured on both N-PEs of the access ring. • Though there are two different N-PEs, only one access link is consumed. • You can modify the configuration redundant N-PEs before or after deploying the service request.
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets the N-PE of the single-homed ring, and the secondary PW will connect the secondary N-PE of the dual-homed ring with the N-PE of the single-homed ring. ISC will issue a warning message if you try to save the service request without enabling the Pseudowire Redundancy option.
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets PE1 vlan ! interface switchport switchport trunk encapsulation dot1q switchport mode trunk switchport trunk allowed vlan add ! interface vlan xconnect encapsulation mpls backup peer PE2 vlan ! interface switchport switchport trunk encapsulation dot1q switchport mode trunk switchport
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets Figure D-6 Pseudowire Connectivity, Dual-Homed N-PEs on Both Sides of the Network, with No Pseudowire Redundancy R1 PE1 PE3 R4 R3 PE2 PE4 R5 R2 204865 Primary Edge Secondary Edge Blocked Segment Data Pseudowire Control Pseudowire Primary VC ID Backup VC ID Sample configlets for the devices are provided below.
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets PE3 vlan ! interface switchport switchport trunk encapsulation dot1q switchport mode trunk switchport trunk allowed vlan add ! interface vlan xconnect encapsulation mpls PE4 vlan ! interface switchport switchport trunk encapsulation dot1q switchport mode trunk switchport trunk allowed vlan add ! interf
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets Sample configlets for the devices are provided below.
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets Figure D-8 VPLS Connectivity, Dual-Homed N-PEs on Both Sides of the Network R1 PE1 PE3 R4 R3 PE2 PE4 R5 Primary Edge Secondary Edge Blocked Segment Data Pseudowire Control Pseudowire 204867 R2 Sample configlets for the devices are provided below.
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets PE3 vlan ! l2 vfi manual vpn id neighbor encapsulation mpls neighbor encapsulation mpls neighbor encapsulation mpls ! interface vlan xconnect vfi ! interface switchport trunk allowed vlan add PE4 vlan ! l2 vfi manual vpn id neighbor encapsulation mpls neighbor encapsulation mpls
Appendix D Terminating an Access Ring on Two N-PEs Additional Network Configurations and Sample Configlets Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.
A P P E N D I X E ISC Layer 2 VPN Concepts This appendix provides an overview of ISC Layer 2 VPN concepts. It contains the following sections. • Layer 2 Terminology Conventions, page E-1 • L2VPN Service Provisioning, page E-5 • VPLS Service Provisioning, page E-10 Layer 2 Terminology Conventions Layer 2 service provisioning for the IP Solution Center (ISC) consists of the Layer 2 Virtual Private Network (L2VPN) Service and the Virtual Private LAN Service (VPLS).
Appendix E ISC Layer 2 VPN Concepts Layer 2 Terminology Conventions Table E-1 Ethernet Service Definitions Service Type Port-Based VLAN-Based E-Line Ethernet Private Line (EPL) Ethernet Virtual Private Line (EVPL) E-LAN Ethernet Private LAN (EP-LAN) Ethernet Virtual Private LAN (EVP-LAN) In addition to E-Line and E-LAN services, two additional service types are available for Layer 2: • Frame Relay over MPLS (FRoMLS) • ATM over MPLS (ATMoMPLS) These service types are not covered in the curr
Appendix E ISC Layer 2 VPN Concepts Layer 2 Terminology Conventions Mapping MEF Terminologies to Network Technologies The MEF terminology only describes the outside characteristics of a service, that is, what the service looks like from the perspective of a customer looking in towards the user-to-network-interface (UNI) device. It does not describe how the service is implemented. For details about how these service are implemented, see the following URL: http://www.cisco.
Appendix E ISC Layer 2 VPN Concepts Layer 2 Terminology Conventions ISC Terminology and Supported Network Types This section discusses the ISC terminology for Layer 2 services and supported network types.
Appendix E ISC Layer 2 VPN Concepts L2VPN Service Provisioning L2VPN Service Provisioning This section provides and overview of ISC provisioning for L2VPN services that provide Layer 2 point-to-point connectivity over an MPLS core. Cisco’s Any Transport over MPLS (AToM) enables supports these services. These implementations, in turn, support service types, as follows: – Ethernet Wire Service (EWS). The MEF term for this service is EPL. – Ethernet Relay Service (ERS). The MEF term for this service is EVPL.
Appendix E ISC Layer 2 VPN Concepts L2VPN Service Provisioning • Single PE scenario—The customer is directly connected to an Ethernet port on the N-PE in Figure E-2. Figure E-2 Single PE scenario U_PE PE_AGG N_PE1 10.1.1.1 N_PE2 10.2.2.2 MPLS Core U_PE Single PE scenario Site B CE • Figure E-3 138356 Site A CE Distributed PE scenario—The end customer is connected through an Access Domain to the N-PE in Figure E-3. That is, there is a Layer 2 switching environment in the middle of CE and N-PE.
Appendix E ISC Layer 2 VPN Concepts L2VPN Service Provisioning For the N-PE that is serving Site A, a VLAN interface (Layer 3 interface) is created to terminate all L2 traffic for the customer, and an EoMPLS tunnel is configured on this interface. Note This configuration is based on the Cisco 7600 Optical Services Router. Other routers, such as the Cisco 7200, have different configurations. The VC ID that defines the EoMPLS tunnel is 200. (See Figure E-4.
Appendix E ISC Layer 2 VPN Concepts L2VPN Service Provisioning This VLAN-VC ID mapping lets the service provider reuse VLAN IDs in Access Domains. (See Figure E-6.) VLAN-VC ID Mapping U_PE PE_AGG U_PE VLAN 100 N_PE1 10.1.1.1 VC ID 200 Mapping VLAN ID to VC ID MPLS Core N_PE2 10.2.2.2 VC ID 200 Mapping VLAN 200 VLAN ID to VC ID Site A CE Site B CE 138359 Figure E-6 The VLAN IDs allocated and used at each access domain do not have to be the same.
Appendix E ISC Layer 2 VPN Concepts L2VPN Service Provisioning Figure E-7 Configuring AAL5 and Cell Relay over MPLS MPLS Core PE PE ATM virtual circuits CE CE CE CE 138360 ATM ATM Frame Relay over MPLS (FRoMPLS) With Cisco AToM for Frame Relay, customer Frame Relay traffic can be encapsulated in MPLS packets and forwarded to destinations required by the customer. Cisco AToM allows service providers to quickly add new sites with less effort than typical Frame Relay provisioning.
Appendix E ISC Layer 2 VPN Concepts VPLS Service Provisioning Figure E-8 Frame Relay over MPLS MPLS Core PE PE Frame Relay DLCI Frame Relay CE CE CE 138361 CE Frame Relay VPLS Service Provisioning VPLS services are multipoint. They provide multipoint connectivity over an MPLS or an Ethernet core. These implementations, in turn, support service types, as follows: • VPLS over MPLS core: – Ethernet Wire Service (EWS). This is also sometimes referred to as EMS, or Ethernet Multipoint Service.
Appendix E ISC Layer 2 VPN Concepts VPLS Service Provisioning VPLS can be connected to this VFI. The PE router establishes emulated VCs to all the other PE routers in that VPLS instance and attaches these emulated VCs to the VFI. Packet forwarding decisions are based on the data structures maintained in the VFI. All the PE routers in the VPLS domain use the same VC-ID for establishing the emulated VCs. This VC-ID is also called the VPN-ID in the context of the VPLS VPN.
Appendix E ISC Layer 2 VPN Concepts VPLS Service Provisioning Figure E-9 CE MPLS-Based VPLS Topology CE Device Point-of-View CE Provider Core Emulated LAN CE 104081 CE The PE routers must create a full-mesh of emulated virtual circuits (VCs) to simulate the emulated LAN seen by the CE devices. Forming a full-mesh of emulated VCs simplifies the task of emulating a LAN in the provider core. One property of a LAN is to maintain a single broadcast domain.
Appendix E ISC Layer 2 VPN Concepts VPLS Service Provisioning VPLS for an Ethernet-Based (L2) Provider Core With an Ethernet-based provider core, customer traffic forwarding is trivial in the core. VPLS for an Ethernet-based provider core is a multipoint Layer 2 VPN that connects two or more customer devices using 802.1Q-in-Q tag-stacking technology. A VPLS essentially emulates an Ethernet switch from a users perspective. All connections are peers within the VPLS and have direct communications.
Appendix E ISC Layer 2 VPN Concepts VPLS Service Provisioning Figure E-11 VPLS EWS Topology 192.168.11.11/24 192.168.11.25/24 192.168.11.1/24 192.168.11.2/24 192.168.11.12/24 104080 Ethernet Core The Ethernet Relay Service (ERS or EVP-LAN) offers the any-to-any connectivity characteristics of EWS and the service multiplexing.
I N D EX with CE, creating Numerics 8-2 without CE, creating 1 to 1 VLAN translation C-3 audience 2 to 1 VLAN translation C-4 auditing 3750 iii-xi service requests VLAN translation on C-6 8-11 11-1, 11-12 autodiscovery 7600 creating NPC links through autodiscovery VLAN translation on C-6 autodiscovery, of L2 services A 2-10 12-1 B AAL5 E-8 bridge domain access domains, creating accessing, reports 2-4 using the Bridge Domain ID attribute in VPLS service requests 10-13 13-1 B
Index defining MPLS/EMS (EP-LAN) policies with CE 9-11 FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Multipoint Circuit) A-47, A-53 defining MPLS/ERMS (EVP-LAN) policies with CE 9-3 FlexUNI/EVC (ATM-Ethernet Interworking, Pseudowire Core Connectivity, Point-to-Point Circuit) A-46 configlet examples ATM (Port Mode, Pseudowire Class, E-Line, L2VPN Group Name, IOS XR Device) A-26 ATM over MPLS (VC Mode) A-24 ATM over MPLS (VP Mode) A-25 FlexUNI/EVC (AutoPick Service Instance Na
Index configuring D basic ISC services 1-2 device settings to support ISC data files 2-2 switches, in VTP transparent mode the network creating in service requests 2-2 see also templates and data files) 1-1 the network to support Layer 2 services B-1 using in FlexUNI/EVC ATM-Ethernet service requests 6-24 1-2 transport mode when pseudowire classes are not supported 2-13 using in FlexUNI/EVC service requests working with templates and data files conventions for terminology ATM policies wi
Index deploying service requests multipoint EWS (EP-LAN) for an Ethernet-based provider core E-13 11-1, 11-2 deploying service requests multipoint EWS (EP-LAN) for an MPLS-based provider core E-11 11-1 devices EWS (EPL) service requests configuring device settings 2-2 with CE, creating creating and modifying pseudowire classes for IOS XR devices 2-10 device roles with FlexUNI/EVC without CE, creating 8-16 3-5 setting loopback addresses on N-PE devices setting up 8-8 2-2 F 1-2 setting up
Index setting direct connect links in 6-8 G setting links with L2 access nodes 6-22 setting service request details for setting up links to N-PEs within getting started 6-3 overview 6-8 using templates and data files with tasks 6-24 1-1 1-1 FlexUNI/EVC Ethernet policies defining 3-6 setting FlexUNI attributes in 3-10 setting interface attributes in 3-16 setting service attributes in setting service options in H history, viewing in service requests 3-11 3-8 setting VLAN matching crit
Index defining an Ethernet ERS (EVPL) policy with CE mapping MEF terminologies to network technologies E-3 7-3 defining an Ethernet ERS (EVPL) policy without CE 7-9 defining an Ethernet EWS (EPL) policy with CE terminology conventions 7-15 defining an Ethernet EWS (EPL) policy without CE 7-22 Metro Ethernet Forum (see MEF) FlexUNI/EVC ATM-Ethernet service requests FlexUNI/EVC service requests 8-2 L2VPN service requests creating an ERS (EVPL), ATM, or frame relay L2VPN service request with CE 8-2
Index using N-PE redundancy in FlexUNI/EVC service requests D-3 setting up 1-2 pseudowire classes configuring transport mode when pseudowire classes are not supported 2-13 O creating objective pseudowire class objects iii-xi organization 2-11 modifying iii-xi 2-12 pseudowire core connectivity overview of FlexUNI/EVC ATM-Ethernet policies of FlexUNI/EVC ATM-Ethernet service requests of FlexUNI/EVC support in ISC in FlexUNI/EVC ATM-Ethernet service requests 5-1 in FlexUNI/EVC service reque
Index states of S 11-4 using templates with saving verifying FlexUNI/EVC ATM-Ethernet service requests FlexUNI/EVC service requests L2VPN service requests VPLS service requests 6-24 4-23 8-26 setting in FlexUNI/EVC ATM-Ethernet policies setting in FlexUNI/EVC policies 1-4 ATM link attributes in FlexUNI/EVC ATM-Ethernet service requests 6-18 5-8 3-11 service options setting in FlexUNI/EVC ATM-Ethernet policies setting in FlexUNI/EVC Ethernet policies 5-4 3-8 direct connect links in FlexUNI/E
Index direct connect links in FlexUNI/EVC service requests 4-10 creating a data file in the service request workflow B-16 ISC resources creating data files during service request creation B-12 ISC Services 1-3 2-1 decommissioning service requests with added templates B-18 links to N-PEs in FlexUNI/EVC ATM-Ethernet service requests 6-8 overview links to the N-PEs in FlexUNI/EVC service requests 4-9 B-1 overview support in ISC policies B-4 links with L2 Access nodes in FlexUNI/EVC service reques
Index V VC ID pools, creating 2-7 verifying, service requests configlets in service requests 11-9 9-1 Ethernet/ERMS (EVP-LAN) policy without CE, defining 9-27 11-8 11-7 MPLS/EMS (EP-LAN) policy with CE, defining service request details in service requests 11-7 templates from the service requests window B-18 VLAN matching criteria attributes setting in FlexUNI/EVC ATM-Ethernet policies setting in FlexUNI/EVC policies VLAN pools, creating defining Ethernet/ERMS (EVP-LAN) policy with CE, defini