beautypg.com

Reoptimizing lsps – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual

Page 174

background image

150

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

53-1003031-02

Configuring an adaptive LSP

1

OTHER INSTANCE PRIMARY: NEW_INSTANCE admin: DOWN, status: DOWN

Maximum retries: 0, no. of retries: 0

Setup priority: 7, hold priority: 1

Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes

Constraint-based routing enabled: yes

Tie breaking: random, hop limit: 0

Active Path attributes:

Tunnel interface: tnl1, outbound interface: e1/2

Tunnel index: 4, Tunnel instance: 1 outbound label: 3

Path calculated using constraint-based routing: yes

Explicit path hop count: 1

10.2.1.2 (S)

Recorded routes:

Protection codes: P: Local N: Node B: Bandwidth I: InUse

10.2.1.2

The following commit command makes the new parameter settings active in Adaptive LSP to20’s
configuration

Brocade(config-mpls)# lsp to20

Brocade(config-mpls-lsp-to20)# commit

Syntax: [no] commit

After the commit command runs, the user can see that the priorities have changed by using the
show mpls lsp command for lsp to20.

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: 1

Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes

Constraint-based routing enabled: yes

Tie breaking: random, hop limit: 0

Active Path attributes:

Tunnel interface: tnl1, outbound interface: e1/2

Tunnel index: 4, Tunnel instance: 2 outbound label: 3

Path calculated using constraint-based routing: yes

Explicit path hop count: 1

10.2.1.2 (S)

Recorded routes:

Protection codes: P: Local N: Node B: Bandwidth I: InUse

10.2.1.2

Reoptimizing LSPs

Under ordinary conditions, an LSP path does not change unless the path becomes inoperable.
Consequently, the router needs to be directed to consider configuration changes made to an LSP
and to optimize the LSP path based on those changes. This is accomplished using the mpls
reoptimize command as shown in the following.

Brocade# mpls reoptimize lsp to20

Syntax: [no] mpls reoptimize all | lsp lsp-name