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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 167
53-1003031-02
Dynamic Bypass LSPs
1
To change the value of one of these parameters, enter the command by the same name in the
bypass LSP context, and then enter the commit command. The following example changes the limit
on the number of hops a bypass LSP can traverse.
Brocade(config)# router mpls
Brocade(config-mpls)# bypass-lsp xm4-by
Brocade(config-mpls-bypasslsp-xm4-by)# hop-limit 20
Brocade(config-mpls-bypasslsp-xm4-by)# commit
For descriptions of all LSP parameters and the syntax of the commands that set them, refer to
“Configuring signaled LSP parameters” . For bypass LSPs, however, the user must execute the
commands in the bypass LSP context.
After entering the commit command, a new bypass LSP is signaled and includes the changes.
However, considerations apply depending on whether the enabled adaptive bypass LSP is currently
protecting any LSPs, and if so, whether it is actively carrying traffic. When the adaptive bypass LSP
is not currently protecting any LSP, no additional considerations exist on configuring LSP
parameters.
When the adaptive bypass LSP is carrying traffic from a locally repaired LSP, then the signaling of
the new LSP instance is delayed until the bypass LSP is no longer actively backing up any LSP.
When the adaptive bypass LSP is protecting LSPs, some of those protected LSPs might become
unprotected by this bypass LSP when the user changes any of the following parameters:
• exclude-any
• include-any
• include-all
• traffic-eng max-rate
• traffic-eng mean-rate
For example, when the traffic-eng mean-rate is decreased, one of the following actions takes place:
• The bypass LSP reroutes, which affects whether the backup is still valid on that bypass LSP.
• The bandwidth of the bypass LSP is reduced, which does not affect the path, but it does affect
any backup that is reserving bandwidth on the bypass LSP. In this case, the protected LSPs are
evaluated, and backups are removed from the bypass LSP until a consistent state is achieved.
The following example changes the traffic-eng mean-rate for a bypass LSP.
Brocade(config)# router mpls
Brocade(config-mpls)# bypass-lsp xm4-by
Brocade(config-mpls-bypasslsp-xm4-by)# traffic-eng mean-rate 2000
Brocade(config-mpls-bypasslsp-xm4-by)# commit
Syntax: commit
Dynamic Bypass LSPs
When the user configures node protection or link protection on a device, bypass LSPs are created
to the next-hop or next-next-hop routers for the LSPs traversing the device. Multiple protected LSPs
use the same bypass LSP in case of protected LSP link or node failures.