Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

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 OS command-line interface (CLI) operational mode command from the ingress router:

Sample Output 1

Sample Output 2

Sample Output 3

Meaning

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 topic. 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 topic 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.