Table of Contents
Advertisement
MPLS and RSVP-TE
Primary Path and FRR Behavior
Once the primary path of the LSP is set up and is operationally up, any subsequent changes
to the SRLG membership of an interface that the primary path is using will not be considered
by the MPLS/RSVP-TE task at the PLR for FRR bypass or detour LSP association until the
next opportunity that the primary path is resignaled. The path may be resignaled due to a
failure or to a make-before-break (MBB) operation. A make-before-break operation occurs as
a result of a global revertive operation, a reoptimization of the LSP path (timer-based or
manual), or a change by the user to any of the path constraints.
Once the FRR bypass or detour LSP is set up and is operationally up, any subsequent
change to the SRLG membership of an interface that the FRR bypass or detour LSP is using
will not be considered by the MPLS/RSVP-TE task at the PLR until the next opportunity that
the association with the primary LSP path is rechecked. The association is rechecked if the
FRR bypass or detour LSP is reoptimized. Detour routes are not reoptimized and are
resignaled if the primary path is down.
The user must first shut down MPLS before enabling or disabling the srlg-frr option in CLI.
An RSVP-TE interface can belong to a maximum of 64 SRLGs. The user creates SRLGs
using the config>router>mpls>srlg-group command. The user associates the SRLGs with
an RSVP-TE interface using the srlg-group command in the config>router>
mpls>interface context.
The no form of the command reverts to the default value.
Default
no srlg-frr
Parameters
strict — specifies that the CSPF calculation for the FRR backup must include the SRLG
176
constraint and the backup must be on the resulting list of eligible backup paths
Values
non-strict:srlg-frr
strict:srlg-frr strict
Use subject to Terms available at: www.nokia.com
© 2022 Nokia.
MPLS Guide
3HE 18686 AAAB TQZZA
Advertisement
Table of Contents
