Software Configuration for MPLS-TP - Microchip Technologyww1.microchip.com/downloads/en/Appnotes/VPPD-03907_AN.pdf · 2019-10-29 · Software Configuration for MPLS-TP 2 Configuration

Application Note ENT-AN1122

Software Configuration for MPLS-TP

This document describes how the CLI and web interfaces can be used to configure MPLS-TP inCEServices applications running on Serval-1 Carrier Ethernet switches. Descriptions used in thisdocument are based on the CEServices Software Development Kit (SDK) release 3.60beta.

Note: The examples documented use Up-MEP functionality and require the Serval-1 image with loopport.

Table of Contents

CLI ConventionsTerminal input/output is indicated as follows

# show versionMEMORY: Total=86382 KBytes, Free=70497 KBytes, Max=70496KBytesFLASH: 0x40000000-0x40ffffff, 64 x 0x40000 blocksMAC Address: 00-01-c1-00-ad-80Previous Restart: Cold...Configuration examples are shown using default values. To get all parameters use the command show …all-default. To reset counters use clear...

CLI Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Configuration Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

MPLS-TP Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20OAM Support in MPLS-TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21MPLS-TP Modes and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

July 2015 1

© 2015 Microsemi Corporation

Software Configuration for MPLS-TP Software Configuration for MPLS-TP

Configuration DescriptionsThe following illustration shows a simple network configuration based on three connected nodes. Thephysical connections between the nodes are 1 Gbps copper or optical (SFP). The two outer nodes arethe MPLS Label Edge Router (LER) nodes and the middle node is the MPLS Label Switch Router (LSR)node. Customer traffic is received and sent on the two UNI ports.

MPLS LER configuration with E-LINE (VPWS)To configure a tunnel LSP with a pseudowire (PW), first configure the MPLS link layer on the NNI port (4).

For the link layer, configure the destination MAC address as tx-mac and configure an rx-mac address tobe used as source MAC address.

Note: The rx-mac address should be configured to be equal to the switch MAC address if only one MPLSlink layer is defined on a port. The MPLS link layer MAC address can be configured different fromthe switch mac address, in this case make sure it is unique.

Then configure a tunnel LSP with in-label as received from the remote tunnel LSP and out-label asexpected by remote tunnel LSP. The tunnel LSP is connected to the MPLS link 4 and has TC fixed to 1.

Figure 1 • Network Configuration with All MEPs and MIPs

Figure 2 • MPLS-TP Links Configuration

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

22

Configuration DescriptionsConfiguration Descriptions

TTL is set to 16 but could be set down to 2 as only two nodes are used in this simple network. Tunnelmode is set to pipe.

Finally a pseudowire is created with a control word (0) and connected to the LSP. The VCCV-type is setto 1 to use control word without using GAL-normal label values are used for in and out labels. First labelis the in label and next label is the out label.

The following code shows the same configuration using the CLI.

! MPLS Link Layerinterface GigabitEthernet 1/4mpls tp link 4 tx-mac 00:21:21:21:21:21 rx-mac 00:14:14:14:14:14 s-tag100 pcp 7 dei 0! tunnel LSPinterface tunnel-tp 11 tunnel-mode pipein-label 6689out-label 6692 out-link 4 tc 1 ttl 16!Pseudo Wire mpls pw 11mpls label 6693 6696 ttl 4 control-word 0interface out-tunnel 11Now the MPLS PW can be connected to an Ethernet service (EVC). In this case an EPL EVC is usedtaking all traffic from the UNI (port 2) and send it out in PW 11.

Figure 3 • MSP-TP Tunnel Configuration

Figure 4 • MPLS Pseudo Wires Configuration

33


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


!E-line configevc 2 vid 22 ivid 22 interface GigabitEthernet 1/4 learning pw 11evc 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

MPLS Link, PW and LSP Status

The following code shows the same status using the CLI.

show mpls tp link 4MPLS-TP link 4: GigabitEthernet 1/4, tx_mac 00:21:21:21:21:21, rx_mac 00:14:14:14:14:14, S-tagged, VID 100, pcp 7, dei 0 src node_id 0.0.0.0, global_id 0dst node_id 0.0.0.0, global_id 0 if_num 0show mpls pw 11

Figure 5 • EVC Configuration

Figure 6 • MPLS Pseudo Wires Status

Figure 7 • MPLS-TP Tunnel Status

44


MPLS-TP PW 11: in_label 6693, out_label 6696, control-word 0tunnel-mode pipe, MPLS-TP tunnel 11, tc 0, ttl 4, vccv vccv1, OAMactive, state UPin_cos_map_id 0, out_cos_map_id 0, E-LSPshowinterface tunnel-tp 11MPLS-TP tunnel 11: 'tunnel 11', tunnel-mode pipe, OAM active, state UPsrc node_id 0.0.0.0, global_id 0dst node_id 0.0.0.0, global_id 0 tunnel_tp_num 0 in_label 6689, out_label 6692, MPLS-TP link 4,tc 1, ttl 16, in_cos_map_id 0, out_cos_map_id 0, E-LSPThe PW state UP means the PW has been configured in Serval with all parameters. This does not meanconnection to other end has been established.

Src and dest node ID are used by MPLS BFD OAM.

MPLS Link, PW and LSP Statistics

show mpls pw statistics 11MPLS-TP PW 11: in_label 6693, out_label 6696, control-word 0 Rx Green Frames: 56519 Tx Green Frames: 110572 Rx Yellow Frames: 0 Tx Yellow Frames: 0 Rx Red Frames: 0 Rx Discard Frames: 14 Tx Discard Frames: 0 Rx Green Bytes: 4140679 Tx Green Bytes: 7926782 Rx Yellow Bytes: 0 Tx Yellow Bytes: 0 Rx Red Bytes: 0 Rx Discard Bytes: 1128 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: 4181825 Tx Green Frames: 278944002 Rx Yellow Frames: 0 Tx Yellow Frames: 0 Rx Red Frames: 0 Rx Discard Frames: 17 Tx Discard Frames: 0 Rx Green Bytes: 339818693 Tx Green Bytes: 22312976079 Rx Yellow Bytes: 0 Tx Yellow Bytes: 0 Rx Red Bytes: 0 Rx Discard Bytes: 1501 Tx Discard Bytes: 0

Figure 8 • MPL Pseudo Wires Statistics

Figure 9 • MPLS-TP Tunnel Statistics

55


G.8113.1 MPLS-TP OAM (PTN/Y.1731 based) for Pseudowire and LSP MEGs

MPLS-TP OAM is configured in the same way as Ethernet service OAM using the MEP commands. Thefollowing configuration creates tunnel and PW OAM with CC rate of 1 frame per second and enablesdelay measurements and loss measurements.


! Tunnel OAMmep41 down domain tunnel-tp flow 11 level 0

Figure 10 • MEP Tunnel Configuration

Figure 11 • MEP PW Configuration

66


mep41 meg-id MEG_ID1 itumep41 mep-id 111mep41 peer-mep-id 112 mac 00-21-21-21-21-21mep41 cc 7mep41 ccm-tlvmep41 lm 0mep41 dm 0 interval 10 last-n 10! PW OAMmep51 down domain pw flow 11 level 7mep51 meg-id MEG_ID51 itumep51 mep-id 51mep51 peer-mep-id 52 mac 00-21-21-21-21-21mep51 cc 7mep51 ccm-tlvmep51 lm 0mep51 dm 0 interval 10 last-n 10!

Continuity Check (CC) StatusOnly the tunnel MEP is shown.

show mep 41 detailMEP 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 FalseMEP 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 0 00-14-14-14-14-Delay Measurement (DMM)

MEP Statusshow mep 41 cc detailMEP CC Configuration is:InstPrioRateTlv41 7 1s Tlv

Figure 12 • Continuity Check Status

77


Loss Measurement (LM)

sh mep 41 lm detailMEP LM state is: Inst Tx Rx Near Count Far Count Near Ratio Far Ratio 41 974 973 0 0 0 0MEP LM Configuration is: Inst Prio Cast Ended Rate Flr 41 0 Multi Single 1s 5

Delay Measurement (DM)Note: Delay measurements that have a negative delay will be counted as RxErr.

show mep dm 41MEP 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 valueOF : 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 usMEP DM binning state is: ins bin0 bin1 bin2 bin3 bin4 bin5 bin6 bin7 bin8 bin9Frame Delay

Figure 13 • Loss Measurement

Figure 14 • Delay Measurement

88


1-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

Loop Back (LB)With loop back it is possible to test connectivity to the MEP at the other end of of the tunnel and PW, andto the MIP in the LSR. When doing LB to an LSP MIP the MIP is determined by the TTL. TTL of 1 meansnext hop, for example.

(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

Test Generation (TST)Use the following command to enable test frame generation and reception.

!Test frame generation(config)# mep 41 tst tx!Test frame reception(config)# mep 41 tst rxTest frames are generated in software and it is not possible to set the rate. The reception of test frames isshown with:

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

Other OAM functionsAIS and Lock are not supported in this release. LT (Link trace) is not supported in G.8113.1.

Figure 15 • Loop Back

99


G.8113.2 MPLS-TP OAM (BFD based) for Pseudowire and LSP MEGsBFD based OAM is also configured using the MEP command. BFD OAM uses a destination and sourceIP address together with a tunnel-tp ID to verify correct connection. These parameters are configured onthe tunnel LSP.

The MEP is configured in the same way as for Y.1731 based OAM, but with BFD cc.

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

• Simple password

• MD5, or

• SHA1

mep bfd auth-key 0 simple-pwd key 000102030405060708090a0b0c0d0e0f mep bfd auth-key 1 md5 key 000102030405060708090a0b0c0d0e0fmep bfd auth-key 2 sha1 key 000102030405060708090a0b0c0d0e0f10111213mep 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 BFDcc configuration is coordinated to determine which one is used for bi-directional tunnels.An independent mode is supported, where two tunnels are required.

Status:

Figure 16 • MEP OAM Configuration

Figure 17 • MEP BFD Configuration

Figure 18 • MEP BFD Authentication Keys Configuration

1010


sh mep 1 bfdMEP 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 NONEMEP BFD remote state is: Inst State Diag Discriminator Min. Rx Flags 1 UP NONE 0x2db0d0a4 10000 us 0x00show mep 1MEP 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 FalseBFD False FalseFalse False

Y.1731 / 802.1ag Service OAM on Physical Port, Subscriber MIP, and EVC Up MEPFor completeness of OAM functionality, physical Port MEP, Subscriber MIP, and EVC Up MEPconfiguration is described in this section.

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

!Port MEP on NNI portmep os-tlv oui 0xC sub-type 0x1 value 0x2mep 4 down domain port level 0 interface GigabitEthernet 1/4 mep 4 mep-id 44mep 4 voemep 4 peer-mep-id 45 mac 00-01-C1-00-C3-E1 mep 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 down mep 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 interfaceGigabitEthernet 1/3 mep 32 vid 113!EVC Up-mep on NNI portmep 33 up domain evc flow 2 level 4 interface GigabitEthernet 1/3 mep 33 voemep 33 peer-mep-id 2 mac 00-01-C1-00-C4-13 mep 33 cc 6mep 33 ccm-tlv mep 33 lm 6mep 33 dm 6 interval 10 last-n 10

Link Trace (LT)With the preceding MIPs in the service provider network the subscriber can check the connectivity usinglink trace generated by the customer equipment.

(config)# mep 3 lt 6 mep-id 2 ttl 3show mep 3 ltMEP LT state is: Inst Transaction ID Ttl Mode Direction Forwarded relay Last MAC Next MAC 3 36 2 Mip Down Yes FDB 00-01-C1-00-71-43 00-01-C1-00-B6-D3 1 Mip Up Yes FDB 00-01-C1-00-B6-D3 00-01-C1-00-C4-13

1111


0 Mep Down No MAC 00-01-C1-00-C4-13 00-01-C1-00-72-03When the subscriber sends an LT message, first the subscriber MIP on the near UNI (down half MIP) willrespond and forward the LT to the remote end UNI where another subscriber MIP (up half MIP) willrespond, and finally the subscriber MEP at the customer equipment will respond. MAC addresses ofeach MIP/MEP are given.

MPLS LSR ConfigurationConfiguring label switch routing (LSR) functionality is done by configuring two LSPs, one in the forwarddirection and one in the reverse direction. As with the LER function, an MPLS link layer must be defined.

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

LSP Status

show mpls tp lspMPLS-TP LSP XC 1: 'lsp_xc 1', OAM active, state UPsrc node_id 0.0.0.0, global_id 0 tunnel_tp_num 0, lsp_num 0 dst node_id 0.0.0.0, global_id 0 tunnel_tp_num 0, lsp_num 0Forward in_label 6692, out_label 6692, in_cos_map_id 0, out_cos_map_id 0, E-LSP, MPLS-TP link 2, hqos_id **none**

Figure 19 • MPLS-TP Links Configuration

Figure 20 • MPLS TP LSP Configuration

Figure 21 • MPLS-TP LSP Status

1212


Reverse in_label 6689, out_label 6689, in_cos_map_id 0,out_cos_map_id 0, E-LSP, MPLS-TP link 1, hqos_id **none**

LSP MIPCreation of a MIP on an LSP is possible using the following commands.

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

Pseudowire StitchingIt is possible to connect two PWs together, known as Pseudowire Stitching. The two PWs are connectedtogether without analyzing the payload. OAM on these PWs are no possible.

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

QoSFixed QoS and Mapped QoS are the two available options.

Fixed QoS configuration is shown in MPLS LER Configuration with E-Line (VPWS) (see page ). Here TCis set to 1. For mapped QoS, a mapping table needs to be defined; eight mapping tables are available.

In the following configuration two mapping tables are defined.Mapping table 1 is used on egress to mapCoS into MPLS TC and mapping table 2 is used on ingress to map MPLS TC into CoS.

mpls tp cos-map 1ingress 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 0ingress tc 6 map-to cos 6 dp 0ingress 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

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

Figure 23 • MPLS-TP Tunnel Detailed Configuration

1313


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 2ingress 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 mapping mpls tp cos-map 1! interface tunnel-tp 11tunnel-mode pipein-label 6689out-label 6692 out-link 4 ttl 16 in-cos-map 2out-cos-map 1The default LSP type is E-LSP where the above QoS mapping is used directly. But also for L-LSPs it ispossible to map CoS into TC bits. The TC and TTL handling in an MPLS-TP network depends on thetunnel mode configured.

1414


HQoSServal-1 supports hierarchical QoS with egress shaping. HQoS is possible to use for PWs and LSPs.First create HQoS configuration on the interface. For more information about HQoS configuration, seeHQoS Configuration. Then connect the PW or LSP to the HQoS using the HQoS ID.

! PW with HQoSmpls pw 11mpls label 6693 6696 ttl 4 control-word 0vccv-type 1interface out-tunnel 11 hqos 11! LSR with HQoSmpls tp lsp 1forward-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

MPLS LER Configuration with E-LAN (VPLS)Configuration of an E-LAN EVC over MPLS-TP (VPLS) is done in the same way as for the E-LINE(VPWS), just with multiple PWs attached to the EVC. Network access ports are either Ethernet portsconnected via ECE (MEF UNI ports) or PWs connected to the EVC (IETF attachment circuits). NNI(network) ports that 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. Full VPLS functionality is possible,but requires separate ports for each PW, which does not scale, but make it possible to use Serval-1for VPLS testing.

The following is a configuration example 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 is a configuration example of VPLS with one UNI port and two NNI ports.

evc 2 vid 22 ivid 22 learning pw split-horizon 1,11

Figure 24 • MPLS Pseudo Wires Detailed Configuration

Figure 25 • MPLS-TP LSP Detailed Configuration

1515


evc ece 2 interface GigabitEthernet 1/3 outer-tag add pcp-mode fixedpcp 6 evc 2 cos 6

Linear Protection Switching between Pseudo Wires or between 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 LAPS (Linear Automatic Protection Switching)

6. Create EPS (Ethernet Protection Switching) instance with working and protecting PW/Tunnel andwith the MEPs

7. Connect the PW to an EVC

Note: Other protection mechanisms such as Spanning Tree and Link Aggregation do not work with linearprotection and should be disabled.

Linear protection is supported in the following five 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 SPME monitoring

• 1:1 Tunnel LSP group protection (active/active)

• 1:N Tunnel LSP group protection (active/standby)

The following illustration shows two sets of PWs, tunnel LSPs, and EPS instances.

Figure 26 • Protection Setup

PW 3TunnelLSP 3

E-LINE EVC XEndpoint UNI _1

E-LAN EVC YEndpoint UNI _1

PW 4TunnelLSP 4

PW 1TunnelLSP 1

Protect PWs 2 and 4

Working PWs 1 and 3

PW 2TunnelLSP 2

1 3

E-LAN EVC YEndpoint UNI _2

2 4

LSP 1

LSP 3

LSP 2

LSP 4

UN

I 1U

NI 2

NN

IN

NI

EVC Y MEP

EVC Y MEP

PWMEPs

LSPMEPs

Serval-1

EVC X MEP

1616


EVC Protection over MPLS using Pseudowire MonitoringThe following code shows the basic port and MPLS link layer configuration for two sets of PWs, tunnelLSPs, and EPS instances.NNI working is port 3 and protecting is port 4. UNI ports are 1 and 2.

interface GigabitEthernet 1/1 switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybridno lldp transmit no spanning-tree evc key normal!interface GigabitEthernet 1/2 switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybridno lldp transmit no spanning-tree evc key normal!interface GigabitEthernet 1/3 switchport hybrid native vlan 2 switchport hybrid allowed vlan none switchport mode hybridno lldp transmit no spanning-tree evc key normalmpls 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 hybridno lldp transmit no spanning-tree evc key normalmpls 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:44The following code shows step 1 and 2.

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

1717


tunnel-mode short-pipempls label 322 324 tc 7 ttl 200control-word 0 vccv-type 1interface out-tunnel 4!The following code shows step 3, 4, 5, and 6 for the configuration of MEPs and EPS instances, assumingthe tunnel LSPs and PWs have already been created.

mep os-tlv oui 0xC sub-type 0x1 value 0x2 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-33 mep 1 cc 0mep 2 down domain pw flow 2 level 0mep 2 meg-id MEG_ID1 itu mep 2 mep-id 2mep 2 peer-mep-id 4 mac 00-44-44-44-44-44 mep 2 cc 0mep 2 aps 0 lapsmep 3 down domain pw flow 3 level 0 mep 3 meg-id MEG_ID1 itumep 3 mep-id 3mep 3 peer-mep-id 1 mep 3 cc 0mep 4 down domain pw flow 4 level 0 mep 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 pw architecture 1for1 work-flow 1 protect-flow 2 eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 2 domain pw architecture 1for1 work-flow 3 protect-flow 4 eps 2 mep-work 3 mep-protect 4 mep-aps 4

The following code shows step 7, the connection of EVC. The EVCs are created on working port andworking PW.

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

1:1 EVC Protection over MPLS using Tunnel LSP Monitoring (Active/ Standby)Protection based on tunnel LSP MEPs follows the same configuration steps, except the MEPs used arenow the tunnel LSP MEPs and 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.Also a protected tunnel LSP can carry a number of LSPs.

mep os-tlv oui 0xC sub-type 0x1 value 0x2 mep 1 down domain tunnel-tp flow 1 level 0 mep 1 meg-id MEG_ID1 itumep 1 peer-mep-id 3 mac 00-33-33-33-33-33 mep 1 cc 0mep 2 down domain tunnel-tp flow 2 level 0 mep 2 meg-id MEG_ID1 itumep 2 mep-id 2mep 2 peer-mep-id 4 mac 00-44-44-44-44-44 mep 2 cc 0mep 2 aps 0 lapsmep 3 down domain tunnel-tp flow 3 level 0 mep 3 meg-id MEG_ID1 itumep 3 mep-id 3mep 3 peer-mep-id 1 mep 3 cc 0mep 4 down domain tunnel-tp flow 4 level 0 mep 4 meg-id MEG_ID1 itu

Figure 27 • Ethernet Protection Switching

1818


mep 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 2 eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 2 domain tunnel-tp architecture 1for1 work-flow 3 protect-flow 4 eps 2 mep-work 3 mep-protect 4 mep-aps 4

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 theMPLS label stack consists of three labels.

mpls tp global-id 0router-id 0.0.0.0icc-carrier-code NONE!interface tunnel-tp 1 tunnel-mode short-pipe in-label 563out-label 561 out-tunnel 11 tc 5 ttl 150tp destination 1.2.3.4 tunnel-tp 234 spme lsp 22!interface tunnel-tp 2 tunnel-mode short-pipe in-label 579out-label 577 out-tunnel 12 tc 5 ttl 150tp destination 1.2.3.4 tunnel-tp 345 spme lsp 33!interface tunnel-tp 3 tunnel-mode short-pipe in-label 561out-label 563 out-tunnel 13 tc 5 ttl 150tp destination 1.2.3.4 tunnel-tp 345 spme lsp 44!interface tunnel-tp 4 tunnel-mode short-pipe in-label 577out-label 579 out-tunnel 14 tc 5 ttl 150tp destination 1.2.3.4 tunnel-tp 345 spme lsp 55!interface tunnel-tp 11 tunnel-mode short-pipe in-label 307out-label 305 out-link 1 tc 5 ttl 150!interface tunnel-tp 12 tunnel-mode short-pipe in-label 323out-label 321 out-link 2 tc 5 ttl 150!interface tunnel-tp 13 tunnel-mode short-pipe in-label 305out-label 307 out-link 3 tc 5 ttl 150!interface tunnel-tp 14 tunnel-mode short-pipe in-label 321out-label 323 out-link 4 tc 5 ttl 150!mpls pw 1tunnel-mode short-pipempls label 308 306 tc 7 ttl 200 control-word 0vccv-type 1interface out-tunnel 1!mpls pw 3tunnel-mode short-pipempls label 306 308 tc 7 ttl 200 control-word 0vccv-type 1interface out-tunnel 3!mep os-tlv oui 0xC sub-type 0x1 value 0x2 mep 1 down domain tunnel-tp flow 1 level 0 mep 1 meg-id MEG_ID1 itumep 1 peer-mep-id 3 mep 1 cc 0mep 2 down domain tunnel-tp flow 2 level 0 mep 2 meg-id MEG_ID1 itu

1919


mep 2 mep-id 2mep 2 peer-mep-id 4 mep 2 cc 0mep 2 aps 0 lapsmep 3 down domain tunnel-tp flow 3 level 0 mep 3 meg-id MEG_ID1 itumep 3 mep-id 3mep 3 peer-mep-id 1 mep 3 cc 0mep 4 down domain tunnel-tp flow 4 level 0 mep 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 2 eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 2 domain tunnel-tp architecture 1for1 work-flow 3 protect-flow 4 eps 2 mep-work 3 mep-protect 4 mep-aps 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 theWorking role in one EPS instance and the protect role in the other EPS instance.

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 thesame protecting tunnel LSP.

P2M (Point-to-Multipoint)P2M (Point-to-Multipoint) is not supported.

MPLS-TP TroubleshootingThe manual configuration of each end of a connection and the intermediate hops make MPLS-TP error-prone. Use the MPLS OAM functions and add OAM with cc enabled on each connection. Only whenOAM is running the MPLS connection is functioning. The MPLS state up only indicates the MPLSconnection has been configured, but the connection may not work.

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

In addition to the show commands the debug command, debug api mplscore ail, displays an overview ofMPLS link layer configuration and label assignment.

debug api mplscore ailApplication Interface Layer=========================== MPLS----L2 Entries In UseIdx Iprt Peer_MACSelf_MACTagVID PCP DEI LL-upLL-dn OAM User_segments0 1 00:12:12:12:12:12 00:02:02:02:02:02S10070-10 N 0,11 3 00:21:21:21:21:21 00:14:14:14:14:14S10070-11 N 2,3Segments In UseIdx Type E/L L-CoS TC-mapLabel AssignL2XC Server PW CntrlWord OAMtype Alloc MLL MLBS VPr ES0 Encap ELen ESDX Clients0 in E 0 T2Q/-16689/255/255 downst00-1N- - N Y N -1 - - - - 41 outE 0 Q2T/-16692/1/ 16 downst01-1N- - N - - - N -1 0 -1 52 in E 0 T2Q/-16689/255/255 downst12-1N- MEPN Y Y 13 - - - - 63 outE 0 Q2T/-16692/1/ 16 downst13-1N

2020

OAM Support in MPLS-TPOAM Support in MPLS-TP

- - N - - - N -1 0 -1 74 in E 0 T2Q/-16693/255/255 downst-140Y 0x00000000-NN Y 14 - - - - -5 outE 0 Q2T/-16696/0/4 downst-151Y 0x00000000-N- - - N 1 30 -1 -6 in E 0 T2Q/-16693/255/255 downst-162Y 0x00000000VCCV1NNY15- - - - -7 outE 0 Q2T/-16696/0/4 downst-173Y 0x00000000-N- - - N 2 30 -1 - XCs In UseIdxTypeIn-segOut-segTC-modeTTL-modeISDXMCchain0 LER 0 -1 PipePipe -1-1 LER -1 1 PipePipe -1-2 LER 2 -1 PipePipe 7-3 LER -1 3 PipePipe -1-4 LER 4 -1 PipePipe 5-5 LER -1 5 PipePipe -1-6 LER 6 -1 PipePipe 6-7 LER -1 7 PipePipe -1-

OAM Support in MPLS-TPThe following table shows the supported OAM functions.

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

MPLS-TP Modes and Terminology

Tunnel ModesA set of behaviors defined to provide mechanisms to control TC (EXP) values in various scenarios.These mechanisms are called tunnel modes. The following tunnel modes are defined in RFC 3270.

• Uniform

• Pipe

• Short-Pipe

Table 1 • Supported OAM Functions

OAM Function

G.8113.1 (Y.1731) Tunnel, PW, MPLS-Link

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

MEP • • Direction is down

CC • •

LB • -

RT N/A - Route Trace similar to Y.1731 LT

AIS - -

Lock - -

TST • N/A

TLV • N/A

LM • -

DM • -

MIP N/A N/A Supported on LSP (LSR)

2121


The following figures shows the complete processing with VLAN PCP values mapped to MPLS TC forboth PW and LSP.

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

Uniform ModeIn uniform mode, any changes made to the TC value of the topmost label on a label stack are propagatedboth upward as new labels are added and downward as labels are removed. The idea here is that thenetwork is a single DiffServ domain, so any changes made to the TC values on the MPLS packet intransit 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.

Uniform mode is used to change the TC somewhere in the MPLS network to affect how the frame istreated after it exits the MPLS portion of the network. In an MPLS-TP context, uniform mode does notallow separation of subscriber COS from the servicepProvider network COS, and is not preferred.

Pipe ModePipe mode is useful for service providers implementing their own QoS policy independent of theircustomer'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 arekept; outer label's TC may be mapped.

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

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

Figure 28 • Tunnel Mode Overview

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 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 2

MPLS TC 4

MPLS TC 5MPLS 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

MPLS TC 4

MPLS TC 5MPLS TC

5m

MPLS TC 4


Tunnel Mode: Short Pipe

”m” indicates mapped or fixed

CoS base

CoS

CoS based

2222

VPPD-03907. 1.1. July 2015

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

Power Matters.TM

Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductorand system solutions for communications, defense & security, aerospace and industrialmarkets. Products include high-performance and radiation-hardened analog mixed-signalintegrated circuits, FPGAs, SoCs and ASICs; power management products; timing andsynchronization devices and precise time solutions, setting the world's standard for time; voiceprocessing devices; RF solutions; discrete components; security technologies and scalableanti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well ascustom design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif., andhas approximately 3,600 employees globally. Learn more at www.microsemi.com.

Microsemi Corporate HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USA

Within the USA: +1 (800) 713-4113 Outside the USA: +1 (949) 380-6100Sales: +1 (949) 380-6136Fax: +1 (949) 215-4996E-mail: [email protected]

© 2015 Microsemi Corporation. Allrights reserved. Microsemi and theMicrosemi logo are trademarks ofMicrosemi Corporation. All othertrademarks and service marks are theproperty of their respective owners.

mailto:[email protected]

www.microsemi.com

Documents

Software Configuration for MPLS-TP - Microchip Technologyww1.microchip.com/downloads/en/Appnotes/VPPD-03907_AN.pdf · 2019-10-29 · Software Configuration for MPLS-TP 2 Configuration