Huawei MPLS-TP OAM

HUAWEI ME60 Multiservice Control Gateway
Feature Description - Network Reliability 4 MPLS-TP OAM
4 MPLS-TP OAM
About This Chapter
4.1 Overview of MPLS-TP OAM

4.2 Understanding MPLS-TP OAM
4.3 Application Scenarios for MPLS-TP OAM
4.4 Terminology for MPLS-TP OAM
4.1 Overview of MPLS-TP OAM

Definition
Multiprotocol Label Switching Protocol Transport Profile (MPLS-TP) is a transport technique
that integrates MPLS packet switching with traditional transport network features. MPLS-TP
networks are poised to replace traditional transport networks in the future. MPLS-TP
Operation, Administration, and Maintenance (MPLS-TP OAM) works on the MPLS-TP client
layer. It can effectively detect, identify, and locate faults in the client layer and quickly switch
traffic when links or nodes become defective. OAM is an important part of any plan to reduce
network maintenance expenditures.
Purpose
Both networks and services are part of an ongoing process of transformation and integration.
New services like triple play services, Next Generation Network (NGN) services, carrier
Ethernet services, and Fiber-to-the-x (FTTx) services are constantly emerging from this
process. Such services demand more investment and have higher OAM costs. They require
state of the art QoS, full service access, and high levels of expansibility, reliability, and
manageability of transport networks. Traditional transport network technologies such as
Multi-Service Transfer Platform (MSTP), Synchronous Digital Hierarchy (SDH), or
Wavelength Division Multiplexing (WDM) cannot meet these requirements because they lack
a control plane. Unlike traditional technologies, MPLS-TP does meet these requirements
because it can be used on next-generation transport networks that can process data packets, as
well as on traditional transport networks.
Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 61

Because traditional transport networks or Optical Transport Node (OTN) networks have high
reliability and maintenance benchmarks, MPLS-TP must provide powerful OAM capabilities.
MPLS-TP OAM provides the following functions:
l Fault management
l Performance monitoring
l Triggering protection switching
Benefits
l MPLS-TP OAM can rapidly detect link faults or monitor the connectivity of links, which
helps measure network performance and minimizes OPEX.
l If a link fault occurs, MPLS-TP OAM rapidly switches traffic to the standby link to
restore services, which shortens the defect duration and improves network reliability.
MPLS-TP OAM Components

MPLS-TP OAM functions are implemented by maintenance entities (MEs). An ME consists
of a pair of maintenance entity group end points (MEPs) located at two ends of a link and a
group of maintenance entity group intermediate points (MIPs) between them.
MPLS-TP OAM components are described as follows:
l ME
An ME maintains a relationship between two MEPs. On a bidirectional label switched
path (LSP) that has two MEs, MPLS-TP OAM detection can be performed on the MEs
without affecting each other. One ME can be nested within another ME but cannot
overlap with another ME.
ME1 and ME2 in Figure 4-1 are used as an example:
– ME1 consists of two MEPs only.
– ME2 consists of two MEPs and two MIPs.
Figure 4-1 ME deployment on a point-to-point bidirectional LSP
Ingress LER Transit LER Transit LER Egress LER
ME1
ME2
LSP
ME
l MEG
A maintenance entity group (MEG) comprises one or more MEs that are created for a
transport link. If the transport link is a point-to-point bidirectional path, such as a
bidirectional co-routed LSP or pseudo wire (PW), a MEG comprises only one ME.

l MEP
A MEP is the source or sink node in a MEG. Figure 4-2 shows ME node deployment.
Figure 4-2 ME node deployment
– For a bidirectional LSP, only the ingress label edge router (LER) and egress LER
can function as MEPs, as shown in Figure 4-2.
– For a PW, only user-end provider edges (UPEs) can function as MEPs.
MEPs trigger and control MPLS-TP OAM operations. OAM packets can be generated or
terminated on MEPs.
Fault Management
Table 4-1 lists the MPLS-TP OAM fault management functions supported by the ME60.
Table 4-1 MPLS-TP OAM fault management functions
Function Description
Continuity check Checks link connectivity periodically.

(CC)
Connectivity Detects forwarding faults continuously.

verification (CV)
Loopback (LB) Performs loopback.
Remote defect Notifies remote defects.

indication (RDI)
Performance Monitoring
Table 4-2 lists the MPLS-TP OAM performance monitoring functions supported by the
ME60.

Table 4-2 MPLS-TP OAM performance monitoring functions

Function Description
Loss measurement Collects statistics about lost frames. LM includes the following
(LM) functions:
l Single-ended frame loss measurement
l Dual-ended frame loss measurement
Delay measurement Collects statistics about delays and delay variations (jitter). DM
(DM) includes the following functions:
l One-way frame delay measurement
l Two-way frame delay measurement
4.2 Understanding MPLS-TP OAM
4.2.1 Basic Concepts

An MPLS-TP network consists of the section, LSP, and PW layers in bottom-up order. A
lower layer is a server layer, and an upper layer is a client layer. For example, the section
layer is the LSP layer's server layer, and the LSP layer is the section layer's client layer.
On the MPLS-TP network shown in Figure 4-3, MPLS-TP OAM detects and locates faults in
the section, LSP, and PW layers. Table 4-3 describes MPLS-TP OAM components.
Figure 4-3 MPLS-TP OAM application
LSR A LSR B LSR C LSR D LSR F LSR G RNC
LSR E
Node B
Section
layer
LSP
layer
PW layer
Section
OAM
LSP OAM
PW OAM
MEG End Point
MEG Intermediate Point

Table 4-3 MPLS-TP OAM components

Name Description Example
Maintenance entity (ME) All MPLS-TP OAM l Section layer:

functions are performed on Each pair of adjacent
MEs. Each ME consists of LSRs forms an ME.
two maintenance entity l LSP layer:
group end points (MEPs) LSRs A, B, C, and D
and maintenance entity form an ME.
group intermediate points
(MIPs) on the link between LSRs D and E form an
the two MEPs. ME.
LSRs E, F, and G form
an ME.
l PW layer:
LSRs A, D, E, and G
form an ME.
Maintenance entity group A MEG is comprised of one l Section layer:

(MEG) or more MEs that are Each ME forms a MEG.
created for a transport link. l LSP layer:
MEGs for various services Each ME forms a MEG.
contain different MEs:
l PW layer:
l A MEG for a P2P Each ME forms a MEG.
unidirectional path
NOTE
contains only one ME. If two tunnels in opposite
l A MEG for a P2P directions between LSR A and
bidirectional path LSR D are established, a
contains two MEs. A single MEG consisting of two
MEs is established.
MEG for P2P
bidirectional co-routed
path contains a single
ME.
l A MEG for a P2MP
unidirectional path
contains MEs destined
for leaf nodes.

Name Description Example
MEG end point (MEP) A MEP is the source or sink l Section layer: Each LSR
node in a MEG. can function as a MEP.
Each LSR functions as
an LSR.
l LSP layer: Only an LER
can function as a MEP.
LSRs A, D, E, and G are
LERs functioning as
MEPs.
l PW layer: Only PW
terminating provider
edge (T-PE) LSRs can
function as MEPs.
LSRs A and G are T-PEs
functioning as MEPs.
MEG intermediate point Intermediate nodes between l Section layer:

(MIP) two MEPs on both ends of a No MIPs.
MEG. MIPs only respond to l LSP layer:
OAM packets sent by MEPs LSRs B, C, and F
and do not take the initiative function as MIPs.
in OAM packet exchanges.
l PW layer:
LSRs D and E function
as MIPs.
Usage Scenario
MPLS-TP OAM monitors the following types of links:
l Static bidirectional co-routed CR-LSPs
l Static VLL-PWs,VPLS-PWs
4.2.2 Continuity Check and Connectivity Verification

Continuity check (CC) and connectivity verification (CV) are both MPLS-TP functions. CC is
used to check loss of continuity defeat(dLOC) between two MEPs in a MEG. CV monitors
connectivity between two MEPs within one MEG or in different MEGs.
CC
CC is a proactive OAM operation. It detects LOC faults between any two MEPs in a MEG. A
MEP sends CC messages (CCMs) to a remote RMEP at specified intervals. If the RMEP does
not receive a CCM for a period 3.5 times provided that; if the specified interval, it considers
the connection between the two MEPs faulty. This causes the RMEP to report an alarm and
enter the Down state, and the RMEP triggers automatic protection switching (APS) on both
MEPs. After receiving a CCM from the MEP, the RMEP will clear the alarm and exit the
Down state.

CV
CV is also a proactive OAM operation. It enables a MEP to report alarms when unexpected or
error packets are received. For example, if a CV-enabled MEP receives a packet from an LSP
and finds that this packet has been transmitted in error along an LSP, the MEP will report an
alarm indicating a forwarding error.
4.2.3 Packet Loss Measurement

Packet loss measurement (LM), a performance monitoring function provided by MPLS-TP, is
implemented on the two ends of a PW, LSP, or MPLS section to collect statistics about
dropped packets. Packet loss measurement results contain near- and far-end packet loss
values:
l Near-end packet loss value: the number of dropped packets expected to arrive at the local
MEP.
l Far-end packet loss value: the number of dropped packets the local MEP has sent.
To collect packet loss statistics for both incoming and outgoing packets, each MEP must have
both of the following counters enabled:
l TxFCl: records the number of packets sent to the RMEP.
l RxFCl: records the number of packets received by the local MEP.
Packet loss measurement can be performed in either single- or dual-ended mode. Table 4-4
describes the single- and dual-ended packet loss measurement.
Table 4-4 Packet loss measurement functions

Function Description Usage Scenario
Dual-ended Collects packet loss Dual-ended packet loss measurement provides

packet loss statistics to assess the more accurate results than the single-ended
measurement quality of the link method. The interval between dual-ended
between two MEPs that packet loss measurements varies with the
have connectivity fault interval between CCM transmissions. The
management (CFM) CCM transmission interval is shorter than the
continuity check (CC) interval between LMM transmissions.
enabled. Therefore, the dual-ended method allows for a
shorter measurement interval than the single-
ended method.
Single-ended Collects packet loss Sending CCMs imposes a heavier burden on

packet loss statistics to assess the the network than sending LMMs and LMRs.
measurement quality of the link To minimize the burden, single-ended packet
between two MEPs. loss measurement can be used.
This method is
independent of CC.
Dual-ended Packet Loss Measurement

Figure 4-4 illustrates proactive dual-ended packet loss measurement. Dual-ended packet loss
measurement can only be performed in proactive mode. Two MEPs on both ends of a link
periodically exchange CCMs carrying the following information:

l TxFCf: the local TxFCl value recorded when the local MEP sent a CCM.
l RxFCb: the local RxFCl value recorded when the local MEP received a CCM.
l TxFCb: the TxFCf value carried in a received CCM. This TxFCb value is the local
TxFCl when the local MEP receives a CCM.
Figure 4-4 Proactive dual-ended packet loss measurement
CE1 PE1 PE2 CE2
MPLS-TP
Dual-end LM CCM TxFCf RxFCb TxFCb
MEP
After receiving CCMs carrying packet count information, both MEPs use the following
formulas to measure near- and far-end packet loss values:
Near-end packet loss value = |TxFCf[tc] - TxFCb[tp]| - |RxFCl[tc] - RxFCl[tp]|
Far-end packet loss value = |TxFCb[tc] - TxFCb[tp]| - |RxFCb[tc] - RxFCb[tp]|
l TxFCf[tc], RxFCb[tc], and TxFCb[tc] are the TxFCf, RxFCb, and TxFCb values,
respectively, which are carried in the most recently received CCM. RxFCl[tc] is the local
RxFCl value recorded when the local MEP received the CCM.
l TxFCf[tp], RxFCb[tp], and TxFCb[tp] are the TxFCf, RxFCb, and TxFCb values,
respectively, which are carried in the previously received CCM. RxFCl[tp] is the local
RxFCl value recorded when the local MEP received the previous CCM.
l tc is the time a current CCM was received.
l tp is the time the previous CCM was received.
Single-ended Packet Loss Measurement

Single-ended packet loss measurement is performed in either proactive or on-demand mode.
In proactive mode, a local MEP periodically sends loss measurement messages (LMMs) to an
RMEP carrying the following information:
l TxFCl: the local TxFCl value recorded when the LMM was sent.
After receiving an LMM, the RMEP responds to the local MEP with loss measurement replies
(LMRs) carrying the following information:
l TxFCf: equal to the TxFCf value carried in the LMM.
l RxFCf: the local RxFCl value recorded when the LMM was received.
l TxFCb: the local TxFCl value recorded when the LMR was sent.
Figure 4-5 illustrates proactive single-end packet loss measurement.

Figure 4-5 Proactive single-ended packet loss measurement
CE1 PE1 PE2 CE2
MPLS-TP
LMM TxFCf
Single-end LM
LMR TxFCf RxFCb TxFCb
MEP
After receiving an LMR, the local MEP uses the following formulas to calculate near- and far-
end packet loss values:
Near-end packet loss value = |TxFCb[tc] - TxFCb[tp]| - |RxFCl[tc] - RxFCl[tp]|
Far-end packet loss value = |TxFCf[tc] - TxFCf[tp]| - |RxFCf[tc] - RxFCf[tp]|
l TxFCf[tc], RxFCf[tc], and TxFCb[tc] are the TxFCf, RxFCf, and TxFCb values,
respectively, which are carried in the most recently received LMR. RxFCl[tc] is the local
RxFCl value recorded when the most recent LMR arrives at the local MEP.
l TxFCf[tp], RxFCf[tp], and TxFCb[tp] are the TxFCf, RxFCf, and TxFCb values,
respectively, which are carried in the previously received LMR. RxFCl[tp] is the local
RxFCl value recorded when the previous LMR arrived at the local MEP.
l tc is the time a current LMR was received.
l tp is the time the previous LMR was received.
4.2.4 Frame Delay Measurement

Frame delay measurement (DM), a performance monitoring function provided by MPLS-TP,
calculates the delay time on links. Frame delay measurement is performed in either proactive
or on-demand mode. The on-demand mode is used by default. Delay information can be used
to calculate the delay variation.
The link delay time can be measured using either one- or two-way frame delay measurement.
Table 4-5 describes these frame delay measurement functions.
Table 4-5 Frame delay measurement functions
One-way Measures the network delay time One-way frame delay measurement
frame delay on a unidirectional link between can be used only on a
measurement MEPs. unidirectional link. A MEP and its
RMEP on both ends of the link
must have synchronous time.

Two-way Measures the network delay time Two-way frame delay measurement
frame delay on a bidirectional link between can be used on a bidirectional link
measurement MEPs. between a local MEP and its
RMEP. The local MEP does not
need to synchronize its time with
its RMEP.
One-Way Frame Delay Measurement

Figure 4-6 illustrates one-way frame delay measurement. A local MEP periodically sends its
RMEP one-way delay measurement (1DM) messages carrying TxTimeStampf (the time when
a 1DM was sent).
Figure 4-6 One-way frame delay measurement
CE1 PE1 PE2 CE2
MPLS-TP
One-way DM 1DM TxTimeStampf
MEP
After the RMEP receives a 1DM, it subtracts the TxTimeStampf value from the RxTimef
value to calculate the delay time:
Frame delay time = RxTimef - TxTimeStampf
The frame delay value can be used to measure the delay variation that is the absolute
difference between two delay time values.
One-way frame delay measurement can only be performed when the two MEPs on both ends
of a link have synchronous time. If these MEPs have asynchronous time, they can only
measure the delay variation.
Two-Way Frame Delay Measurement

Two-way frame delay measurement is performed by E2E MEPs. A MEP periodically sends a
DMM carrying TxTimeStampf (the time when the DMM was sent). After receiving the
DMM, the RMEP responds with a delay measurement reply (DMR). This message carries
RxTimeStampf (the time when the DMM was received) and TxTimeStampb (the time when

the DMR was sent). The value in every field of the DMM is copied exactly to the DMR, with
the exception that the source and destination MAC addresses are interchanged.
Figure 4-7 Two-way frame delay measurement
CE1 PE1 PE2 CE2
MPLS-TP
DMM TxTimeStampf
Two-way DM
DMR TxTimeStampb
MEP
Upon receipt of the DMR, the local MEP calculates the two-way frame delay time using the
following formula:
Frame delay = RxTimeb (the time the DMR was received) - TxTimeStampf
To obtain a more accurate result, RxTimeStampf and TxTimeStampb are used.

RxTimeStampf indicates the time a DMM is received, and TxTimeStampb indicates the time
a DMR is sent. After the local MEP receives the DMR, it calculates the frame delay time
using the following formula:
Frame delay = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)
Two-way frame delay measurement supports both delay and delay variation measurement
even if these MEPs do not have synchronous time. The frame delay time is the round-trip
delay time. If both MEPs have synchronous time, the round-trip delay time can be calculated
by combining the two delay values using the following formulas:
l MEP-to-RMEP delay time = RxTimeStampf - TxTimeStampf
l RMEP-to-MEP delay time = RxTimeb - TxTimeStampb
4.2.5 Remote Defect Indication

Remote defect indication (RDI) enables a maintenance entity group end point (MEP) to send
continuity check messages (CCMs), each carrying an RDI flag, to notify a remote MEP
(RMEP) of faults.
The RDI implementation is as follows:
l After a local MEP detects a link fault using the continuity check (CC) function, the local
MEP sets the RDI flag to 1 in CCMs and sends the CCMs along a reverse path to notify
its RMEP of the fault.
l After the fault is rectified, the local MEP sets the RDI flag to 0 in CCMs and sends them
to inform the RMEP that the fault is rectified.

NOTE
l The RDI function is associated with the proactive continuity check function and takes effect only after the
continuity check function is enabled.
l The RDI function applies only to bidirectional links. In the case of a unidirectional LSP, before RDI can
be used, a reverse path must be bound to the LSP.
4.2.6 Loopback
Background
On a multiprotocol label switching transport profile (MPLS-TP) network, a virtual circuit
may traverse muptiple exchanging devices (nodes), including maintenance association end
points (MEPs) and maintenance association intermediate points (MIPs). Any faulty node or
link fault in a virtual circuit may lead to the unavailability of the entire virtual circuit.
Moreover, the fault cannot be located. Loopback (LB) can be configured on a source device
(MEP) to detect or locate faults in links between the MEP and a MIP or between MEPs.
Related Concepts
LB and continuity check (CC) are both connectivity monitoring tools on an MPLS-TP
network. Table 4-6 describes differentces between CC and LB.
Table 4-6 Differences among CC and LB

CC CC is a proactive OAM To only monitor the

operation. It detects LOC connectivity of a link
faults between any two between two MEPs or
MEPs in a MEG. associate APS, choose CC.
LB LB is an on-demand OAM To monitor the bidirectional

operation. It monitors the connectivity of a link
connectivity of bidirectional between a MEP and a MIP
links between a MEP and a or a link between two MEPs
MIP and between MEPs. and not to associate APS,
choose LB.
Implementation
The loopback function monitors the connectivity of bidirectional links between a MEP and a
MIP and between MEPs.
The loopback test process is as follows:

1. The source MEP sends a loopback message (LBM) to a destination. If a MIP is used as
the destination, the TTL in the LBM must be equal to the number of hops from the
source to the destination. LBM checks whether the target MIP ID carried by itself and
the MIP ID are the same. If a MEP is used as the destination, the TTL must be greater
than or equal to the number of hops to the destination. The TTL setting prevents the
LBM from being discarded before reaching the destination.

2. After the destination receives the LBM, it checks whether the target MIP ID or MEP ID
matches the local MIP ID or MEP ID. If they do not match, the destination discards the
LBM. If they match, the destination responds with a loopback reply (LBR).
3. If the source MEP receives the LBR within a specified period of time, it considers the
destination reachable and the loopback test successful. If the source MEP does not
receive the LBR after the specified period of time elapses, it records a loopback test
timeout and log information that is used to analyze the connectivity failure.
Figure 4-8 Loopback test
LSR A LSR B LSR C LSR D
LBM
LBR
MEP
MIP
Figure 4-8 illustrates a loopback test. LSRA initiates a loopback test to LSRC on an LSP. The
loopback test process is as follows:
1. LSRA sends LSRC an LBM carrying a specified TTL and a MIP ID. LSRB
transparently transmits the LBM to LSRC.
2. Upon receipt, LSRC determines that the TTL carried in the LBM times out and checks
whether the target MIP ID carried in the LBM matches the local MIP ID. If they do not
match, LSRC discards the LBM. If they match, LSRC responds with an LBR.
3. If LSRA receives the LBR within a specified period of time, it considers LSRC
reachable. If LSRA fails to receive the LBR after a specified period of time elapses,
LSRA considers LSRC unreachable and records log information that is used to analyze
the connectivity failure.
4.3 Application Scenarios for MPLS-TP OAM
4.3.1 Application of MPLS-TP OAM in the IP RAN Layer 2 to

Edge Scenario
MPLS-TP OAM is deployed on PEs to maintain and operate MPLS networks. Working at the
MPLS client and server layers, MPLS-TP OAM can effectively detect, identify, and locate
client layer faults and quickly switch traffic if links or nodes become faulty, reducing network
maintenance cost.

Figure 4-9 IP RAN over MPLS-TP in the Layer 2 to edge scenario

BTS/NodeB
FE/GE
MPLS-TP
PE1
GE
IMA E1 STM-1
PE2 PE4 RNC/BSC

BTS/NodeB
PE3
FE/GE
BTS/NodeB
TE Tunnel
In Figure 4-9, in Layer 2 to edge scenario on an IP RAN, mature PWE3 techniques are used
to carry services. The process of transmitting services between a BST/NodeB and a
RNC/BSC is as follows:
l The BTS, NodeB, BSC, and RNC can be directly connected to an MPLS-TP network.
l A TE tunnel between PE1 and PE4 is established. PWs are established over the TE
tunnel to transmit various services.
l MPLS-TP OAM is enabled on PE1 and PE4 OAM parameters are configured on PE1
and PE4 on both ends of a PW. These PEs are enabled to send and receive OAM
detection packets, which allows OAM to monitor the PW between PE1 and PE4. OAM
can obtain basic PW information. If OAM detects a default, PE4 sends a RDI packet to
PE1 over a reverse tunnel. PEs notify the user-side BTS, NodeB, RNC, and BSC of fault
information so that the user-side devices can use the information to maintain networks.
4.3.2 Application of MPLS-TP OAM in VPLS Networking
Service Overview
The operation and maintenance of virtual leased line (VLL) and virtual private LAN service
(VPLS) services require an operation, administration and maintenance (OAM) mechanism.
MultiProtocol Label Switching Transport Profile (MPLS-TP) OAM provides a mechanism to
rapidly detect and locate faults, which facilitates network operation and maintenance and
reduces the network maintenance costs.
Networking Description
As shown in Figure 4-10, a user-end provider edge (UPE) on the access network is dual-
homed to SPE1 and SPE2 on the aggregation network. A VLL supporting access links of
various types is deployed on the access network. A VPLS is deployed on the aggregation
network to form a point-to-multipoint leased line network. Additionally, Fast Protection
Switching (FPS) is configured on the UPE; MPLS tunnel automatic protection switching
(APS) is configured on SPE1 and SPE2 to protect the links between the virtual switching
instances (VSIs) created on the two superstratum provider edges (SPEs).

Figure 4-10 UPE dual-homing networking
SPE1
VSI
PW FPS
UPE PE
Tunnel
VLL
APS
Node B RNC
VSI
SPE2
Feature Deployment
To deploy MPLS-TP OAM to monitor link connectivity of VLL and VPLS pseudo wires
(PWs), configure maintenance entity groups (MEGs) and maintenance entities (MEs) on the
UPE, SPE1, and SPE2 and then enable one or more of the continuity check (CC), and
loopback (LB) functions. The UPE monitors link connectivity and performance of the primary
and secondary PWs.
MPLS-TP OAM is implemented as follows:

l When SPE1 detects a link fault on the primary PW, SPE1 sends a Remote Defect
Indication (RDI) packet to the UPE, instructing the UPE to switch traffic from the
primary PW to the secondary PW. Meanwhile, the UPE sends a MAC Withdraw packet,
in which the value of the PE-ID field is SPE1's ID, to SPE2. After receiving the MAC
Withdraw packet, SPE2 transparently forwards the packet to the NPE and the NPE
deletes the MAC address it has learned from SPE1. After that, the NPE learns a new
MAC address from the secondary PW.
l After the primary PW recovers, the UPE switches traffic from the secondary PW back to
the primary PW. Meanwhile, the UPE sends a MAC Withdraw packet, in which the
value of the PE-ID field is SPE2's ID, to SPE1. After receiving the MAC Withdraw
packet, SPE1 transparently forwards the packet to the NPE and the NPE deletes the
MAC address it has learned from SPE2. After that, the NPE learns a new MAC address
from the new primary PW.
4.4 Terminology for MPLS-TP OAM

Terms
None
Abbreviations
Abbreviation Full Name
AIS Alarm Indication Signal
CC Continuity Check

Abbreviation Full Name
CSF Client Signal Failure
CV Connectivity Verification
DM Delay Measurement
LB Loopback
LCK Locked Signal
LM Loss Measurement
LSP Label Switched Path
LSR Label Switching Router
LT Linktrace
MEP Maintenance association End Point
MIP Maintenance association Intermediate Point
MPLS-TP Multiprotocol Label Switching Transport Profile
OAM Operation Administration & Maintenance
PE Provider Edge Router
PW Pseudo-Wires
RDI Remote Defect Indication
SPE Superstratum PE
TST Test
UPE Underlayer PE

Huawei MPLS-TP OAM

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei MPLS-TP OAM

Uploaded by

Copyright:

Available Formats

HUAWEI ME60 Multiservice Control Gateway

Feature Description - Network Reliability 4 MPLS-TP OAM

About This Chapter

4.1 Overview of MPLS-TP OAM

4.1 Overview of MPLS-TP OAM

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 61

MPLS-TP OAM Components

Figure 4-1 ME deployment on a point-to-point bidirectional LSP

Ingress LER Transit LER Transit LER Egress LER

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 62

Figure 4-2 ME node deployment

Table 4-1 MPLS-TP OAM fault management functions

Continuity check Checks link connectivity periodically.

Connectivity Detects forwarding faults continuously.

Loopback (LB) Performs loopback.

Remote defect Notifies remote defects.

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 63

Table 4-2 MPLS-TP OAM performance monitoring functions

4.2 Understanding MPLS-TP OAM

4.2.1 Basic Concepts

Figure 4-3 MPLS-TP OAM application

LSR A LSR B LSR C LSR D LSR F LSR G RNC

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 64

Table 4-3 MPLS-TP OAM components

Maintenance entity (ME) All MPLS-TP OAM l Section layer:

Maintenance entity group A MEG is comprised of one l Section layer:

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 65

Name Description Example

MEG intermediate point Intermediate nodes between l Section layer:

4.2.2 Continuity Check and Connectivity Verification

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 66

4.2.3 Packet Loss Measurement

Table 4-4 Packet loss measurement functions

Dual-ended Collects packet loss Dual-ended packet loss measurement provides

Single-ended Collects packet loss Sending CCMs imposes a heavier burden on

Dual-ended Packet Loss Measurement

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 67

Figure 4-4 Proactive dual-ended packet loss measurement

CE1 PE1 PE2 CE2

Dual-end LM CCM TxFCf RxFCb TxFCb

Near-end packet loss value = |TxFCf[tc] - TxFCb[tp]| - |RxFCl[tc] - RxFCl[tp]|

Far-end packet loss value = |TxFCb[tc] - TxFCb[tp]| - |RxFCb[tc] - RxFCb[tp]|

Single-ended Packet Loss Measurement

Figure 4-5 illustrates proactive single-end packet loss measurement.

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 68

Figure 4-5 Proactive single-ended packet loss measurement

CE1 PE1 PE2 CE2

Near-end packet loss value = |TxFCb[tc] - TxFCb[tp]| - |RxFCl[tc] - RxFCl[tp]|

Far-end packet loss value = |TxFCf[tc] - TxFCf[tp]| - |RxFCf[tc] - RxFCf[tp]|

4.2.4 Frame Delay Measurement

Table 4-5 Frame delay measurement functions

Function Description Usage Scenario

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 69

Function Description Usage Scenario

One-Way Frame Delay Measurement

Figure 4-6 One-way frame delay measurement

CE1 PE1 PE2 CE2

One-way DM 1DM TxTimeStampf

Frame delay time = RxTimef - TxTimeStampf

Two-Way Frame Delay Measurement

Issue 01 (2018-12-05) Copyright © Huawei Technologies Co., Ltd. 70

Figure 4-7 Two-way frame delay measurement

CE1 PE1 PE2 CE2

To obtain a more accurate result, RxTimeStampf and TxTimeStampb are used.