Changing the metric for an lsp – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 613
![background image](/manuals/361646/613/background.png)
Brocade(config-bgp)# next-hop-mpls compare-lsp-metric
Brocade(config-bgp)# show ip route
Total number of IP routes: 5
Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric
ISIS Codes - L1:Level-1 L2:Level-2
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link
Destination Gateway Port Cost Type Uptime
1 10.1.1.1/32 DIRECT loopback 1 0/0 D 11m30s
2 10.2.3.3/32 DIRECT loopback 2 0/0 D 11m30s
3 10.5.5.5/32 10.1.1.10 eth 1/1 1/1 S 11m19s
4 10.8.8.1/32 10.1.1.2 lsp to2 20/0 B 0m1s
10.8.8.1/32 10.10.1.2 lsp to2_sec 20/0 B 0m1s
5 10.8.8.2/32 10.1.1.2 lsp to2 20/0 B 0m1s
10.8.8.2/32 10.10.1.2 lsp to2_sec 20/0 B 0m1s
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
589
53-1003031-02
BGP shortcuts
5
Syntax: [no] next-hop-mpls [compare-lsp-metric]
Changing the metric for an LSP
In the next example, the metric for LSP to2 is changed to a value (20) that causes the system to
remove it from the routing table, so only LSP to2_sec to 10.8.8.1/32 remains. This output
illustrates this result.
Brocade(config-mpls)# lsp to2
Brocade(config-mpls-lsp-to2)# disconnect
Disconnecting signaled LSP
Brocade(config-mpls-lsp-to2)# metric 20
Brocade(config-mpls-lsp-to2)# enable
Connecting signaled LSP to2
Brocade(config-mpls)# show ip route
Total number of IP routes: 5
Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric
ISIS Codes - L1:Level-1 L2:Level-2
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link
Destination Gateway Port Cost Type Uptime
1 10.1.1.1/32 DIRECT loopback 1 0/0 D 12m23s
2 10.2.3.3/32 DIRECT loopback 2 0/0 D 12m23s
3 10.5.5.5/32 10.1.1.10 eth 1/1 1/1 S 12m12s
4 10.8.8.1/32 10.10.1.2 lsp to2_sec 20/0 B 0m6s
5 10.8.8.2/32 10.10.1.2 lsp to2_sec 20/0 B 0m6s
Disabling LSP-metric compare and checking the consequences
For the last example related to next-hop MPLS, disable LSP-metric compare using the no form of
the next-hop-mpls command and include the compare-lsp-metric option.
NOTE
When the user employs the no form with the optional compare-lsp-metric parameter for the
next-hop-mpls command, only this optional parameter is deleted, so global next-hop-mpls enable
remains the same. To disable both the optional LSP-metric compare and the global next-hop-mpls,
use the [no] form of the next-hop-mpls command without the optional parameter.