Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 190)

166 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Configuring a bypass LSP to be adaptive
1
The lsp-name variable specifies the LSP to be optimized. This LSP can be a regular LSP or a bypass
LSP.
Time-triggered reoptimizing a bypass LSP
As with regular LSPs, the user can set a timer to optimize a specific bypass LSP path on a periodic
basis. By default, the timer is disabled. Upon expiration of this timer, the bypass LSP is optimized
for a new path when the new path has a lower cost than the existing path.
The user can configure the reoptimization timer when the bypass LSP is in either the disabled state
or the enabled state. When configured with the bypass LSP in the disabled state, the new timer
value takes effect immediately. When configured with the bypass LSP in the enabled state, the new
timer value takes effect when the user performs an explicit commit operation by entering the
commit command; until the user enters the commit command, the timer expires according to its
previous setting.
When the bypass LSP is carrying traffic when the reoptimization timer expires, the path is not
reoptimized, and the bypass LSP is evaluated for optimization the next time the timer expires.
To set the reoptimization timer for a bypass LSP, use the reoptimize-timer command in the bypass
LSP context.
Brocade(config)# router mpls
Brocade(config-mpls)# bypass-lsp xm4-by
Brocade(config-mpls-bypasslsp-xm4-by)# reoptimize-timer 1000
Brocade(config-mpls-bypasslsp-xm4-by)# commit
Syntax: [no] reoptimize-timer seconds
The seconds variable specifies the number of seconds from the beginning of one reoptimization
attempt to the beginning of the next attempt. The range of values for seconds is 300 through
65535. The [no ] option can be used to disable a timer that has been configured.
Modifying parameters on an enabled bypass LSP
When an adaptive bypass LSP is enabled, the user can change the following parameters:
• exclude-any
• exclude-interface
• hop-limit
• include-all
• include-any
• primary-path
• priority
• reoptimize-timer
• tie-breaking
• traffic-eng
NOTE
For a bypass LSP, the user cannot change the CSPF parameter.