MPLS and RSVP
7210 SAS M, T, X, R6, Mxp MPLS Configuration Guide Page 155
Once primary path of the LSP is setup and is operationally up, any subsequent changes to the SRLG
group membership of an interface the primary path is using would not be considered until the next
opportunity the primary path is re-signaled. The primary path may be re-signaled due to a failure or to
a make-before-break operation. Make-before-break occurs as a result of a global revertive operation,
a timer based or manual re-optimization of the LSP path, or an operator change to any of the path
constraints.
One an SRLG secondary path is setup and is operationally UP, any subsequent changes to the SRLG
group membership of an interface the secondary path is using would not be considered until the next
opportunity secondary path is re-signaled. The secondary path is re-signaled due to a failure, to a re-
signaling of the primary path, or to a make before break operation. Make-before break occurs as a
result of a timer based or manual re-optimization of the secondary path, or an operator change to any
of the path constraints of the secondary path, including enabling or disabling the SRLG constraint
itself.
Also, the user-configured include/exclude admin group statements for this secondary path are also
checked together with the SRLG constraints by CSPF
The no form of the command reverts to the default value.
Default no srlg
standby
Syntax [no] standby
Context config>router>mpls>lsp>secondary
Description The secondary path LSP is normally signaled once the primary path LSP fails. The standby keyword
ensures that the secondary path LSP is signaled and maintained indefinitely in a hot-standby state.
When the primary path is re-established then the traffic is switched back to the primary path LSP.
The no form of this command specifies that the secondary LSP is signaled when the primary path
LSP fails.
Default none
To Next Page
Loading...
Need help?
General
