Displaying LSP Status Events

Purpose

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

Action

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

user@host> show mpls lsp extensive

Sample Output 1

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

    Will be enqueued for recomputation in 3 second(s).

   68 Jan  5 10:02:56 CSPF failed: no route toward 10.0.0.6[9 times]

   67 Jan  5 09:58:33 Deselected as active

   66 Jan  5 09:58:33 CSPF failed: no route toward 10.0.0.6

   65 Jan  5 09:58:33 Clear Call

   64 Jan  5 09:58:33 Session preempted

   63 Jan  5 09:58:33 Down

   62 Jan  5 09:58:32 CSPF failed: no route toward 10.0.0.6[2 times]

   61 Jan  5 09:57:55 10.1.36.2: Explicit Route: wrong delivery

   60 Jan  5 09:57:34 CSPF failed: no route toward 10.0.0.6[2 times]

   59 Jan  5 09:57:28 CSPF: link down/deleted 
10.1.36.1(R3.00/10.0.0.3)->10.1.36.2(R6.00/10.0.0.6)

   58 Jan  5 09:54:37 Selected as active path

   57 Jan  5 09:54:37 Record Route:  10.1.13.2 10.1.36.2

   56 Jan  5 09:54:37 Up

   55 Jan  5 09:54:37 Originate Call

   54 Jan  5 09:54:37 CSPF: computation result accepted

   53 Jan  4 18:11:28 CSPF failed: no route toward 10.0.0.6[2 times]

   52 Jan  4 18:10:44 Deselected as active

   51 Jan  4 18:10:44 CSPF failed: no route toward 10.0.0.6

   50 Jan  4 18:10:44 CSPF: link down/deleted 
10.1.13.1(R1.00/10.0.0.1)->10.1.13.2(R3.00/10.0.0.3)

   49 Jan  4 18:10:44 RSVP Disabled

   48 Jan  4 18:10:44 RSVP error, subcode 4: protocol shutdown

   47 Jan  4 18:10:44 Down

   46 Jan  4 18:06:15 Up

   45 Jan  4 18:06:15 Down

   44 Jan  4 18:06:10 Selected as active path

   43 Jan  4 18:06:09 Record Route:  10.1.13.2 10.1.36.2

   42 Jan  4 18:06:09 Up

   41 Jan  4 18:06:09 Originate Call

   40 Jan  4 18:06:09 CSPF: computation result accepted

   39 Jan  4 18:05:40 CSPF failed: no route toward 10.0.0.6[2 times]

   38 Jan  4 18:04:57 Deselected as active

   37 Jan  4 18:04:57 CSPF failed: no route toward 10.0.0.6

   36 Jan  4 18:04:57 CSPF: link down/deleted 
10.1.13.1(R1.00/10.0.0.1)->10.1.13.2(R3.00/10.0.0.3)

   35 Jan  4 18:04:57 CSPF failed: no route toward 10.0.0.6

   34 Jan  4 18:04:57 Clear Call

   33 Jan  4 18:04:57 Explicit Route: bad strict route

   32 Jan  4 18:04:57 No Route toward dest

   31 Jan  4 18:04:57 Down

   30 Dec 28 13:47:29 Selected as active path

   29 Dec 28 13:47:29 Record Route:  10.1.13.2 10.1.36.2

   28 Dec 28 13:47:29 Up

   27 Dec 28 13:47:29 Originate Call

   26 Dec 28 13:47:29 CSPF: computation result accepted

   25 Dec 28 13:46:59 CSPF failed: no route toward 10.0.0.6

   24 Dec 28 13:46:39 Deselected as active

   23 Dec 28 13:46:39 CSPF failed: no route toward 10.0.0.6

   22 Dec 28 13:46:39 Clear Call

   21 Dec 28 13:46:39 ResvTear received

   20 Dec 28 13:46:39 Down

   19 Dec 28 13:46:39 10.1.13.2: Session preempted

Created: Mon Dec 13 11:47:18 2004

Total 1 displayed, Up 0, Down 1

[...Output truncated...]

Sample Output 2

user@R1> show mpls lsp extensive

[...Output truncated...]

*Primary use-TOKYO       State: Up, No-decrement-ttl

    Received RRO:

         10.222.28.2(flag=0x9) 10.222.4.2(flag=0x1) 10.222.44.2

    7 Sep 20 18:13:45 Record Route: 10.222.28.2(flag=0x9)

10.222.4.2(flag=0x1) 10.222.44.2

    6 Sep 20 18:13:45 Record Route: 10.222.28.2(flag=0x9)

10.222.4.2 10.222.44.2 

    5 Sep 20 18:13:45 Fast-reroute Detour Up

    4 Sep 20 18:13:42 Selected as active path

    3 Sep 20 18:13:42 Record Route: 10.222.28.2 10.222.4.2 

10.222.44.2 

    2 Sep 20 18:13:42 Up 

    1 Sep 20 18:13:42 Originate Call 

Sample Output 3

user@R1> show mpls lsp extensive

[...Output truncated...]

*Primary   long             State: Up, COS: 6

    Bandwidth per class: <ct0 20Mbps> <ct1 2Mbps> <ct2 3Mbps>

    OptimizeTimer: 250

    Reoptimization in 237 second(s).

    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 50)

          10.35.38.2 S 192.168.135.29 S 10.35.39.1 S 10.35.40.2 S 10.35.41.1 S

    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node

10=SoftPreempt):

          10.35.38.2 (flag=0x09) 192.168.135.29 (flag=0x10) 10.35.39.1 

   (flag=0x01) 10.35.40.2 (flag=0x01) 10.35.41.1 (flag=0x01)

[...Output truncated...]

What It Means

Sample Output 1 from ingress router R1 shows extensive ingress LSP information, including LSP events that led to an LSP failure and the 50 most recent state events.

LSP events in bold are described in this chapter. Descriptions include sample output of the LSP event, an explanation of what the event means, the possible cause of the event, and any possible actions that you can take.

For completeness, events not included in this example output are also described in this chapter to show LSP events that did not occur in the example network configuration, but might occur in your network. The LSP events are organized alphabetically.

Sample Output 2 shows the state of the route received in the Received Record Route (Received RRO) created by fast reroute configurations in the network. The Received RRO indicates a series of hops. Each hop has an address followed by a flag. For more information on flags, see the JUNOS MPLS Network Operations Guide. In most cases, the Received RRO is the same as the computed Explicit Route Object (ERO).

Sample Output 3 shows a Computed ERO and a Received RRO. In this instance they are the same. However, if Received RRO is different from the Computed ERO, there is a topology change in the network, and the route is taking a detour.