Admin Group Support on Facility Bypass Backup LSP
Page 106 7450 ESS MPLS Guide
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.
Procedures at PLR Node
The user enables the use of the admin-group constraints in the association of a manual or dynamic
bypass LSP with the primary LSP path at a Point-of-Local Repair (PLR) node using the following
global command:
configure>router>mpls>admin-group-frr
When this command is enabled, each PLR node reads the admin-group constraints in the
FAST_REROUTE object in the Path message of the LSP primary path. If the FAST_REROUTE
object is not included in the Path message, then the PLR will read the admin-group constraints
from the Session Attribute object in the Path message.
If the PLR is also the ingress LER for the LSP primary path, then it just uses the admin-group
constraint from the LSP and/or path level configurations.
Whether the PLR node is also the ingress LER or just an LSR for the protected LSP primary path,
the outcome of the ingress LER configuration dictates the behavior of the PLR node and is
summarized in Table 4.
Table 4: Bypass LSP Admin-Group Constraint Behavior
Ingress LER
Configuration
Session Attribute FRR Object Bypass LSP at PLR
(LER/LSF) follows
admin-group con-
straints
1
frr-object
lsp>no propagate-admin
group
lsp>frr>propagate-admin-
group
Admin color constraints
not sent
Admin color constraints
sent
yes
2
frr-object
lsp>propagate-admin-
group
lsp>frr>propagate-admin
group
Admin color constraints
sent
Admin color constraints
sent
yes