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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 139
53-1003031-02
FRR bypass LSPs
1
Enabling a signaled LSP
After the user sets the parameters for the signaled LSP, the user can enable it. Enabling the LSP
causes the path to be set up and resources reserved on the LSRs in the LSPs primary path.
Enabling the LSP is the final step in configuring it.
To enable LSP tunnel1.
Brocade(config-mpls)# lsp tunnel1
Brocade(config-mpls-lsp)# enable
Syntax: [no] enable
Disabling an LSP
Disabling an LSP de-activates it, but does not remove the LSP from the device’s configuration. (To
remove the LSP from the device’s configuration, use the no lsp command.) To make
changes to an active LSP, first disable the LSP, modify parameters on the LSP, and then enable the
LSP.
To disable LSP tunnel1.
Brocade(config-mpls)# lsp tunnel1
Brocade(config-mpls-lsp)# disable
Syntax: [no] disable
FRR bypass LSPs
The LSP ping and traceroute facilities support FRR bypass LSPs. The user can ping or trace the
protected LSP and bypass tunnel separately.
The user can ping or trace the ingress-originated or transit-originated bypass tunnel by specifying
either the name of bypass LSP (as the user would any regular LSP name) or the entire RSVP
session ID (including the tunnel endpoint, the tunnel ID, and the extended tunnel ID).
NOTE
In the current facility backup implementation, the bypass LSP name must be unique in the system
(for example, the name cannot be the same as the regular LSP name).
The traceroute output of a backup tunnel depends on the setting of the propagate-ttl and
label-propagate-ttl options. When both propagate-ttl and label-propagate-ttl options are turned on,
the traceroute output shows the detail of the bypass path. When both options are turned off, the
bypass path is shown as a single hop. The options are either both ON or both OFF.
To trace the route of a backup path, the TTL of the bypass and protected labels (when they are not
implicit NULL labels) are set as in the following example:
• Both propagate-ttl and label-propagate-ttl are ON: TTL = 1, 2, 3, and so on, are set for both
labels.
• Otherwise: bypass label TTL is set to 255. Protected label TTL is set to 1, 2, 3, and so on.
IP TTL is set to top most label TTL. Otherwise, it is set to 255.