Alcatel-Lucent 7450 Manual page 228

MPLS Commands
If a /32 prefix is added to (removed from) or if a prefix range is expanded (shrunk) in a prefix list
associated with a LSP template, the same prefix policy re-evaluation described above is performed.
The user must perform a no shutdown of the template before it takes effect. Once a template is in
use, the user must shutdown the template before effecting any changes to the parameters except for
those LSP parameters for which the change can be handled with the Make-Before-Break (MBB)
procedures. These parameters are bandwidth and enabling fast-reroute with or without the hop-
limit or node-protect options. For all other parameters, the user shuts down the template and once a it
is added, removed or modified, the existing instances of the LSP using this template are torn down
and re-signaled.
The trigger to signal the LSP is when the router with a router-id the matching a prefix in the prefix list
appears in the Traffic Engineering database. The signaled LSP is installed in the Tunnel Table
Manager (TTM) and is available to applications such as LDP-over-RSVP, resolution of BGP label
routes, resolution of BGP, IGP, and static routes. It is, however, not available to be used as a
provisioned SDP for explicit binding or auto-binding by services.
Except for the MBB limitations to the configuration parameter change in the LSP template, MBB
procedures for manual and timer based re-signaling of the LSP, for TE Graceful Shutdown and for
soft pre-emption are supported.
The one-to-one option under fast-reroute, the LSP Diff-Serv class-type and backup-class-type
parameters are not supported. If diffserv-te is enabled under RSVP, the auto-created LSP will still be
signaled but with the default LSP class type.
If the one-hop option is specified instead of a prefix list, this command enables the automatic
signaling of one-hop point-to-point LSPs using the specified template to all directly connected
neighbors. This LSP type is referred to as auto-LSP of type one-hop. Although the provisioning
model and CLI syntax differ from that of a mesh LSP only by the absence of a prefix list, the actual
behavior is quite different. When the above command is executed, the TE database will keep track of
each TE link that comes up to a directly connected IGP neighbor which router-id is discovered. It
then instructs MPLS to signals an LSP with a destination address matching the router-id of the
neighbor and with a strict hop consisting of the address of the interface used by the TE link. Thus, the
auto-lsp command with the one-hop option will result in one or more LSPs signaled to the
neighboring router.
An auto-created mesh or one-hop LSP can have egress statistics collected at the ingress LER by
adding the egress-statistics node configuration into the LSP template. The user can also have ingress
statistics collected at the egress LER using the same ingress-statistics node in CLI used with a
provisioned LSP. The user must specify the full LSP name as signaled by the ingress LER in the
RSVP session name field of the Session Attribute object in the received Path message.
The no form of this command deletes all LSP signaled using the specified template and prefix policy.
When the one-hop option is used, it deletes all one-hop LSPs signaled using the specified template to
all directly connected neighbors.
Parameters lsp-template template-name — Specifies an LSP template name up to 32 characters in length.
policy peer-prefix-policy — Specifies an peer prefix policy name up to 32 characters in length.
Page 228 7450 ESS MPLS Guide