Alcatel-Lucent 7210 SAS M - Page 53

MPLS and RSVP
7210 SAS M, T, X, R6, Mxp MPLS Configuration Guide Page 53
[no] working-tp-path
lsp-num <lsp-num>
in-label <in-label>
out-label <out-label> out-link <if-name>
[next-hop <ipv4-address>]
[no] mep
[no] oam-template <name>
[no] bfd-enable [cc | cc_cv] // defaults to cc
[no] shutdown
exit
[no] shutdown
exit
[no] protect-tp-path
lsp-num <lsp-num>
in-label <in-label>
out-label <out-label> out-link <if-name>
[next-hop <ipv4-address> ]
[no] mep
[no] protection-template <name>
[no] oam-template <name>
[no] bfd-enable [cc | cc_cv] //defaults to cc
[no] shutdown
exit
[no] shutdown
exit
<if-name> could be numbered or unnumbered interface using an Ethernet port.
<src-tunnel-num> is a mandatory create time parameter for mpls-tp tunnels, and has to be assigned
by the user based on the configured range of tunnel ids. The src-global-id used for the LSP ID is
derived from the node-wide global-id value configured under config>router>mpls>mpls-tp. A
tunnel can not be un shutdown unless the global-id is configured.
The from address of an LSP to be used in the tunnel identifier is taken to be the local node’s node-
id/global-id, as configured under config>router>mpls>mpls-tp. If that is not explicitly configured,
either, then the default value of the system interface IPv4 address is used
The to node-id address may be entered in 4-octet IPv4 address format or unsigned 32-bit format.
This is the far-end node-id for the LSP, and does do need to be IP addresses.
The from and to addresses are used as the from and to node-id in the MPLS-TP Tunnel Identifier
used for the MEP ID.
Each LSP consists of a working-tp-path and, optionally, a protect-tp-path. The protect-tp-path
provides protection for the working-tp-path is 1:1 linear protection is configured (see below).
Proactive OAM, such as BFD, is configured under the MEP context of each path. Protection for
the LSP is configured under the protect-tp-path mep context.
The ‘to’ global-id is an optional parameter. If it is not entered, then the dest global ID takes the
default value of 0. Global ID values of 0 are allowed and indicate that the node’s configured
Global ID should be used. If the local global id value is 0, then the remote ‘to’ global ID must also
be 0. The ‘to’ global ID value cannot be changed if an LSP is in use by an SDP.