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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 135
53-1003031-02
Setting up signaled LSPs
1
Configuring a priority for a signaled LSP
The user can specify a priority for each signaled LSP for which this is the ingress LER. The priority
determines the relative importance of the LSP during setup or preemption. The priority for an LSP
has two components the setup priority and the hold priority.
When multiple LSPs are enabled at the same time, such as when the device is booted, LSPs that
have a higher setup priority are enabled before LSPs that have a lower setup priority.
When an LSP is assigned a high setup priority, it may preempt an LSP that is already established,
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 if it would allow the
higher priority LSP to be established successfully.
To configure LSP tunnel1 with a setup priority of 6 and hold priority of 1.
Brocade(config-mpls)# lsp tunnel1
Brocade(config-mpls-lsp)# priority 6 1
Syntax: [no] priority setup-priority / hold-priority
Possible values are 0 (highest priority) through 7 (lowest priority). An LSP setup priority must be
lower than or equal to the hold priority. The default LSP setup priority is seven, and the hold priority
is zero.
Assigning a metric to the LSP
The user can assign a metric to the LSP, which can be used by routing protocols to determine the
relative preference among several LSPs towards a given destination.
To assign a metric of five to LSP tunnel1
Brocade(config-mpls)# lsp tunnel1
Brocade(config-mpls-lsp)# metric 5
Syntax: [no] metric number
The metric has a range of 1– 65535. By default, all LSPs have a metric of one. A lower metric is
preferred over a higher one. When multiple LSPs have the same destination LSR, and they have the
same metric, the traffic load is shared among them.
Including or excluding administrative groups from LSP calculations
Administrative groups, also known as resource classes or link colors, lets the user assign
MPLS-enabled interfaces to various classes. When a device uses CSPF to calculate the path for an
LSP, it takes into account the administrative group to which an interface belongs; the user can
specify which administrative groups the device can include or exclude for this calculation.
For example, to include interfaces in either of the administrative groups “gold” and “silver” in the
path calculations for LSP tunnel1, do the following.
Brocade(config-mpls)# lsp tunnel1
Brocade(config-mpls-lsp)# include-any gold silver