Automatic Creation Of A Rsvp Mesh Lsp; Feature Configuration - Alcatel-Lucent 7450 Manual

Automatic Creation of a RSVP Mesh LSP

Feature Configuration

The user first creates an LSP template of type mesh P2P:
config>router>mpls>lsp-template template-name mesh-p2p
Inside the template the user configures the common LSP and path level parameters or options
shared by all LSPs using this template.
Then the user references the peer prefix list which is defined inside a policy statement defined in
the global policy manager.
config>router>mpls>auto-lsp lsp-template template-name policy peer-prefix-policy
The user can associate multiple templates with same or different peer prefix policies. Each
application of an LSP template with a given prefix in the prefix list will result in the instantiation
of a single CSPF computed LSP primary path using the LSP template parameters as long as the
prefix corresponds to a router-id for a node in the TE database. This feature does not support the
automatic signaling of a secondary path for an LSP. If the user requires the signaling of multiple
LSPs to the same destination node, he/she must apply a separate LSP template to the same or
different prefix list which contains the same destination node. Each instantiated LSP will have a
unique LSP-id and a unique tunnel-ID. This feature also does not support the signaling of a non-
CSPF LSP. The selection of the 'no cspf' option in the LSP template is thus blocked.
Up to 5 peer prefix policies can be associated with a given LSP template at all times. Each time the
user executes the above command, with the same or different prefix policy associations, or the
user changes a prefix policy associated with an LSP template, the system re-evaluates the prefix
policy. The outcome of the re-evaluation will tell MPLS if an existing LSP needs to be torn down
or a new LSP needs to be signaled to a destination address which is already in the TE database.
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.
7450 ESS MPLS Guide
MPLS and RSVP
Page 149