Displaying General LSP Error Events

Purpose

Display extensive information about LSPs, including the 50 most recent history events and the possible reasons why an LSP failed.

Action

To examine error messages, enter the following JUNOS command-line interface (CLI) operational mode command from the ingress router:

user@host> show mpls lsp extensive

Sample Output

user@R1# run show mpls lsp extensive

Ingress LSP: 1 sessions

10.0.0.6

  From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6

  ActivePath: (none)

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

  Primary                    State: Dn, No-decrement-ttl

    Bandwidth: 100Mbps 

   14 Jan 21 15:43:39 Requested bandwidth unavailable[3 times]

   13 Jan 21 15:43:21 Deselected as active

   12 Jan 21 15:43:21 Requested bandwidth unavailable

   11 Jan 21 15:43:21 Clear Call

   10 Jan 21 15:42:32 Selected as active path

    9 Jan 21 15:42:32 Record Route:  10.1.12.2 10.1.26.2

    8 Jan 21 15:42:32 Up

[...Output truncated...]

What It Means

The sample output from ingress router R1 is a section from the complete output. Typically, the output includes LSP events that led to an LSP failure and the 50 most recent state events. Only one example of a general LSP error event is displayed because it is impossible to provide all of the events described in this chapter in one sequence of log history. For a detailed description of this error event, see Requested Bandwidth Unavailable Event.

For completeness, events not generated by the example network used throughout this book are described to show LSP events that might occur in your network. The output for these events includes the prompt user@host rather than the usual user@R1 prompt.