Display CSPF Fate-Sharing Group Configuration

To display CSPF fate-sharing group information for a specific CSPF group, use the show running-config router mpls cspf-group cspf-group name command. The output from the show running-config router mpls command. In the following example output, the CSPF fate-sharing group information is displayed for CSPF group gold.

device# show running-config router mpls cspf-group gold
cspf-group gold
penalty 65535
node 10.7.7.3
node 10.7.7.8

Fate-sharing group membership for any given TE link or node consists of its own membership to the group, and the TE node to which it belongs. The output from the show mpls te database detail command is enhanced to display the fate-sharing groups to which the TE links or nodes belong. In the following example output, node 10.20.20.20 displays fate-sharing group information for group1/100 and group2/10.

TE Router ID: 30.11.1.30
 OSPF Area: 0.0.0.0
  Node Id: (14.1.2.3), Type: Router
   P2P Link: From: 14.1.2.3 To: 13.13.13.13, Local: 13.14.1.14, Remote: 13.14.1.13, LSA Id: 16777313, Gen:927
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec
   P2P Link: From: 14.1.2.3 To: 13.13.13.13, Local: 13.14.20.14, Remote: 13.14.20.13, LSA Id: 16777314, Gen:916
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec
   P2P Link: From: 14.1.2.3 To: 19.19.19.19, Local: 19.14.1.14, Remote: 19.14.1.19, LSA Id: 16777223, Gen:934
    Admin Group: 0x0
    IGP Metric: 1
    TE 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
   P2P Link: From: 14.1.2.3 To: 57.57.57.57, Local: 14.57.1.14, Remote: 14.57.1.57, LSA Id: 16777241, Gen:886
    Admin Group: 0x0
    IGP Metric: 1
    TE 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
  Node Id: (4.4.4.4), Type: Router
   P2P Link: From: 4.4.4.4 To: 17.17.17.17, Local: 23.45.67.8, Remote: 23.45.67.17, LSA Id: 16777220, Gen:938
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec
  Node Id: (13.13.13.13), Type: Router
   P2P Link: From: 13.13.13.13 To: 14.1.2.3, Local: 13.14.1.13, Remote: 13.14.1.14, LSA Id: 16777218, Gen:928
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec
   P2P Link: From: 13.13.13.13 To: 14.1.2.3, Local: 13.14.20.13, Remote: 13.14.20.14, LSA Id: 16777219, Gen:915
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec
   P2P Link: From: 13.13.13.13 To: 11.12.13.14, Local: 11.13.1.13, Remote: 11.13.1.11, LSA Id: 16777220, Gen:919
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec
   P2P Link: From: 13.13.13.13 To: 11.12.13.14, Local: 11.13.2.13, Remote: 11.13.2.11, LSA Id: 16777221, Gen:921
    Admin Group: 0x0
    IGP Metric: 1
    TE Metric: 1
    Link BW: 1000000 kbits/sec
    Reservable BW: 1000000 kbits/sec
    Unreserved BW:
     [0]    1000000 kbits/sec   [1]    1000000 kbits/sec
     [2]    1000000 kbits/sec   [3]    1000000 kbits/sec
     [4]    1000000 kbits/sec   [5]    1000000 kbits/sec
     [6]    1000000 kbits/sec   [7]    1000000 kbits/sec

The show running-config router mpls lsp lsp_name command displays detailed information about a specific LSP name. The output from the show mpls lsp name lsp_name 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 the fate-sharing group information is applied, "yes" is displayed in the field. 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, the fate-sharing group information is applied to LSP test2.

device# show  mpls lsp name lsp_name test2
LSP test2, to 10.100.100.100
 From: 10.20.20.20, admin: UP, status: UP, tunnel interface(primary path): tnl3
 Times primary LSP goes up since enabled: 1
 Metric: 0, number of installed aliases: 0 Adaptive
 Maximum retries: NONE, no. of retries: 0
 Pri. path: NONE, up: yes, active: yes
 Setup priority: 7, hold priority: 0
 Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
 Constraint-based routing enabled: yes
 Tie breaking: random, hop limit: 0
 LDP tunneling enabled: no
 Sec. path: path2, active: no
  Hot-standby: yes, status: up
  Setup priority: 7, hold priority: 0
  Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
  Constraint-based routing enabled: yes
  Fate-sharing group applied: yes
  hop limit: 0
 Active Path attributes:
  Tunnel interface: tnl3, outbound interface: e1/1
  Tunnel index: 2, Tunnel instance: 1 outbound label: 3
  Path calculated using constraint-based routing: yes
  Path calculated using interface constraint: no
  Recorded routes:
   Protection codes: P: Local N: Node B: Bandwidth I: InUse
   10.1.1.1

In the following example output, the primary LSP path, and the secondary bypass LSP path is UP. The add-penalty parameter is enabled under the CSPF group computation mode as highlighted below.

device# show  mpls lsp name lsp_name test2
LSP test2, to 10.100.100.100
 From: 10.20.20.20, admin: UP, status: UP, tunnel interface(primary path): tnl3
 Times primary LSP goes up since enabled: 1
 Metric: 0, number of installed aliases: 0 Adaptive
 Maximum retries: NONE, no. of retries: 0
 Pri. path: NONE, up: yes, active: yes
 ...
Sec. path: path2, active: no
 Hot-standby: yes, status: up
  Setup priority: 7, hold priority: 0
  Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
  Constraint-based routing enabled: yes
 Path cspf-group computation-mode: add-penalty