beautypg.com

Static transit lsp, Time-triggered reoptimizing, Configuring static transit lsp – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual

Page 175

background image

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide

151

53-1003031-02

Static transit LSP

1

The all option directs the router to reoptimize the paths for all LSPs configured.

The lsp option directs the router to reoptimize the path for the LSP specified by the .

NOTE

On reoptimization of an adaptive LSP, LSP accounting statistics might miss the accounting of some
of the packets.

Time-triggered reoptimizing

The user can set a timer to optimize a specific LSP path on a periodic basis. Upon expiration of this
timer, the LSP is optimized for a new path when the new path has a lower cost than the existing
path. This timer can be configured when the LSP is in a disabled state, and the timer value can be
adaptively changed when the LSP is in an enabled state by issuing a commit to take effect. Until a
commit is issued the reopt timer is disabled.

To set the LSP reoptimization timer, use the reoptimize_timer command during LSP configuration,
as the following shows.

Brocade(config)# router mpls

Brocade(config-mpls)# lsp to20

Brocade(config-mpls-lsp-to20)# reoptimize_timer 1000

Syntax: [no] reoptimize_timer seconds

The seconds variable specifies the number of seconds from the beginning of one reoptimization
attempt to the beginning of the next attempt. The range of values for seconds is 300 – 65535.

The [no] option can be used to disable a timer that has been configured. By default, a timer is not
configured.

Configuring a reoptimization timer does not interfere with running the manual reoptimize
command as described in

“Reoptimizing LSPs”

.

NOTE

When upgrading software, configured adaptive LSPs are initialized with no reoptimization timer.

NOTE

This feature does not apply to LSPs within a FRR network.

Static transit LSP

Static Transit LSP allows you to configure a transit cross-connect, consisting of the inbound-label,
an optional outbound-label, and a next-hop IPv4 address. The next-hop configured will be used to
get the outbound-interface and the interface next-hop address, and send the packet.

Configuring Static Transit LSP

To configure Static Transit LSP you will perform the following procedure: