Mpls-Tp Lsp Protection - Alcatel-Lucent 7450 Manual

MPLS-TP Maintenance Identifiers
contains the SAP connected to the external device is used to inject test traffic into the PW. Lock
request messaging is not supported.
A lock can be applied using the CLI or NMS. The forwarding state of the PW can be either active
or standby.
After the PW is locked it can be put into loopback mode (for two way tests) so the ingress data
path in the forward direction is cross connected to the egress data path in the reverse direction of
the PW. The loopback can be configured through the CLI or NMS.
The PW loopback is created at the PW level, so everything under the PW label is looped back.
This distinguishes a PW loopback from a service loopback, where only the native service packets
are looped back.
The following MPLS-TP loopback configuration is supported:
•
•
For more information about configuring lock instruct and loopback for MPLS-TP Pseudowires
see, 7450 ESS Services Overview Guide.

MPLS-TP LSP Protection

Linear 1-for-1 protection of MPLS-TP LSPs is supported, as defined in RFC. This applies only to
LSPs (not PWs).
This is supported edge-to-edge on an LSP, between two LERs, where normal traffic is transported
either on the working LSP or on the protection LSP using a logical selector bridge at the source of
the protected LSP.
At the sink LER of the protected LSP, the LSP that carries the normal traffic is selected, and that
LSP becomes the working LSP. A protection switching coordination (PSC) protocol coordinates
between the source and sink bridge, which LSP will be used, as working path and protection path.
The PSC protocol is always carried on a G-ACh on the protection LSP.
Page 76
An MPLS-TP loopback can be created for an epipe, cpipe or apipe VLL.
Test traffic can be inserted at an epipe, cpipe or apipe VLL endpoint or at an epipe
spoke-sdp termination on a VPLS interface.
7450 ESS MPLS Guide