MPLS Commands
Page 218 7450 ESS MPLS Guide
lsp-template
Syntax lsp-template template-name [p2mp | one-hop-p2p | mesh-p2p]
no lsp-template template-name
Context config>router>mpls
Description This command creates a template construct that can be referenced by client application where
dynamic LSP creation is required. The LSP template type p2mp, one-hop-p2p, or mesh-p2p is
mandatory.
The no form of command deletes LSP template. LSP template cannot be deleted if a client
application is using it.
Parameters lsp-template-name — Specifies the name to identify LSP template. ANy LSP template name and LSP
name must not be the same.
p2mp | one-hop-p2p | mesh-p2p — Identifies the type of the LSP this template will signal.
propagate-admin-group
Syntax [no] propagate-admin-group
Context config>router>mpls>lsp>fast-reroute
config>router>mpls>lsp-template>fast-reroute
Description The command enables the signaling of the primary LSP path admin-group constraints in the FRR
object at the ingress.
When this command is executed, the admin-group constraints configured in the context of the P2P
LSP primary path, or the ones configured in the context of the LSP and inherited by the primary path,
are copied into the FAST_REROUTE object. The admin-group constraints are copied into the
‘include-any’ or ‘exclude-any’ fields.
The ingress LER thus propagates these constraints to the downstream nodes during the signaling of
the LSP to allow them to include the admin-group constraints in the selection of the FRR backup LSP
for protecting the LSP primary path.
The ingress LER will insert the FAST_REROUTE object by default in a primary LSP path message.
If the user disables the object using the following command, the admin-group constraints will not be
propagated: configure>router>mpls>no frr-object .
Note that the same admin-group constraints can be copied into the Session Attribute object. They are
intended for the use of an LSR, typically an ABR, to expand the ERO of an inter-area LSP path. They
are also used by any LSR node in the path of a CSPF or non-CSPF LSP to check the admin-group
constraints against the ERO regardless if the hop is strict or loose. These are governed strictly by the
command:
configure>router>mpls>lsp>propagate-admin-group
In other words, the user may decide to copy the primary path admin-group constraints into the
FAST_REROUTE object only, or into the Session Attribute object only, or into both. Note, however,
that the PLR rules for processing the admin-group constraints can make use of either of the two
object admin-group constraints.
To Next Page
Loading...
