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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 149
53-1003031-02
Configuring an adaptive LSP
1
Configuring an adaptive LSP
The Multi-Service IronWare software supports Adaptive LSPs. Using this feature, the user can
change the following parameters of an LSP while it is in the enabled state:
• cspf
• exclude-any
• hop-limit
• include-all
• include-any
• primary-path
• priority
• tie-breaking
• traffic-eng
When one of these parameters is changed on a Adaptive LSP, a new instance of the same LSP is
signaled using the newly defined parameters. Once the new LSP comes up, traffic is moved to the
new LSP instance and the old LSP instance is torn down.
To configure an LSP named to20 as an Adaptive LSP, use the following commands.
Brocade(config)# router mpls
Brocade(config-mpls)# lsp to20
Brocade(config-mpls-lsp-to20)# adaptive
Syntax: [no] adaptive
Once an LSP is configured to be adaptive, it can have the parameters described above changed. In
the following example, the Setup and hold priorities for adaptive LSP to20 are changed to seven
and one.
Brocade(config-mpls)# lsp to20
Brocade(config-mpls-lsp-to20)# priority 7 1
The new parameters are not changed for the adaptive LSP until the commit command is issued for
the LSP.
NOTE
Once the commit command has been issued, there may be a 30 ms traffic disruption.
In the following example of the show mpls lsp command for lsp to20, the priorities are not changed
in the output.
Brocade(config-mpls-lsp-to212)# show mpls lsp to212
LSP to212, to 10.5.1.1
From: 10.4.1.1, admin: UP, status: UP, tunnel interface: tnl1
Times primary LSP goes up since enabled: 1
Metric: 0, number of installed aliases: 0 Adaptive
Maximum retries: 0, no. of retries: 0
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Constraint-based routing enabled: yes
Tie breaking: random, hop limit: 0