ent-an1122-4.2 application note software configuration

ENT-AN1122-4.2 Application NoteSoftware Configuration Guide for MPLS-TP

VPPD-04562. 1.0 9/19

Microsemi HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USAWithin the USA: +1 (800) 713-4113 Outside the USA: +1 (949) 380-6100Sales: +1 (949) 380-6136Fax: +1 (949) 215-4996Email: [email protected]

©2018 Microsemi, a wholly owned subsidiary of Microchip Technology Inc. All rights reserved. Microsemi and the Microsemi logo are registered trademarks of Microsemi Corporation. All other trademarks and service marks are the property of their respective owners.

Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of its products and services for any particular purpose, nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit. The products sold hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications. Any performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer’s responsibility to independently determine suitability of any products and to test and verify the same. The information provided by Microsemi hereunder is provided “as is, where is” and with all faults, and the entire risk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to such information itself or anything described by such information. Information provided in this document is proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this document or to any products and services at any time without notice.

About MicrosemiMicrosemi, a wholly owned subsidiary of Microchip Technology Inc. (Nasdaq: MCHP), offers a comprehensive portfolio of semiconductor and system solutions for aerospace & defense, communications, data center and industrial markets. Products include high-performance and radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs and ASICs; power management products; timing and synchronization devices and precise time solutions, setting the world's standard for time; voice processing devices; RF solutions; discrete components; enterprise storage and communication solutions, security technologies and scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well as custom design capabilities and services. Learn more at www.microsemi.com.

mailto:[email protected]

http://www.microsemi.com

VPPD-04562 ENT-AN1122-4.2 Application Note Revision 1.0 iii

Contents

1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Revision 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 MPLS-TP Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 CLI Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 Configuring MPLS LER with E-LINE (VPWS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.2.1 Configuring PW to Operate in Tagged Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2.2 Viewing MPLS Link, PW, and Tunnels Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2.3 MPLS PW and LSP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3 Configuring G.8113.1 MPLS-TP OAM for PW and LSP MEGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3.1 Viewing MEP/Continuity Check (CC) Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3.2 Loss Measurement (LM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3.3 Delay Measurement (DM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.4 Loopback (LB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.5 Test Generation (TST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.6 Alarm Indication Signal/Locked Signal (AIS/LCK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 Configuring G.8113.2 MPLS-TP OAM for PW and LSP MEGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5 Configuring Y.1731/802.1ag Service OAM on Physical Port, Subscriber MIP, and EVC Up MEP . . . . 17

2.5.1 Link Trace (LT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6 MPLS Label Switch Routing (LSR) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.6.1 LSP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.6.2 LSP MIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.7 PW Stitching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.8 Configuring Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.8.1 Hierarchical Quality of Service (HQoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.9 MPLS LER Configuration with E-LAN (Virtual Private LAN Service (VPLS)) . . . . . . . . . . . . . . . . . . . . . 212.10 Linear Protection Switching of PWs or of Tunnel LSPs (1:1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.10.1 1:1 EVC Protection over MPLS Using PW Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.10.2 1:1 EVC Protection over MPLS Using Tunnel LSP Monitoring (Active/Standby) . . . . . . . . . . 252.10.3 1:1 PW or LSP Protection using SPME Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.10.4 1:1 Tunnel LSP Group Protection (Active/Active) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.10.5 1:N Tunnel LSP Group Protection (Active/Standby) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1 Tunnel Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.1.1 Uniform Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1.2 Pipe Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.1.3 Short-Pipe Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.2 OAM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

VPPD-04562 ENT-AN1122-4.2 Application Note Revision 1.0 iv

Figures

Figure 1 Network Configuration with All MEPs and MIPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Figure 2 MPLS Link Layer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Figure 3 MPLS Tunnel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Figure 4 MPLS Pseudo Wire Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Figure 5 EVC Configuration for Tagged Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Figure 6 ECE Configuration for Tagged Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Figure 7 MPLS PW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Figure 8 MPLS-TP Tunnel Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Figure 9 MPLS PW Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Figure 10 MPLS-TP Tunnel Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Figure 11 Configuration of MEP 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 12 Configuration of MEP 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 13 MEP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 14 MEP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 15 LM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 16 DM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 17 LB Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 18 TST Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 19 Status of MEP 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 20 Status of EVC MEP 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 21 Fault Management Configuration of Tunnel MEP 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 22 G.8113.2 MPLS-TP OAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 23 MEP BFDs Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 24 MEP BFDs Authentication key Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 25 Configure LSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 26 Configure MPLS Link Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 27 LSP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 28 MPLS-TP TC/CoS-DP Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 29 MPLS-TP Tunnel Mapping Table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 30 MPLS PW Detailed Configuration for HQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 31 MPLS-TP LSP Detailed Configuration for HQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 32 Protection Setup-One End Shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 33 Configuring EVC Protection over MPLS through PW Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 34 Configuring EVC Protection over MPLS Through Tunnel LSP Monitoring . . . . . . . . . . . . . . . . . . . 26Figure 35 Overview of Tunnel Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 36 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

VPPD-04562 ENT-AN1122-4.2 Application Note Revision 1.0 v

Tables

Table 1 Supported OAM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Revision History

VPPD-04562 ENT-AN1122-4.2 Application Note Revision 1.0 1

1 Revision History

The revision history describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication.

1.1 Revision 1.0Revision 1.0 was published in October 2017. It was the first publication of this document.

MPLS-TP Software Configuration


2 MPLS-TP Software Configuration

This application note describes how to configure MPLS-TP in CEServices™ applications running on the Microsemi Serval-1 Carrier Ethernet switches. This document shows the Command Line Interface (CLI) configurations and web configurations based on the CEServices software development kit (SDK) release 4.2.

Note: This configuration guide uses Up-MEP functionality for certain configurations and requires the Serval-1 image with loop port.

A simple network configuration based on three connected nodes is shown in the following illustration.

Figure 1 • Network Configuration with All MEPs and MIPs

The physical connections between the nodes are 1 Gbps copper or optical (SFP).

The two outer nodes are the MPLS Label Edge Router (LER) nodes and the middle node is the MPLS Label Switch Router (LSR) node.

The customer traffic is received and sent on the two UNI ports.

2.1 CLI Conventions Terminal input/output is indicated as shown in the following code snippet. The user input is written in bold.

# show version

MAC Address : 00-01-c1-00-b3-90Previous Restart : Cold...The configuration examples are shown using the default values. To get all the parameters, use the command: show running-config all-default. To reset counters, use: clear …, for example, clear evc statistics.

Subscriber

CustomerEdge (CE)

NID withMPLS-TP

UNIMPLS-TP Network

LSR

Subscriber

CustomerEdge (CE)

UNI

Tunnel LSPPWEVC

Port MEPPort MEP

SubscriberMIP

NID with MPLS-TP

PW EVC

EVC Up MEP EVC Up MEP

PW MEP PW MEP

Tunnel LSP MEP Tunnel LSP MEP

SubscriberMIP

SubscriberService Frames

SubscriberService Frames

Subscriber MEP Subscriber MEP

Tunnel LSP MIP(s)

Port MEPPort MEP Port MEPPort MEP Port MEPPort MEP



2.2 Configuring MPLS LER with E-LINE (VPWS)To configure a tunnel MPLS Label Switched Path (LSP) with a pseudowire (PW), perform the following steps.

1. Configure the following parameters for the MPLS link layer on the NNI Port 4 as shown in the following illustration. • The MAC address of peer (next hop) MPLS node—tx-mac • The MAC address of this MPLS interface—rx-mac

Note: The rx-mac address should usually be configured to be equal to the switch MAC address. The MPLS link layer MAC address can be configured different from the switch mac address, in this case make sure it is unique.

Note: The Spanning Tree Protocol should be disabled on ports that carry MPLS in order to avoid potential connectivity loss.

Figure 2 • MPLS Link Layer Configuration

2. Configure the following parameters of a tunnel LSP as shown in the following illustration.• In-label—as received from the remote tunnel LSP• Out-label—as expected by remote tunnel LSP• Link—4 (tunnel LSP is connected to the MPLS link 4)• TC—1• TTL—16 (but could be set down to 2 as only two nodes are used in this simple network)• Tunnel Mode—Pipe

Figure 3 • MPLS Tunnel Configuration

3. Create a pseudowire with the following parameters as shown in the following illustration.• Control Word—0 and connected to the LSP• VCCV-type—1 (which means use Control Word)• Label—select the options under Ingress and Egress

Figure 4 • MPLS Pseudo Wire Configuration

The equivalent ICLI commands are as follows.

! MPLS Link Layerinterface GigabitEthernet 1/4 mpls tp link 4 tx-mac 00:21:21:21:21:21 rx-mac 00:14:14:14:14:14 s-tag 100 pcp 7 dei 0



! tunnel LSPinterface tunnel-tp 11 tunnel-mode pipe in-label 6689 out-label 6692 out-link 4 tc 1 ttl 16!Pseudo Wirempls pw 11 mpls label 6693 6696 ttl 4 control-word 0 vccv-type 1 interface out-tunnel 11The MPLS PW can now be connected to an Ethernet Service (EVC). In this case, an EPL EVC is used to take all traffic from the UNI (Port 2) and send it out in PW 11. For details on configuring EVCs see separate software configuration guide.

Note: Learning must be enabled on the EVC to support Subscriber MEG OAM (MIP on the UNI).

2.2.1 Configuring PW to Operate in Tagged ModeIn the previous configuration, the PW is configured to operate in tagged mode, that is, the PW Ethernet payload frames include a service-distinguishing VLAN, 22 This is useful, for example, in cases where multiple EVCs use the same PW. Each EVC should then be configured with separate vid values.

It is also possible to run the PW in 'raw' mode by not configuring 'vid' = 0 for the EVC. In that case, the payload frames won't contain a service-distinguishing VLAN tag.

To configure PW to be operated in tagged mode, perform the following steps.



1. Click Configuration > Ethernet Services > EVCs and press Add New EVC to add new EVC instance.

Figure 5 • EVC Configuration for Tagged Mode

2. Click Configuration > Ethernet Services > ECEs and press Add New ECE to add new ECE instance.



Figure 6 • ECE Configuration for Tagged Mode

The equivalent ICLI commands are as follows.

!E-line configevc 2 vid 22 ivid 22 learning pw 11



evc ece 2 interface GigabitEthernet 1/3 outer-tag add pcp-mode fixed pcp 6 evc 2 cos 6! Configure key sizeinterface GigabitEthernet 1/4 evc key normal

2.2.2 Viewing MPLS Link, PW, and Tunnels StatusTo view the status of MPLS link, PW and tunnel, perform the following steps.

1. Click Monitor > MPLS-TP > Status > Pseudo Wires.Figure 7 • MPLS PW Status

2. Click Monitor > MPLS-TP > Status > LSPs.3. Click Monitor > MPLS-TP > Status > Tunnels.

Figure 8 • MPLS-TP Tunnel Status

The equivalent ICLI codes are as follows.

show mpls tp link 4

MPLS-TP link 4: GigabitEthernet 1/4 OAM: Disabled Tx MAC : 00-21-21-21-21-21 Rx MAC : 00-14-14-14-14-14 VLAN : S-tagged VID : 100 VLAN PCP : 7 VLAN DEI : 0 Src Node ID : 0.0.0.0 Src Global ID : 0 Dst Node ID : 0.0.0.0 Dst Global ID : 0 Dst IfNum : 0

show mpls pw 11MPLS-TP PW 11: OAM: Disabled state: UP Local label : 6693 Remote label : 6696 Interface : MPLS-TP tunnel 11 Tunnel mode : Pipe Type : E-LSP Traffic Class : 0 Time To Live : 4 In CoS Map ID : 0 Out CoS Map ID : 0 VCCV : VCCV-1 Control word : 0show interface tunnel-tp 11 MPLS-TP tunnel 11: 'tunnel 11' OAM: Disbled state:UP In Label : 6689 Out Label : 6692 Interface : MPLS-TP link 4 Tunnel mode : Pipe Type : E-LSP Traffic Class : 1 Time To Live : 16 In CoS Map ID : 0 Out CoS Map ID : 0 Src Node ID : 0.0.0.0 Src Global ID : 0 Dst Node ID : 0.0.0.0 Dst Global ID : 0 Dst Tunnel : 0

Note: The reason OAM is reported as not active for the PW, although it is configured, is that no PW MEP has been configured yet.



The PW state, UP, means the PW has been configured in Serval-1 with all parameters. This does not mean that the connection to the other end has been established. Src and dest node id are used by MPLS Bidirectional Forwarding Detection (BFD) OAM.

2.2.3 MPLS PW and LSP StatisticsTo view MPLS PW and LSP statistics, perform the following steps.

1. Click Monitor > MPLS-TP > Statistics > Pseudo Wires.Figure 9 • MPLS PW Statistics

2. Click Monitor > MPLS-TP > Statistics > LSPs.Figure 10 • MPLS-TP Tunnel Statistics

The equivalent ICLI codes are as follows.

show mpls pw statistics 11MPLS-TP PW 11: OAM: Disabled state: UP Rx Green Frames: 101202 Tx Green Frames: 86621 Rx Yellow Frames: 0 Tx Yellow Frames: 0 Rx Red Frames: 0 Rx Discard Frames: 0 Tx Discard Frames: 0 Rx Green Bytes: 7286544 Tx Green Bytes: 6583196 Rx Yellow Bytes: 0 Tx Yellow Bytes: 0 Rx Red Bytes: 0 Rx Discard Bytes: 0 Tx Discard Bytes: 0

show interface tunnel-tp statistics 11MPLS-TP tunnel 11: 'tunnel 11', tunnel-mode pipe, OAM active, state UP Rx Green Frames: 101202 Tx Green Frames: 86621 Rx Yellow Frames: 0 Tx Yellow Frames: 0 Rx Red Frames: 0 Rx Discard Frames: 0 Tx Discard Frames: 0 Rx Green Bytes: 8096160 Tx Green Bytes: 7276164 Rx Yellow Bytes: 0 Tx Yellow Bytes: 0 Rx Red Bytes: 0 Rx Discard Bytes: 0 Tx Discard Bytes: 0

2.3 Configuring G.8113.1 MPLS-TP OAM for PW and LSP MEGs G.8113.1 MPLS-TP OAM (PTN/Y.1731-based) is configured in the same way as the Ethernet service OAM using the MEP commands.

To configure the G.8113.1 MPLS-TP OAM (PTN/Y.1731-based), perform the following step.

• Create a tunnel and PW OAM with CC rate of 1 fps and enable delay measurements and loss measurements as shown in the following illustrations.



Figure 11 • Configuration of MEP 41

Figure 12 • Configuration of MEP 51

[The equivalent ICLI commands are as follows:

! Tunnel OAMmep 41 down domain tunnel-tp flow 11 level 0mep 41 meg-id MEG_ID1 itumep 41 mep-id 111mep 41 peer-mep-id 112 mac 00-21-21-21-21-21mep 41 cc 7mep 41 ccm-tlvmep 41 lm 0mep 41 dm 0 interval 10 last-n 10! PW OAMmep 51 down domain pw flow 11 level 7mep 51 meg-id MEG_ID51 itumep 51 mep-id 51mep 51 peer-mep-id 52 mac 00-21-21-21-21-21mep 51 cc 7mep 51 ccm-tlvmep 51 lm 0mep 51 dm 0 interval 10 last-n 10

2.3.1 Viewing MEP/Continuity Check (CC) StatusTo view the MEP/CC status, perform the following step.



1. Click Configuration > MEP > Configuration and then click on the specific Instance.Figure 13 • MEP Status

The equivalent ICLI commands are as follows:

Figure 14 • MEP Status

show mep 41 detail

MEP state is: Inst cLevel cMeg cMep cAis cLck cLoop cConf cSsf aBlk aTsf Peer MEP 41 False False False False False False False False False False 112 cLoc cRdi cPeriod cPrioFalse False False False

MEP Basic Configuration is:Inst Mode Voe Vola Direct Port Dom Level FormatName Meg id Mep id Vid Flow Eps MAC 41 Mep Down GigabitEthernet 1/4 MplsT 0 ITU ICC MEG_ID1 111 0 11 NOT AVAILABLE

show mep 41 cc detail

MEP CC Configuration is: Inst Prio Rate Tlv 41 7 1s Tlv

2.3.2 Loss Measurement (LM)To view the status of LM, perform the following step.

• Click Configuration > MEP > Configuration, click the specific instance, and click Performance Monitoring.

show mep 41 detail

MEP state is: Inst cLevel cMeg cMep cAis cLck cLoop cConf cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 41 False False False False False False False False False False 112 False False False False

MEP Basic Configuration is: Inst Mode Voe Vola Direct Port Dom Level Format Name Meg id Mep id Vid Flow Eps MAC

41 Mep Down GigabitEthernet 1/4 MplsT 0 ITU ICC MEG_ID1 111 0 11 NOT AVAILABLE

show mep 41 cc detail

MEP CC Configuration is:Inst Prio Rate Tlv

41 7 1s Tlv



Figure 15 • LM Status


sh mep 41 lm detail

Frame Loss Ratio (Flr) is shown in per mille, i.e. (Loss/Tx)*1000.MEP LM state is:Inst Tx Rx Near Far Threshold Near Far Near Far Count Count Count Ratio Ratio Ratio Ratio interval interval near interval interval min/max min/max /total /total /far /total /total 41 1279 1164 0/0 0/0 0/0 0/0 0/0 0/0 0/0

MEP LM Configuration is:Inst Prio Cast Ended Rate Flr Flow Count Oam Loss Threshold Count 41 0 Multi Single 1s 5 Disable Y1731

2.3.3 Delay Measurement (DM)Notice that the delay measurements which have a negative delay is counted as RxErr.

To view the status of DM, perform the following step.

• Click Configuration > MEP > Configuration, click the specific instance, and click Performance Monitoring.

Figure 16 • DM Status


show mep dm 41

MEP DM state is:

RxTime : Rx TimeoutRxErr : Rx ErrorAvTot : Average delay TotalAvN : Average delay last NMin : Min Delay valueMax : Max Delay valueAvVarT : Average delay Variation TotalAvVarN : Average delay Variation last NMinVar : Min Delay Variation valueMaxVar : Max Delay Variation value



OF : Overflow. The number of statistics overflow.

Inst Tx Rx RxTime RxErr AvTot AvN Min Max AvVarTot AvVarN MinVar MaxVar OF Unit1-Way FtoN 41 0 0 0 0 0 0 0 0 0 0 0 0 0 us1-Way NtoF 41 0 0 0 0 0 0 0 0 0 0 0 0 0 us2-Way 41 1204 1204 0 0 201 200 199 216 0 1 0 15 0 us

MEP DM binning state is: ins bin0 bin1 bin2 bin3 bin4 bin5 bin6 bin7 bin8 bin9Frame Delay1-Way FtoN 41 0 0 0 0 0 0 0 0 0 01-Way NtoF 41 0 0 0 0 0 0 0 0 0 02-Way 41 1204 0 0 0 0 0 0 0 0 0Inter-Frame Delay Variation1-Way FtoN 41 0 0 0 0 0 0 0 0 0 01-Way NtoF 41 0 0 0 0 0 0 0 0 0 02-Way 41 1204 0 0 0 0 0 0 0 0 0

2.3.4 Loopback (LB)With loopback it is possible to test the connectivity to the MEP at the other end of the tunnel and PW, and to the MIP in the LSR. When doing LB to an LSP MIP, the MIP is determined by the TTL, that is. TTL of 1 means the next hop.

To view the status of LB, perform the following step.

• Click Configuration > MEP > Configuration, click the specific instance, and click Fault Management.

Figure 17 • LB Status


(config)# mep 41 lb 7 mpls ttl 16 count 5 size 64 interval 10sw1(config)# do show mep 41 lbMEP LB state is:Inst Transaction ID TX LBM Peer Received Out Of Order 41 16 5 mepId: 112 5 0!(config)# mep 41 lb 7 mpls ttl 1 count 5 size 64 interval 10sw1(config)# do show mep 41 lbMEP LB state is:



Inst Transaction ID TX LBM Peer Received Out Of Order 41 21 5 0 0

2.3.5 Test Generation (TST)To enable test frame generation and reception use the commands as shown in the following code block.

!Test frame generation: First set parameters, then activate TX:(config)# mep 41 tst 0 mep-id 112 rate 100 size 1000(config)# mep 41 tst tx!Test frame reception(config)# mep 41 tst rxTest frames are processed by software that limits the number of frames that can be processed per second. To test higher data rates, bigger frames should be used.

To view the reception of test frames execute the following ICLI command.

show mep 41 tstMEP TST state is:Inst TX frame count RX frame count RX rate Test time 41 0 678081 647 595# sh mep

MEP state is: Inst cLevel cMeg cMep cAis cLck cLoop cConf cDeg cSsf aBlk aTsd aTsf Peer MEP cLoc cRdi cPeriod cPrio 33 False False False True False False False False True False False True 2 False False False False 41 False False False False False False False False False False False True 112 True False False False 51 False False False False False False False False False False False False 52 False False False FalseDufe to a software limitation, TST TX counters are not available.• Click Configuration > MEP > Configuration, click the specific instance, and click Fault

Management.Figure 18 • TST Status

2.3.6 Alarm Indication Signal/Locked Signal (AIS/LCK)MPLS link and tunnel MEPs support AIS and LCK for the LSP and EVC client layers. So it is possible to have, for example, an MPLS section OAM MEP insert AIS and/or LCK OAM PDUs into a client LSP or into an EVC of a client PW.

LSP client AIS/LCK is signaled using the label stack for the LSP followed by a Generic Associated Channel Label (GAL). EVC client AIS/LCK is signaled using normal Y.1731 OAM.

The following configuration adds an LSP that uses the existing tunnel for the forward direction and a new MPLS link for the reverse direction. The LSP is then added as a client to the tunnel MEP, as is the EVC. Add another MEP, an up-MEP, for the EVC UNI; this MEP receives an AIS in case the MPLS tunnel encounters LOC. It is added in this example to demonstrate AIS indication.

mpls tp lsp 22



forward-lsp in-label 5000 out-label 5001 out-tunnel 11 reverse-lsp in-label 5002 out-label 5003 out-link 4!interface GigabitEthernet 1/2 switchport hybrid allowed vlan none switchport mode hybrid no lldp receive no lldp transmit no spanning-tree mpls tp link 2 tx-mac 00:34:34:34:34:34 rx-mac 00:22:22:22:22:22 s-tag 100 pcp 7 dei 0!mep 33 up domain evc flow 2 level 4 interface GigabitEthernet 1/3mep 33 meg-id EVC itumep 33 peer-mep-id 2!mep 41 down domain tunnel-tp flow 11 level 0mep 41 meg-id MEG_ID1 itumep 41 mep-id 111mep 41 peer-mep-id 112 mac 00-21-21-21-21-21mep 41 cc 0mep 41 client domain evc flow 2 level 4 ais-prio 6 lck-prio 6mep 41 client domain lsp flow 22mep 41 aisWhen the tunnel 41 experiences LOC, the following status indicates LOC on MEP 41 and AIS on EVC MEP 33, and the consequent Server Signal Fail and Trail Signal Fail.

sh mep

MEP state is: Inst cLevel cMeg cMep cAis cLck cLoop cConf cDeg cSsf aBlk aTsd aTsf Peer MEP cLoc cRdi cPeriod cPrio 33 False False False True False False False False True False False True 2 False False False False 41 False False False False False False False False False False False True 112 True False False False 51 False False False False False False False False False False False False 52 False False False FalseTo view the same status perform the following step.

• Click Configuration > MEP > Configuration and click the specific MEP instances to view the status on the web as shown in the following illustrations.

Figure 19 • Status of MEP 41

Figure 20 • Status of EVC MEP 33

To perform the fault management configuration of tunnel MEP 41, perform the following step.



• Click Configuration > MEP > Configuration, select the relevant MEP instance, and then click Fault Management.

Figure 21 • Fault Management Configuration of Tunnel MEP 41

2.4 Configuring G.8113.2 MPLS-TP OAM for PW and LSP MEGs G.8113.2 MPLS-TP OAM (BFD-based) is configured using the MEP commands.

To configure the G.8113.2 MPLS-TP OAM (BFD-based), perform the following step.

1. Configure a destination and a source IP address together with a tunnel-tp ID on the tunnel LSP as shown in the following illustration.

Figure 22 • G.8113.2 MPLS-TP OAM Configuration

2. Configure the MEP as configured for Y.1731 based OAM, but with BFD CC as shown in the following illustration.



Figure 23 • MEP BFDs Configuration


interface GigabitEthernet 1/2 mpls tp link 1 tx-mac 00:02:02:02:02:02 rx-mac 00:01:01:01:01:01interface tunnel-tp 1 tp destination 10.0.0.1 tunnel-tp 2 tp source 10.0.0.1 in-label 0x100 out-label 0x200 out-link 1 tc 0 ttl 16mep 1 down domain tunnel-tp flow 1 level 0 mep 1 bfd cc-period 10000The Bfd cc can run unauthenticated as show in the previous configuration or with authentication. Three authentication key types are supported:

• Simple password• MD5, or • SHA1

Figure 24 • MEP BFDs Authentication key Configuration


# Configure keys:mep bfd auth-key 0 simple-pwd key 000102030405060708090a0b0c0d0e0f mep bfd auth-key 1 md5 key 000102030405060708090a0b0c0d0e0f mep bfd auth-key 2 sha1 key 000102030405060708090a0b0c0d0e0f10111213 # Select key, using one of:mep 1 bfd cc-period 10000 tx-auth key 0 rx-auth mep 1 bfd cc-period 10000 tx-auth key 1 rx-auth mep 1 bfd cc-period 10000 tx-auth key 2 rx-authThe default bfd cc configuration is "coordinated" which is for bi-directional tunnels.

Status:

sh mep 1 bfd

MEP BFD state is: Inst CC Tx CC Rx CV Tx CV Rx CC Rx inv CV Rx inv Discriminator State Diag 1 428833 428777 5093 4932 0 0 0x337f52e2 UP NONE

MEP BFD remote state is: Inst State Diag Discriminator Min. Rx Flags 1 UP NONE 0x2db0d0a4 10000 us 0x00



show mep 1

MEP state is: Inst cLevel cMeg cMep cAis cLck cLoop cConf cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 1 False False False False False False False False False False BFD False False False False

2.5 Configuring Y.1731/802.1ag Service OAM on Physical Port, Subscriber MIP, and EVC Up MEPFor complete OAM functionality, the configurations of physical port MEP, subscriber MIP, and EVC up MEP is described in this section.

When an Ethernet EVC is carried over an MPLS-TP network, PW OAM and tunnel LSP OAM are used to monitor the health of the MPLS domain, as described in the previous section. Combined with service OAM on the EVC up MEP and port OAM on the physical links, the operator has full visibility of the complete network. The subscriber can monitor the service delivered using subscriber MEG OAM including the end to end delay and loss measurements. The connectivity can be tested using link trace.

!Port MEP on NNI portmep 4 down domain port level 0 interface GigabitEthernet 1/4mep 4 mep-id 44mep 4 voemep 4 peer-mep-id 45 mac 00-01-C1-00-C3-E1mep 4 cc 0mep 4 ccm-tlvmep 4 dm 0 interval 10 last-n 10!Subscriber MIP on UNI port!Implemented as two half MIPs, one for up and one for downmep 31 mip down domain evc vid 113 flow 2 level 7 interface GigabitEthernet 1/3mep 31 vid 113mep 32 mip up domain evc vid 113 flow 2 level 7 interface GigabitEthernet 1/3mep 32 vid 113!EVC Up-mep on NNI portmep 33 up domain evc flow 2 level 4 interface GigabitEthernet 1/3mep 33 voemep 33 peer-mep-id 2 mac 00-01-C1-00-C4-13mep 33 cc 6mep 33 ccm-tlvmep 33 lm 6mep 33 dm 6 interval 10 last-n 10

2.5.1 Link Trace (LT)With the previous MIPs in the service provider network, the subscriber can check the connectivity using the LT generated by the customer equipment by executing the following command.

(config)# mep 3 lt 6 mep-id 2 ttl 3show mep 3 ltMEP LT state is: Inst Transaction ID Ttl Mode Direction Forwarded relay 3 36 2 Mip Down Yes FDB 1 Mip Up Yes FDB 0 Mep Down No MAC Last MAC Next MAC00-01-C1-00-71-43 00-01-C1-00-B6-D300-01-C1-00-B6-D3 00-01-C1-00-C4-1300-01-C1-00-C4-13 00-01-C1-00-72-03When the subscriber sends an LT message:



1. The subscriber MIP on the near UNI (down half MIP) responds and forwards the LT to the remote end UNI where another subscriber MIP (up half MIP) responds.

2. The subscriber MEP at the customer equipment responds. 3. Subsequently, the MAC addresses of each MIP/MEP are given.

2.6 MPLS Label Switch Routing (LSR) ConfigurationTo configure the LSR functionality, perform the following steps.

1. Configuring two LSPs, one in the forward direction and one in the reverse direction as shown in the following illustration.

Figure 25 • Configure LSPs

2. As with the LER function, define an MPLS link layer as shown in the following illustration.Figure 26 • Configure MPLS Link Layer


interface GigabitEthernet 1/1 mpls tp link 1 tx-mac 00:14:14:14:14:14 rx-mac 00:21:21:21:21:21 s-tag 100 pcp 7 dei 0!interface GigabitEthernet 1/2 mpls tp link 2 tx-mac 00:34:34:34:34:34 rx-mac 00:22:22:22:22:22 s-tag 100 pcp 7 dei 0!mpls tp lsp 1 forward-lsp in-label 6692 out-label 6692 out-link 2 reverse-lsp in-label 6689 out-label 6689 out-link 1

2.6.1 LSP StatusTo view the LSP status, perform the following step.

• Click Monitor > MPLS-TP > Status > LSPs and the LSP status is displayed as shown in the following illustration.

Figure 27 • LSP Status


show mpls tp lspMPLS-TP LSP XC 1: 'lsp_xc 1' OAM: Disabled state: UP Fwd In Label : 6692 Fwd Out Label : 6692 Fwd Interface : MPLS-TP link 2 Fwd HQoS ID : **none** Fwd In CoS Map ID : 0 Fwd Out CoS Map ID : 0 Fwd Type : E-LSP Rev In Label : 6689 Rev Out Label : 6689 Rev Interface : MPLS-TP link 1 Rev HQoS ID : **none**



Rev In CoS Map ID : 0 Rev Out CoS Map ID : 0 Rev Type : E-LSP Src Node ID : 0.0.0.0 Src Global ID : 0 Dst Node ID : 0.0.0.0 Dst Global ID : 0 Src Tunnel : 0 Src LSP number : 0 Dst Tunnel : 0 Dst LSP number : 0

2.6.2 LSP MIPTo create an MIP on an LSP is possible using the following commands.

mep 41 mip up domain lsp flow 1 level 0mep 42 mip down domain lsp flow 1 level 0

2.7 PW StitchingIt is possible to connect two PWs together, known as PW Stitching. The two PWs are connected together without analyzing the payload. OAM on these PWs is not possible. The following example shows how to connect to PWs.

mpls pw 1 mpls label 100 200 interface out-tunnel 10 stitch 2!mpls pw 2 mpls label 1000 2000 interface out-tunnel 20 stitch 1

2.8 Configuring Quality of Service (QoS) There are two QoS: fixed QoS and mapped QoS.

In Configuring MPLS LER with E-LINE (VPWS), page 3, the fixed QoS is used. In that case, the Traffic Class (TC) is set to 1.

For mapped QoS, a mapping table needs to be defined in the following procedure. Eight mapping tables are available.

To define the mapping tables, perform the following steps.

1. Click Configuration > MPLS-TP > TC/Cos-DP Mapping and define two mapping tables where table 1 is used on egress (mapping of CoS into MPLS TC), and mapping table 2 is used on ingress (mapping MPLS TC into CoS) as shown in the following illustration.

Figure 28 • MPLS-TP TC/CoS-DP Mapping Configuration

2. Click Configuration > MPLS-TP > Tunnel and select the relevant tunnel by clicking the tunnel instance.

Figure 29 • MPLS-TP Tunnel Mapping Table Configuration


mpls tp cos-map 1 ingress tc 0 map-to cos 7 dp 0 ingress tc 1 map-to cos 1 dp 0 ingress tc 2 map-to cos 2 dp 0 ingress tc 3 map-to cos 3 dp 0



ingress tc 4 map-to cos 4 dp 0 ingress tc 5 map-to cos 5 dp 0 ingress tc 6 map-to cos 6 dp 0 ingress tc 7 map-to cos 7 dp 0 egress cos 0 dp 0 map-to tc 0 egress cos 1 dp 0 map-to tc 1 egress cos 2 dp 0 map-to tc 2 egress cos 3 dp 0 map-to tc 3 egress cos 4 dp 0 map-to tc 4 egress cos 5 dp 0 map-to tc 5 egress cos 6 dp 0 map-to tc 6 egress cos 7 dp 0 map-to tc 7 egress cos 0 dp 1 map-to tc 0 egress cos 1 dp 1 map-to tc 1 egress cos 2 dp 1 map-to tc 2 egress cos 3 dp 1 map-to tc 3 egress cos 4 dp 1 map-to tc 4 egress cos 5 dp 1 map-to tc 5 egress cos 6 dp 1 map-to tc 6 egress cos 7 dp 1 map-to tc 7 !mpls tp cos-map 2 ingress tc 0 map-to cos 0 dp 0 ingress tc 1 map-to cos 1 dp 0 ingress tc 2 map-to cos 2 dp 0 ingress tc 3 map-to cos 3 dp 0 ingress tc 4 map-to cos 4 dp 0 ingress tc 5 map-to cos 5 dp 0 ingress tc 6 map-to cos 6 dp 0 ingress tc 7 map-to cos 7 dp 0 egress cos 0 dp 0 map-to tc 0 egress cos 1 dp 0 map-to tc 1 egress cos 2 dp 0 map-to tc 2 egress cos 3 dp 0 map-to tc 3 egress cos 4 dp 0 map-to tc 4 egress cos 5 dp 0 map-to tc 5 egress cos 6 dp 0 map-to tc 6 egress cos 7 dp 0 map-to tc 7 egress cos 0 dp 1 map-to tc 0 egress cos 1 dp 1 map-to tc 1 egress cos 2 dp 1 map-to tc 2 egress cos 3 dp 1 map-to tc 3 egress cos 4 dp 1 map-to tc 4 egress cos 5 dp 1 map-to tc 5 egress cos 6 dp 1 map-to tc 6 egress cos 7 dp 1 map-to tc 7

! Tunnel with QoS mappinginterface tunnel-tp 11 tunnel-mode pipe in-label 6689 out-label 6692 out-link 4 ttl 16 in-cos-map 2 out-cos-map 1The default LSP type is E-LSP, where the previous QoS mapping is used directly. Also for L-LSPs, it is possible to map CoS into TC bits. The TC and Time to Live (TTL) handling in an MPLS-TP network depends on the configured tunnel mode.



2.8.1 Hierarchical Quality of Service (HQoS)Serval-1 supports hierarchical QoS with egress shaping. HQoS is possible to use for PWs and LSPs.

To configure HQoS, perform the following steps.

1. Create HQoS configuration on the interface, see HQoS configuration guide for the actual configuration parameters.

Figure 30 • MPLS PW Detailed Configuration for HQoS

2. Then connect the PW or LSP to the HQoS using the HQoS ID.Figure 31 • MPLS-TP LSP Detailed Configuration for HQoS


! PW with HQoSmpls pw 11 mpls label 6693 6696 ttl 4 control-word 0 vccv-type 1 interface out-tunnel 11 hqos 11! LSR with HQoSmpls tp lsp 1 forward-lsp in-label 6692 out-label 6692 out-link 2 hqos 2 reverse-lsp in-label 6689 out-label 6689 out-link 1 hqos 1

2.9 MPLS LER Configuration with E-LAN (Virtual Private LAN Service (VPLS))Configuration of an E-LAN EVC over MPLS-TP (VPLS) is done in the same way as of E-LINE (VPWS), with multiple PWs attached to the EVC. Network access ports are either Ethernet ports connected through ECE (MEF UNI ports) or PWs connected to the EVC (IETF attachment circuits). NNI (Network) ports, which need split-horizon are connected to the EVC using the split-horizon parameter.



Note: Serval-1 plays the role of H-VPLS MTU-s in a VPLS network. Complete VPLS functionality is possible, but requires separate ports for each PW, which does not scale, but make it possible to use Serval-1 for VPLS testing.

The following example shows the configuration of H-VPLS MTU-s with two UNI ports (Port 3 and Port 5).

evc 2 vid 22 ivid 22 learning pw 11evc ece 2 interface GigabitEthernet 1/3 outer-tag add pcp-mode fixed pcp 6 evc 2 cos 6evc ece 3 interface GigabitEthernet 1/5 outer-tag add pcp-mode fixed pcp 6 evc 2 cos 6The following example shows the Configuration of VPLS with one UNI port and two NNI ports.

evc 2 vid 22 ivid 22 learning pw split-horizon 1,11evc ece 2 interface GigabitEthernet 1/3 outer-tag add pcp-mode fixed pcp 6 evc 2 cos 6

2.10 Linear Protection Switching of PWs or of Tunnel LSPs (1:1)Configuration of linear protection requires the following steps.

1. First configure a working and a PW or tunnel LSP.2. Configure a protection PW or tunnel LSP.3. Create PW and tunnel LSP MEPs on both protection and working PW/tunnel.4. Enable CC on the MEPs.5. On Protecting PW/tunnel enable Linear Automatic Protection Switching (LAPS).6. Create Ethernet Protection Switching (EPS) instance with working and protecting PW/tunnel and

with the MEPs.7. Connect the PW to an EVC.

Note: Other protection mechanisms like spanning tree and link aggregation do not interwork with linear protection and should be disabled.

Linear protection is supported in 5 different modes:

• 1:1 EVC protection over MPLS using pseudowire monitoring• 1:1 EVC protection over MPLS using tunnel LSP monitoring• 1:1 PW or LSP protection using Sub-Path Maintenance Entity (SPME) monitoring• 1:1 tunnel LSP group protection (active/active)• 1:N tunnel LSP group protection (active/standby)The following illustration shows the linear protection setup at one end of the system.



Figure 32 • Protection Setup-One End Shown

2.10.1 1:1 EVC Protection over MPLS Using PW Monitoring The following configuration shows two sets of PWs, tunnel LSPs and EPS instances as shown in the previous illustration. NNI is configured on port 3 and protection is configured on port 4. UNI is configured on ports are 1 and 2.Hierarchical Quality of Service (HQoS)

To complete a basic port and MPLS link layer configuration, perform the following step.

• Create two sets of PWs, tunnel LSPs and EPS instances with the following setup as shown in the following illustration.• NNI is configured on port 3 and protection is configured on port 4. • UNI is configured on ports are 1 and 2

Figure 33 • Configuring EVC Protection over MPLS through PW Monitoring

Note: The Alarm indication in the previous illustration should go green once the peer is configured.


interface GigabitEthernet 1/1 switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybrid no lldp transmit no spanning-tree evc key normal!interface GigabitEthernet 1/2 switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybrid no lldp transmit no spanning-tree evc key normal!interface GigabitEthernet 1/3

VSC5618EVReferenceSystem #1

VSC5619EVReferenceSystem #3

NID/ LER

Mgm

t

UN

I 1

NN

I 1

1 GE 1 GE

UN

I 1 1 GE

NN

I 2

UN

I 2

1 GE

UN

I 21 GE

Impairments

NID/LER

Mirror

1 G

E

Mgm

t

Mgm

t

VSC7428EVReference

MPLS Monitoring

VSC5618EVReference System #2

LSR

Mgm

t

Mgm

t

1 GE

NN

I 1

NN

I 2PWEVC LSP

CalnexParagon-X

PW EVCLSP

VLAN

Delay

Configuration

Laptop

VLANVLAN VLAN

CPU CPU CPUCPU

Mgmt

Mgmt

Mgm

t

FrameGenerator

FrameChecker

FrameChecker

FrameGenerator

100us delay in both directions

Mgmt

CPU

Mgmt

CPU

Mgm

t

Mgm

t

SW1 SW2 SW3



switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybrid no lldp transmit no spanning-tree evc key normal mpls tp link 1 tx-mac 00:33:33:33:33:33 rx-mac 00:03:03:03:03:03 mpls tp link 3 tx-mac 00:03:03:03:03:03 rx-mac 00:33:33:33:33:33!interface GigabitEthernet 1/4 switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybrid no lldp transmit no spanning-tree evc key normal mpls tp link 2 tx-mac 00:44:44:44:44:44 rx-mac 00:04:04:04:04:04 mpls tp link 4 tx-mac 00:04:04:04:04:04 rx-mac 00:44:44:44:44:44Step 1 and 2:

interface tunnel-tp 1 tunnel-mode short-pipe in-label 307 out-label 305 out-link 1 tc 5 ttl 150!interface tunnel-tp 2 tunnel-mode short-pipe in-label 323 out-label 321 out-link 2 tc 5 ttl 150!interface tunnel-tp 3 tunnel-mode short-pipe in-label 305 out-label 307 out-link 3 tc 5 ttl 150!interface tunnel-tp 4 tunnel-mode short-pipe in-label 321 out-label 323 out-link 4 tc 5 ttl 150!mpls pw 1 tunnel-mode short-pipe mpls label 308 306 tc 7 ttl 200 control-word 0 vccv-type 1 interface out-tunnel 1!mpls pw 2 tunnel-mode short-pipe mpls label 324 322 tc 7 ttl 200 control-word 0 vccv-type 1 interface out-tunnel 2!mpls pw 3 tunnel-mode short-pipe mpls label 306 308 tc 7 ttl 200 control-word 0 vccv-type 1



interface out-tunnel 3!mpls pw 4 tunnel-mode short-pipe mpls label 322 324 tc 7 ttl 200 control-word 0 vccv-type 1 interface out-tunnel 4Step 3, 4, 5, and 6: Configuration of MEPs and EPS instances is shown in the following code block. Assuming the tunnel LSPs and PWs have been created as shown previously.

mep 1 down domain pw flow 1 level 0mep 1 meg-id MEG_ID1 itumep 1 peer-mep-id 3 mac 00-33-33-33-33-33mep 1 cc 0mep 2 down domain pw flow 2 level 0mep 2 meg-id MEG_ID1 itumep 2 mep-id 2mep 2 peer-mep-id 4 mac 00-44-44-44-44-44mep 2 cc 0mep 2 aps 0 lapsmep 3 down domain pw flow 3 level 0mep 3 meg-id MEG_ID1 itumep 3 mep-id 3mep 3 peer-mep-id 1mep 3 cc 0mep 4 down domain pw flow 4 level 0mep 4 meg-id MEG_ID1 itumep 4 mep-id 4mep 4 peer-mep-id 2mep 4 cc 0mep 4 aps 0 lapseps 1 domain pw architecture 1for1 work-flow 1 protect-flow 2eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 2 domain pw architecture 1for1 work-flow 3 protect-flow 4eps 2 mep-work 3 mep-protect 4 mep-aps 4Step 7: Connection of EVC

The EVCs are created on working port and working PW.

evc 1 vid 11 ivid 11 pw 1evc 2 vid 11 ivid 22 pw 3evc ece 1 interface GigabitEthernet 1/1 cos 0evc ece 2 interface GigabitEthernet 1/2 evc 2 cos 0

2.10.2 1:1 EVC Protection over MPLS Using Tunnel LSP Monitoring (Active/Standby)Protection based on the tunnel LSP MEPs follows the same configuration steps, except that:

• The MEPs used are now the tunnel LSP MEPs.• The EPS instance is in the tunnel LSP domain.

Note: With tunnel LSP protection, it is possible to protect a group of PWs each carrying a number of EVCs. A protected tunnel LSP can carry a number of LSPs.

To configure EVC protection over MPLS using tunnel LSP monitoring, perform the following step.

• Click Configuration > EPS and configure EVC protection over MPLS using tunnel LSP monitoring as shown in the following illustration.



Figure 34 • Configuring EVC Protection over MPLS Through Tunnel LSP Monitoring


mep 1 down domain tunnel-tp flow 1 level 0mep 1 meg-id MEG_ID1 itumep 1 peer-mep-id 3 mac 00-33-33-33-33-33mep 1 cc 0mep 2 down domain tunnel-tp flow 2 level 0mep 2 meg-id MEG_ID1 itumep 2 mep-id 2mep 2 peer-mep-id 4 mac 00-44-44-44-44-44mep 2 cc 0mep 2 aps 0 lapsmep 3 down domain tunnel-tp flow 3 level 0mep 3 meg-id MEG_ID1 itumep 3 mep-id 3mep 3 peer-mep-id 1mep 3 cc 0mep 4 down domain tunnel-tp flow 4 level 0mep 4 meg-id MEG_ID1 itumep 4 mep-id 4mep 4 peer-mep-id 2mep 4 cc 0mep 4 aps 0 lapseps 1 domain tunnel-tp architecture 1for1 work-flow 1 protect-flow 2eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 2 domain tunnel-tp architecture 1for1 work-flow 3 protect-flow 4eps 2 mep-work 3 mep-protect 4 mep-aps 4

2.10.3 1:1 PW or LSP Protection using SPME MonitoringIn protection based on SPME monitoring, a sub-LSP is inserted in between the PW and LSP, so the MPLS label stack consists of three labels.

To configure PW or LSP protection using tunnel SPME monitoring, execute the following commands.

interface tunnel-tp 1 tunnel-mode short-pipe in-label 563 out-label 561 out-tunnel 11 tc 5 ttl 150 tp destination 1.2.3.4 tunnel-tp 234 spme lsp 22!interface tunnel-tp 2 tunnel-mode short-pipe in-label 579 out-label 577 out-tunnel 12 tc 5 ttl 150 tp destination 1.2.3.4 tunnel-tp 345 spme lsp 33!interface tunnel-tp 3 tunnel-mode short-pipe in-label 561 out-label 563 out-tunnel 13 tc 5 ttl 150 tp destination 1.2.3.4 tunnel-tp 345 spme lsp 44!interface tunnel-tp 4



tunnel-mode short-pipe in-label 577 out-label 579 out-tunnel 14 tc 5 ttl 150 tp destination 1.2.3.4 tunnel-tp 345 spme lsp 55!interface tunnel-tp 11 tunnel-mode short-pipe in-label 307 out-label 305 out-link 1 tc 5 ttl 150!interface tunnel-tp 12 tunnel-mode short-pipe in-label 323 out-label 321 out-link 2 tc 5 ttl 150!interface tunnel-tp 13 tunnel-mode short-pipe in-label 305 out-label 307 out-link 3 tc 5 ttl 150!interface tunnel-tp 14 tunnel-mode short-pipe in-label 321 out-label 323 out-link 4 tc 5 ttl 150!mpls pw 1 tunnel-mode short-pipe mpls label 308 306 tc 7 ttl 200 control-word 0 vccv-type 1 interface out-tunnel 1!mpls pw 3 tunnel-mode short-pipe mpls label 306 308 tc 7 ttl 200 control-word 0 vccv-type 1 interface out-tunnel 3!mep os-tlv oui 0xC sub-type 0x1 value 0x2mep 1 down domain tunnel-tp flow 1 level 0mep 1 meg-id MEG_ID1 itumep 1 peer-mep-id 3mep 1 cc 0mep 2 down domain tunnel-tp flow 2 level 0mep 2 meg-id MEG_ID1 itumep 2 mep-id 2mep 2 peer-mep-id 4mep 2 cc 0mep 2 aps 0 lapsmep 3 down domain tunnel-tp flow 3 level 0mep 3 meg-id MEG_ID1 itumep 3 mep-id 3mep 3 peer-mep-id 1mep 3 cc 0mep 4 down domain tunnel-tp flow 4 level 0mep 4 meg-id MEG_ID1 itumep 4 mep-id 4mep 4 peer-mep-id 2



mep 4 cc 0mep 4 aps 0 lapseps 1 domain tunnel-tp architecture 1for1 work-flow 1 protect-flow 2eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 2 domain tunnel-tp architecture 1for1 work-flow 3 protect-flow 4eps 2 mep-work 3 mep-protect 4 mep-aps 4

2.10.4 1:1 Tunnel LSP Group Protection (Active/Active)Active/active tunnel LSP protection is achieved using two instances of EPS. Each tunnel LSP takes the working role in one EPS instance and the protect role in the other EPS instance.

2.10.5 1:N Tunnel LSP Group Protection (Active/Standby)1:N tunnel LSP protection is configured with multiple (N) 1:1 EPS instances. All EPS instances share the same protecting tunnel LSP.

Appendix


3 Appendix

This chapter contains sections which provide additional information on the topic explored.

3.1 Tunnel ModesA set of behaviors are defined that gives a mechanisms to control TC (EXP) values in various scenarios. These mechanisms are called tunnel modes. Three tunnel modes are defined in RFC 3270:

• Uniform• Pipe• Short-PipeThe following illustration provides an overview of the different tunnel modes.

Figure 35 • Overview of Tunnel Modes

Note: The VLAN PCP shown in the overview is the S-tag PCP.

3.1.1 Uniform ModeIn uniform mode, any changes made to the TC value of the topmost label on a label stack are propagated both upward as new labels are added and downward as labels are removed. The idea here is that the network is a single DiffServ domain, so any changes made to the TC values on the MPLS packet in transit are supposed to be applied to all labels underneath the packet.

The rules for uniform mode are as follows:

• On popping labels, copy the TC upward.• On pushing labels, copy the removed TC downward. You use uniform mode if you want a change in TC somewhere in your MPLS network to affect how the frame is treated after it exits the MPLS portion of the network. In an MPLS-TP context, uniform mode

MPLS TC 2m1

MPLS TC 2m1

MPLS TC 2m1

MPLS TC 2m1

MPLS TC 2m1

MPLS TC 2m1

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2m1

VLAN PCP 2

MPLS TC 2m1

MPLS TC 2m1

MPLS TC 2m1

MPLS TC 2m1

MPLS LER MPLS Push MPLS Swap MPLS Pop MPLS LER

Processing direction

Tunnel Mode: Uniform

MPLS TC 4

MPLS TC 3

MPLS TC 4

MPLS TC 3 MPLS TC 3MPLS TC 3m

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 3m

VLAN PCP 2

MPLS TC 4

MPLS TC 5 MPLS TC 5m

MPLS TC 4


Tunnel Mode: Pipe

MPLS TC 4

MPLS TC 3

MPLS TC 2

MPLS TC 2 MPLS TC 3MPLS TC 3m

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

VLAN PCP 2

MPLS TC 4

MPLS TC 5 MPLS TC 5m

MPLS TC 4


Tunnel Mode: Short Pipe

mسindicates mapped or fixed

CoS based on MPLS TC3

CoS based on PCP2

CoS based on MPLS TC 2m1

Appendix


does not allow separation of Subscriber COS from the Service Provider network COS, and is not preferred.

The overview drawing shows complete processing with VLAN PCP value mapped to MPLS TC for both PW and LSP.

3.1.2 Pipe ModePipe mode is useful for service providers implementing their own QoS policy independent of their customer's QoS policy. The CoS of a frame is propagated into the PW label TC. Other labels are fixed. When a new label is pushed new TC is fixed. When labels are swapped, the inner label's TC values are kept; outer label's TC may be mapped.

At the LER, when removing the MPLS encapsulation, the CoS is determined by the PW label, and if mapped the CoS is reflected in the PCP.

3.1.3 Short-Pipe ModeShort-Pipe mode is just like Pipe mode, except at LER egress the CoS is based on the VLAN PCP.

3.2 OAM OverviewThe following tables lists the supported OAM functions.

Note: The service OAM (Y.1731) is supported simultaneously with MPLS OAM, except for EVC down MEP.

3.3 TroubleshootingMPLS-TP is error prone due to the manual configuration of each end of a connection and the intermediate hops. Therefore extra care must be taken when configuring MPLS.

Make use of the MPLS OAM functions and add OAM with cc enabled on each connection. Only when OAM is running the MPLS connection is functioning. The MPLS state up only indicates the MPLS connection has been configured, but the connection may not work.

If an MPLS connection is not functioning, then compare port counters with MPLS counters. Also, check MAC table. An MPLS packet correctly received will not be entered (learnt) in the MAC table. If an MPLS packet is not matching the MPLS link layer, the packet will be switched and learnt.

Table 1 • Supported OAM Functions

OAM FunctionG.8113.1 (Y.1731) Tunnel, PW, and MPLS-Link

G.8113.2 (BFD) Tunnel, PW, and MPLS-Link Comments

MEP • • Direction is down

CC • •

LB •

RT RT (Route Trace) similar to Y.1731 LT

AIS • For LSP clients

Lock • For LSP clients

TST •

TLV •

LM •

DM •

MIP Supported on LSP (LSR)

Appendix


Besides the show... commands there is also a debug command debug api mplscore ail which gives an overview of MPLS link layer configuration and label assignment. The following illustration shows how to execute the troubleshooting.

Figure 36 • Troubleshooting

Note: Debug commands may change between releases without notice.

debug api mplscore ailApplication Interface Layer===========================

MPLS----

L2 Entries In Use Idx Iprt Peer_MAC Self_MAC Tag VID PCP DEI LL-up LL-dn OAM User_segments 0 1 00:12:12:12:12:12 00:02:02:02:02:02 S 100 7 0 -1 0 N 0,1

1 3 00:21:21:21:21:21 00:14:14:14:14:14 S 100 7 0 -1 1 N 2,3

Segments In UseIdx Type E/L L-CoS TC-map Label Assign L2 XC Server PW CntrlWord OAMtype Alloc MLL MLBS VPr ES0 Encap ELen ESDX Clients

0 in E 0 T2Q/-1 6689/255/255 downst 0 0 -1 N - - N Y N -1 - - - - 41 out E 0 Q2T/-1 6692/ 1/ 16 downst 0 1 -1 N - - N - - - N -1 0 -1 5

2 in E 0 T2Q/-1 6689/255/255 downst 1 2 -1 N - MEP N Y Y 13 - - - - 63 out E 0 Q2T/-1 6692/ 1/ 16 downst 1 3 -1 N - - N - - - N -1 0 -1 7

4 in E 0 T2Q/-1 6693/255/255 downst -1 4 0 Y 0x00000000 - N N Y 14 - - - - -5 out E 0 Q2T/-1 6696/ 0/ 4 downst -1 5 1 Y 0x00000000 - N - - - N 1 30 -1 -

6 in E 0 T2Q/-1 6693/255/255 downst -1 6 2 Y 0x00000000 VCCV1 N N Y 15 - - - - - 7 out E 0 Q2T/-1 6696/ 0/ 4 downst -1 7 3 Y 0x00000000 - N - - - N 2 30 -1 -

XCs In Use Idx Type In-seg Out-seg TC-mode TTL-mode ISDX MC chain 0 LER 0 -1 Pipe Pipe -1 - 1 LER -1 1 Pipe Pipe -1 - 2 LER 2 -1 Pipe Pipe 7 - 3 LER -1 3 Pipe Pipe -1 - 4 LER 4 -1 Pipe Pipe 5 - 5 LER -1 5 Pipe Pipe -1 - 6 LER 6 -1 Pipe Pipe 6 - 7 LER -1 7 Pipe Pipe -1 –

ent-an1122-4.2 application note software configuration

Documents