Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 103
Brocade# show mpls ted database detail
This Router is 10.100.100.100
Global Link Gen 21
Area 0
NodeID: 10.20.20.20, Type: Router
info from applied local policies:
cspf-group member information (name/penalty):
group1/100
Type: P2P, To: 10.1.1.1, Local: 10.1.1.2, Remote: 10.1.1.1, Gen 16
Admin Group: 0x00000000
Metric: 1
Link BW: 10000000 kbits/sec
Reservable BW: 10000000 kbits/sec
Unreserved BW:
[0] 10000000 kbits/sec [1] 10000000 kbits/sec
[2] 10000000 kbits/sec [3] 10000000 kbits/sec
[4] 10000000 kbits/sec [5] 10000000 kbits/sec
[6] 10000000 kbits/sec [7] 10000000 kbits/sec
info from applied local policies:
cspf-group member information (name/penalty):
group2/10
Type: P2P, To: 10.1.2.1, Local: 10.1.2.2, Remote: 10.1.2.1, Gen 13
Admin Group: 0x00000000
Metric: 1
Link BW: 10000000 kbits/sec
Reservable BW: 10000000 kbits/sec
Unreserved BW:
[0] 10000000 kbits/sec [1] 10000000 kbits/sec
[2] 10000000 kbits/sec [3] 10000000 kbits/sec
[4] 10000000 kbits/sec [5] 10000000 kbits/sec
[6] 10000000 kbits/sec [7] 10000000 kbits/sec
Type: M/A, To: 1.1.3.1, Local: 1.1.3.2, Remote: 1.1.3.1, Gen 19
Admin Group: 0x00000000
Metric: 1
Link BW: 10000000 kbits/sec
Reservable BW: 10000000 kbits/sec
Unreserved BW:
[0] 10000000 kbits/sec [1] 10000000 kbits/sec
[2] 10000000 kbits/sec [3] 10000000 kbits/sec
[4] 10000000 kbits/sec [5] 10000000 kbits/sec
[6] 10000000 kbits/sec [7] 10000000 kbits/sec
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
79
53-1003031-02
MPLS CSPF fate-sharing group
1
Syntax: show mpls ted database detail
The show mpls lsp lsp_name command displays detailed information about a specific LSP name.
The output from the show mpls lsp lsp_name command is enhanced to display whether the
fate-sharing group information is applied to the path computation for a specified LSP. When
fate-sharing group information is applied, “yes” is displayed in the field, Fate-sharing group applied.
When fate-sharing group information is not applied, “no” is displayed in the field. Fate-sharing
group information can also be applied to the path computation for a secondary LSP or a bypass
LSP path. In the following example, fate-sharing group information is applied to LSP test2.