MPLS-TP Maintenance Identifiers
Page 66 7450 ESS MPLS Guide
control plane for MPLS-TP LSPs, although this is not supported in Release 11.0 of the 7750. PWs
are identified using a PW Path ID which has the same structure as FEC129 AII Type 2.
SR OS derives the identifiers for MEPs and MIPs on LSPs and PWs based on the configured
identifiers for the MPLS-TP Tunnel, LSP or PW Path ID, for use in MPLS-TP OAM and
protection switching, as per RFC6370.
The information models for LSPs and PWs supported in Release 11.0 are illustrated in Figure 13
and Figure 14. The figures use the terminology defined in RFC6370.
Figure 13: MPLS-TP LSP and Tunnel Information Model
The MPLS-TP Tunnel ID and LSP ID are not to be confused with the RSVP-TE tunnel id
implemented on the 7x50 system. Table 3 shows how these map to the X and Y ends of the tunnel
shown in the above figure for the case of co-routed bidirectional LSPs.
al_0227
MEPs MIP
LSP_a
meg_id =
isp_id
mep_id =
global_id::node_id::
tunnel_id::isp_num
mip_id =
node_id::0
isp_id =
x-tunnel_id::y-tunnel_id::isp_num
x-tunnel_id =
global_id::node_id::tunnel_num
x-tunnel if_id = node_id::if_num
if_id =
node_id::if_num
Working
LER X LSR A LSR B LER Y
MIP
MIP
LSP_b
Protect
global_id
node_id
LSR C LSR D
MIP
MEPs
MEG
Table 3: Mapping from RSVP-TE to MPLS-TP Maintenance Identifiers
RSVP-TE Identi-
fier
MPLS-TP Maintenance Identifier
Tunnel Endpoint
Address
Node ID (Y)
Tunnel ID (X) Tunnel Num (X)
Extended Tunnel ID Node ID (X)
Tunnel Sender
Address
Node ID (X)
LSP ID LSP Num
To Next Page
Loading...
