display mpls last-info lsp-down

Function

The display mpls last-info lsp-down command displays information about label switched paths (LSPs) that went Down.

Format

display mpls last-info lsp-down [ protocol ldp ] [ verbose ]

Parameters

Parameter	Description	Value
protocol ldp	Displays information about LSPs that went Down.	-
verbose	Displays detailed information about LDP LSPs.	-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

If LSPs fail and enter the Down state, run the display mpls last-info lsp-down command to view the faults that cause a maximum of 64 LSPs to go Down.

Example

# Display brief information about LDP LSPs that just enter the Down state.

<sysname> display mpls last-info lsp-down

-------------------------------------------------------------------------------
                 LDP LSP Information: Host Address
-------------------------------------------------------------------------------
FEC                In/Out Label  Out Interface              Down Reason
12.12.12.12/32     1029/3        GigabitEthernet0/0/1       route changed
12.12.12.12/32     NULL/3        GigabitEthernet0/0/1       route changed
10.10.10.10/32     1034/3        GigabitEthernet0/0/0       cannot recovery from GR
10.10.10.10/32     NULL/3        GigabitEthernet0/0/0       cannot recovery from GR
10.10.10.10/32     1033/3        GigabitEthernet0/0/0       DS lost
10.10.10.10/32     NULL/3        GigabitEthernet0/0/0       DS lost

**Table 1** Description of the display mpls last-info lsp-down command output
Item	Description
FEC	Forwarding equivalence class
In/Out Label	Values of the incoming and outgoing labels
Out Interface	Outbound interface
Down Reason	Cause for the event that an LSP goes Down. It can be: route changed: A route was changed. adjacency changed: An adjacency was changed. cannot recovery from GR: The LDP LSP failed to be reestablished during GR. recv release msg: A Release message was received. US lost: The session with the upstream node went Down. DS lost: The session with the downstream node went Down. policy changed: The policy to establish LSPs was changed (Generally, configurations of the policy was changed). reach paf limit: PAF resources are insufficient. GR aging: The LSP aged after GR. others

# Display detailed information about LDP LSPs that just enter the Down state.

<sysname> display mpls last-info lsp-down protocol ldp verbose

-------------------------------------------------------------------------------
                 LDP LSP Information: Host Address
-------------------------------------------------------------------------------
  No                  :  1
  VrfIndex            :
  Fec                 :  1.1.1.1/32
  Nexthop             : 10.10.10.1
  In-Label            :  3
  Out-Label           :  NULL
  Out-Interface       :  InLoopBack0
  LspIndex            :  6144
  Token               :  0x0
  LsrType             :  Egress
  Outgoing token      :  0x0
  Label Operation     :  POP
  Down Time           :  2010/11/23 17:49:29+00:00
  Exist time          :  14sec
  Down Reason         :  policy changed

  No                  :  2
  VrfIndex            :
  Fec                 :  1.1.1.1/32
  Nexthop             : 10.10.10.1
  In-Label            :  3
  Out-Label           :  NULL
  Out-Interface       :  InLoopBack0
  LspIndex            :  6144
  Token               :  0x0
  LsrType             :  Egress
  Outgoing token      :  0x0
  Label Operation     :  POP
  Down Time           :  2010/11/23 17:49:50+00:00
  Exist time          :  9sec
  Down Reason         :  policy changed

  No                  :  3
  VrfIndex            :
  Fec                 :  2.2.2.2/32
  Nexthop             :  10.10.2.2
  In-Label            :  NULL
  Out-Label           :  3
  Out-Interface       :  InLoopBack0
  LspIndex            :  6146
  Token               :  0x1
  LsrType             :  Ingress
  Outgoing token      :  0x0
  Label Operation     :  PUSH
  Down Time           :  2010/11/23 17:49:59+00:00
  Exist time          :  5sec
  Down Reason         :  route changed

  No                  :  4
  VrfIndex            :
  Fec                 :  2.2.2.2/32
  Nexthop             :  10.10.2.2
  In-Label            :  1024
  Out-Label           :  3
  Out-Interface       :  InLoopBack0
  LspIndex            :  6147
  Token               :  0x2
  LsrType             :  Transit
  Outgoing token      :  0x0
  Label Operation     :  SWAP
  Down Time           :  2010/11/23 17:49:59+00:00
  Exist time          :  5sec
  Down Reason         :  route changed

**Table 2** Description of the display mpls last-info lsp-down protocol ldp verbose command output
Item	Description
VrfIndex	Name of a VRF instance
Fec	Forwarding equivalence class
Nexthop	Next-hop address
In-Label	Value of the incoming label
Out-Label	Value of the outgoing label
Out-Interface	Outbound interface
LspIndex	Index of an LSP
Token	Token value
LsrType	Type of an label switching routers (LSR) on an LSP, which can be ingress, transit, or egress
Outgoing token	Value of the outgoing token
Label Operation	Label operation, which can be PUSH, POP, SWAP, or SWAPPUSH
Down Time	Time when an LSP went Down
Exist time	Time when an LSP went Up
Down Reason	Cause for the event that the LSP goes Down. It can be: route changed: A route was changed. adjacency changed: An adjacency was changed. cannot recovery from GR: The LDP LSP failed to be reestablished during GR. recv release msg: A Release message was received. US lost: The session with the upstream node went Down. DS lost: The session with the downstream node went Down. policy changed: The policy to establish LSPs was changed (Generally, configurations of the policy was changed). reach paf limit: PAF resources are insufficient. GR aging: The LSP aged after GR. others