Alcatel-Lucent 7210 SAS M - Proactive CC;CV (Using BFD) Configuration

MPLS and RSVP
7210 SAS M, T, X, R6, Mxp MPLS Configuration Guide Page 55
• Deletion of the out-label/out-link sub-command under the MPLS-TP Path is not allowed
once configured. These can only be modified.
• MPLS will allow the deletion of an 'admin shutdown' TP-Path. This will cause MPLS to
de-program the corresponding TP-Path forwarding information from IOM. This can cause
traffic loss for certain users that are bound to the MPLS-TP LSP.
• MPLS will not de-program the IOM on a specific interface admin shut/clear unless the
interface is a System Interface. However, if mpls informs the TP-OAM module that the
mpls interface has gone down, then it triggers a switch to the standby tp-path if the
associated interface went down and if it is valid.
• If a MEP is defined and shutdown, then the corresponding path is also operationally
down. Note, however, that the MEP admin state is applicable only when a MEP is created
from an MPLS-TP path.
• It is not mandatory to configure BFD or protection on an MPLS-TP path in order to bring
the LSP up.
•If bfd-enable cc is configured, then CC-only mode using ACh channel 0x07 is used. If
bfd-enable cc_v is configured, then BFD CC packets use channel 0x22 and CV packets
use channel 0x23.
The protection template is associated with a LSP as a part of the MEP on the protect path. If only
a working path is configured, then the protection template is not configured.
BFD cannot be enabled under the MEP context unless a named BFD template is configured.
Proactive CC/CV (using BFD) Configuration
Generally applicable proactive OAM parameters are configured using templates.
NOTE: The 7210 SAS-R6 supports only BFD based CC mode. BFD based CC-CV mode is not
supported in current release.
Proactive CC and CV uses BFD parameters such as Tx/Rx timer intervals, multiplier and other
session/fault management parameters which are specific to BFD. These are configured using a
BFD Template. The BFD Template may be used for non-MPLS-TP applications of BFD, and
therefore contains the full set of possible configuration parameters for BFD. Only a sub-set of
these may be used for any given application.
Generic MPLS-TP OAM and fault management parameters are configured in the OAM Template.
Named templates are referenced from the MPLS-TP Path MEP configuration, so different
parameter values are possible for the working and protect paths of a tunnel.
The BFD Template is configured as follows:
config