Alcatel-Lucent 7210 SAS M User Manual page 54

MPLS Transport Profile (MPLS-TP)
The 'to' tunnel number is an optional parameter. If it is not entered, then it is taken to be the same
value as the source tunnel number.
LSPs are assumed to be bidirectional and co-routed in Relase 11.0. Therefore, system will assume
that the incoming interface is the same as the out-link.
The next-hop <ip-address> can only be configured if the out-link if-name refers to a numbered IP
interface. In this case, the system will determine the interface to use to reach the configured next-
hop, but will check that the user-entered value for the out-link corresponds to the link returned by
the system. If they do not correspond, then the path will not come up. Note that if a user changes
the physical port referred to in the interface configuration, then BFD, if configured on the LSP,
will go down. Users should therefore ensure that an LSP is moved to a different interface with a
different port configuration in order to change the port that it uses. This is enforced by blocking the
next-hop configuration for an unnumbered interface.
There is no check made that a valid ARP entry exists before allowing a path to be un shut.
Therefore, a path will only be held down if BFD is down. If static ARP is not configured for the
interface, then it is assumed that dynamic ARP is used. The result is that if BFD is not configured,
a path can come up before ARP resolution has completed for an interface. If BFD is not used, then
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:
•
•
•
•
•
•
•
Page 54
tion Guide
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. It's default value is '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 does not 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.
7210 SAS M, T, X, R6, Mxp MPLS Configura-