Alcatel-Lucent 7950 SR User Configuration Manual page 69

•
•
•
•
•
7950 SR OS MPLS Configuration Guide
 Receipt of a PathErr message with error code=25 (Notify) and sub-code=7 (Local link
maintenance required) or a sub-code=8 (Local node maintenance required). This
invokes the TE Graceful Shutdown MBB. Note that in this case, only a single attempt
is performed by MBB as in current implementation; only the main CT will be retried.
 Receipt of a Resv refresh message with the 'Preemption pending' flag set or a PathErr
message with error code=34 (Reroute) and a value=1 (Reroute request soft
preemption). This invokes the soft pre-emption MBB.
 Receipt of a ResvTear message.
 A configuration change MBB.
When an unmapped LSP primary path goes into retry, it uses the main CT until the
number of retries reaches the value of the new main-ct-retry-limit parameter. If the path
did not come up, it must start using the backup CT at that point in time. By default, this
parameter is set to infinite value. The new main-ct-retry-limit parameter has no effect on
an LSP primary path, which retries due to a failure event. This parameter is configured
using the main-ct-retry-limit command in the config>router>mpls>lsp context. If the
user entered a value of the main-ct-retry-limit parameter that is greater than the LSP
retry-limit, the number of retries will still stop when the LSP primary path reaches the
value of the LSP retry-limit. In other words, the meaning of the LSP retry-limit parameter
is not changed and always represents the upper bound on the number of retries. The
unmapped LSP primary path behavior applies to both CSPF and non-CSPF LSPs.
An unmapped LSP primary path is a path that never received a Resv in response to the
first path message sent. This can occur when performing a "shut/no-shut" on the LSP or
LSP primary path or when the node reboots. An unmapped LSP primary path goes into
retry if the retry timer expired or the head-end node received a PathErr message before the
retry timer expired.
When the clear>router>mpls>lsp command is executed, the retry behavior for this LSP
is the same as in the case of an unmapped LSP.
If the value of the parameter main-ct-retry-limit is changed, the new value will only be
used at the next time the LSP path is put into a "no-shut" state.
The following is the behavior when the user changes the main or backup CT:
 If the user changes the LSP level CT, all paths of the LSP are torn down and re-
signaled in a break-before-make fashion. Specifically, the LSP primary path will be
torn down and re-signaled even if it is currently using the backup CT.
 If the user changes the main CT of the LSP primary path, the path will be torn down
and re-signaled even if it is currently using the backup CT.
 If the user changes the backup CT of an LSP primary path when the backup CT is in
use, the path is torn down and is re-signaled.
 If the user changes the backup CT of an LSP primary path when the backup CT is not
in use, no action is taken. If however, the path was in global Revertive, gshut, or soft
pre-emption MBB, the MBB is restarted. This actually means the first attempt will be
with the main CT and subsequent ones, if any, with the new value of the backup CT.
MPLS and RSVP
Page 69