Figure 12: Mpls-Tp Maintenance Architecture - Alcatel-Lucent 7450 Manual

LER
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.
SROS supports the configuration of the following node and interface related identifiers:
•
•
•
Statically configured LSPs are identified using GMPLS-compatible identifiers with the addition of
a Tunnel_Num and LSP_Num. As in RSVP-TE, tunnels represent, for example, a set of working
and protect LSPs. These are GMPLS-compatible because GMPLS chosen by the IETF as the
7450 ESS MPLS Guide
MEP MIP
LSR A

Figure 12: MPLS-TP Maintenance Architecture

Global_ID: this is similar to the global ID that can be configured for Dynamic MS-PWs in
Release 9.0 of SR OS. However, in MPLS-TP this should be set to the AS# of the node. If
not explicitly configured, then it assumes the default value of 0. In SR OS, 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 system 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
routable IP address. Indeed, a node-id can represent a separate IP-compatible addressing
space that may be separate from the IP addressing plan of the underlying network. If no
node ID is configured, then the node ID is taken to be the system interface IPv4 address of
the node. When configuring a tunnel at an LER, either an IPv4 or an unsigned integer
Node ID can be configured as the source and destination identifiers, but both ends must be
of the same type.
IF_ID: This is an MPLS-TP section layer identifier at the MPLS interface level. On the
7x50, this is used to provide an identifier for the LSP-Trace DSMAP when an IP identifier
is not available. The IF_ID is a 64-bit identifier of an MPLS-TP interface on a node that is
unique within the scope of a Global_ID. It is composed of the Node_ID and the IF_Num.
The IF_Num is a node-wide unique identifier for an MPLS-TP interface. On the 7x50, this
is primarily used for supporting the DSMAP TLV in LSP Trace using MPLS-TP
identifiers with unnumbered MPSL-TP interfaces.
MIP
LSP
LSR B
MPLS and RSVP
MEG
MEP
LER
al_0226
Page 65