MPLS Transport Profile (MPLS-TP)
Page 30 7210 SAS M, T, X, R6, Mxp MPLS Configura-
tion Guide
The following MPLS-TP OAM and protection mechanisms, defined by the IETF, are supported:
• MPLS-TP Generic Associated Channel for LSPs and PWs (RFC 5586)
• MPLS-TP Identifiers (RFC 6370)
• Proactive CC, CV, and RDI using BFD for LSPs (RFC 6428)
• BFD based CV is not supported in this release.
• On-Demand CV for LSPs and PWs using LSP Ping and LSP Trace (RFC 6426)
• 1-for-1 Linear protection for LSPs (RFC 6378)
• Static PW Status Signaling (RFC 6478)
The 7210 SAS can play the role of an LER and an LSR for static MPLS-TP LSPs, and a PE/T-PE
for static MPLS-TP PWs. It can also act an MPLS network that supports both MPLS-TP and
dynamic IP/MPLS.
MPLS-TP Model
Figure 5 shows a high level functional model for MPLS-TP in 7210 SAS. LSP A and LSP B are
the working and protect LSPs of an LSP tunnel. These are modelled as working and protect paths
of an MPLS-TP LSP in 7210 SAS. MPLS-TP OAM runs in-band on each path. 1:1 linear
protection coordinates the working and protect paths, using a protection switching coordination
protocol (PSC) that runs in-band on each path over a Generic Associated Channel (G-ACh) on
each path. Each path can use an IP numbered, IP unnumbered, or MPLS-TP unnumbered (that is,
non-IP) interface.
Figure 5: MPLS-TP Model
To Next Page
Loading...
