Configuring MPLS-TP
Page 88 7450 ESS MPLS Guide
it is recommended that the connectivity of the path is explicitly checked using on-demand CC/CV
prior to sending user traffic on it.
The following is a list of additional considerations for the configuration of MPLS-TP LSPs and
paths:
• The working-tp-path must be configured before the protect-tp-path.
• Likewise, the protect-tp-path has to be deleted first before the working-tp-path.
•The lsp-num parameter is optional. The default values are 1 for the working-tp-path and 2
for protect-tp-path.
•The mep context must be deleted before a path can be deleted.
• An MPLS interface needs to be created under config>router>mpls>interface before
using/specifying the out-label/out-link in the Forward path for an MPLS-TP LSP. Creation
of the LSP will fail if the corresponding mpls interface doesn't exist even though the
specified router interface may be valid.
• The system will program the MPLS-TP LSP information upon a no shutdown of the TP-
Path only on the very first no shutdown. The Working TP-Path is programmed as the
Primary and the Protection TP-Path is programmed as the backup.
• The system will not de-program the IOM on an admin shutdown of the MPLS-TP path.
Traffic will gracefully move to the other TP-Path if valid, as determined by the proactive
MPLS-TP OAM. This should not result in traffic loss. However it is recommended that
the user does moves traffic to the other TP-Path through a tools command before doing
'admin shut' of an Active TP-Path.
• 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.
To Next Page
Loading...
