Mpls-Tp Maintenance Identifiers; Figure 9: Mpls-Tp Maintenance Architecture - Alcatel-Lucent 7210 SAS M User Manual

MPLS Transport Profile (MPLS-TP)

MPLS-TP Maintenance Identifiers

MPLS-TP is designed for use both with, and without, a control plane. MPLS-TP therefore
specifies a set of identifiers that can be used for objects in either environment. This includes a path
and maintenance identifier architecture comprising Node, Interface, PW and LSP identifiers,
Maintenance Entity Groups (MEGs), Maintenance End Points (MEPs) and Maintenance
Intermediate Points (MIPs). These identifiers are specified in RFC6370.
MPLS-TP OAM and protection switching operates within a framework that is designed to be
similar to existing transport network maintenance architectures. MPLS-TP introduces concept of
maintenance domains to be managed and monitored. In these, Maintenance Entity Group End
Points (MEPs) are edges of a maintenance domain. OAM of a maintenance level must not leak
beyond corresponding MEP and so MEPs typically reside at the end points of LSPs and PWs.
Maintenance Intermediate Points (MIPS) define intermediate nodes to be monitored. Maintenance
Entity Groups (MEGs) comprise all the MEPs and MIPs on an LSP or PW.
Both IP-compatible and ICC (ITU-T carrier code) based identifiers for the above objects are
specified in the IETF, but only the IP-compatible identifiers defined in RFC6370 are supported.
The 7210 SAS supports the configuration of the following node and interface related identifiers:
•
•
Page 34
tion Guide

Figure 9: MPLS-TP Maintenance Architecture

Global_ID: In MPLS-TP, the Global_ID should be set to the AS# of the node. If not
explicitly configured, then it assumes the default value of 0. In 7210 SAS, the source
Global ID for an MPLS-TP Tunnel is taken to be the Global ID configured at the LER.
The destination Global ID is optional in the tunnel configuration. If it is not configured,
then it is taken as the same as the source Global ID.
Node_ID: This is a 32-bit value assigned by the operator within the scope of the
Global_ID. The 7210 SAS supports the configuration of an IPv4 formatted address
<a.b.c.d> or an unsigned 32-bit integer for the MPLS-TP Node ID at each node. The node
ID must be unique within the scope of the global ID, but there is no requirement for it to
be a valid IP address. Indeed, a node-id can represent a separate IP-compatible addressing
7210 SAS M, T, X, R6, Mxp MPLS Configura-