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

162 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Configuring MPLS Fast Reroute using one-to-one backup
1
Brocade(config-mpls-lsp-frr_tunnel)# frr
Brocade(config-mpls-lsp-frr_tunnel-frr)# hop-limit 20
Syntax: [no] hop-limit number
The number of hops can be from 0 – 255.
Configuring priority for a MPLS Fast Reroute
The user can specify setup and hold priorities for the detour routes within a specified LSP. These
priorities are available to any LSP and function exactly the same on standard LSPs as they do on
detour LSPs. The priority determines the relative importance of the detour routes during setup or
preemption. The priority has two components the setup priority and the hold priority.
When a detour LSP is assigned a higher setup priority, it can preempt any LSP (detour or otherwise)
that is already established and has a lower holding priority, causing resources assigned to the
lower priority LSP to be diverted to the higher priority LSP. The hold priority specifies how likely an
established LSP is to give up its resources to another LSP. To be preempted, an LSP must have a
lower hold priority than the preempting LSPs setup priority. In addition, an established LSP can be
preempted by a higher priority LSP only when it would allow the higher priority LSP to be
established successfully.
To configure the detour routes of LSP frr_tunnel with a setup priority of six and hold priority of one.
Brocade(config-mpls-lsp-frr_tunnel)# frr
Brocade(config-mpls-lsp-frr_tunnel-frr)# priority 6 1
Syntax: [no] priority [setup-priority | hold-priority]
Possible values are zero (highest priority) through seven (lowest priority). A setup priority must be
lower than or equal to the configured hold priority on an LSP. By default, the setup priority is seven
and the hold priority is zero.
Including or excluding administrative groups from LSP calculations
Administrative groups, also known as resource classes or link colors, allows the user to assign
MPLS-enabled interfaces to various classes. When a device calculates the path for a detour LSP, it
takes into account the administrative group to which a interface belongs; the user can specify
which administrative groups the device can include or exclude when making its calculation.
For example, to include interfaces in either administrative group “gold” or “silver” in the path
calculations for detour routes of the LSP frr_tunnel.
Brocade(config-mpls-lsp-frr_tunnel)# frr
Brocade(config-mpls-lsp-frr_tunnel-frr)# include-any gold silver
Syntax: [no] include-any groups
The value specified for groups can be one or more valid administrative group names or numbers. In
this example, the device includes any of the interfaces that are members of groups “gold” or
“silver” when calculating detour routes for this LSP. Only those interfaces in the “gold” or “silver”
groups are considered for the detour routes. Interfaces that are not part of these groups, as well as
interfaces that are not part of any group, are eliminated from consideration.
To exclude interfaces in either administrative group “gold” or “silver” when detour routes for LSP
frr_tunnel are calculated.