MPLS and RSVP-TE
168
MPLS Guide
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com
3HE 18686 AAAB TQZZA
The no form of this command disables the use of administrative group constraints on a FRR
backup LSP at a PLR node.
Default no admin-group-frr
auto-lsp
Syntax auto-lsp lsp-template template-name {policy peer-prefix-policy [peer-prefix-policy...(up to 5
max)] | one-hop}
no auto-lsp lsp-template template-name
Context config>router>mpls
Description This command enables the automatic creation of an RSVP-TE point-to-point LSP within a
single IGP IS-IS level or OSPF area that can subsequently be used by services and/or IGP
shortcuts. It can be used to create an RSVP-TE LSP mesh to a destination node whose router
ID matches a prefix in a specified previously created peer prefix policy, or to create
single-hop RSVP-TE LSPs. These LSP types are referred to as auto LSP of type mesh or
auto LSP of type one-hop.
Multiple templates can be associated with the same or different peer prefix policies. Each
application of an LSP template with a given prefix in the prefix list results 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. Auto LSP does not
support the automatic signaling of a secondary path for an LSP. If the signaling of multiple
LSPs to the same destination node is required, a separate LSP template must be associated
with a prefix list that contains the same destination node address. Each instantiated LSP will
have a unique LSP ID and a unique tunnel ID. Auto LSP also does not support the signaling
of a non-CSPF LSP. The selection of the no cspf option in the LSP template is blocked.
Up to five peer prefix policies can be associated with an LSP template. Every time the user
executes the above command with the same or different prefix policy associations or a prefix
policy associated with the LSP template, the system re-evaluates the prefix policy. The
outcome of the re-evaluation indicates to MPLS whether an existing LSP must be torn down
or a new LSP must be signaled to a destination address that is already in the TE database.
If a /32 prefix is added to or removed from a prefix list associated with the template, or if a
prefix range is expanded or narrowed, the prefix policy re-evaluation described above is
performed.
A no shutdown of the template must be performed before it takes effect. When a template
is in use, it must be shut down before the user can make any changes to the parameters
except for LSP parameters for which the change can be handled with the Make-Before-Break
(MBB) procedures. This includes fast-reroute with or without the hop-limit or node-protect
options. When the template is shut down and parameters are added, removed or modified,
the existing instances of the LSP using this template are torn down and resignaled.
To Next Page
Loading...
Need help?
General
