Step 1: Check the Status of the LSP

Action

To determine the LSP status, on the ingress router, enter the following JUNOS command-line interface (CLI) operational mode command:

user@host> show mpls lsp

Sample Output

user@R1> show mpls lsp 

Ingress LSP: 1 sessions

To              From            State Rt ActivePath       P     LSPname

10.0.0.6        10.0.0.1        Up     1                  *     R1-to-R6

Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions

To              From            State Rt Style Labelin Labelout LSPname 

10.0.0.1        10.0.0.6        Up     0 1 FF       3        - R6-to-R1

Total 1 displayed, Up 1, Down 0

Transit LSP: 0 sessions

Total 0 displayed, Up 0, Down 0

What It Means

The sample output is from the ingress router (R1), and shows ingress, egress, and transit LSP information. Ingress information is for the sessions that originate from this router, egress information is for sessions that terminate on this router, and transit information is for sessions that transit through this router.

There is one ingress route from R1 (10.0.0.1) to R6 (10.0.0.6). This route is currently up, and is an active route installed in the routing table (Rt). The LSP R1-to-R6 is the primary path (P) as opposed to the secondary path, and is indicated by an asterisk (*). The route to R6 does not contain a named path (ActivePath).

There is one egress LSP from R6 to R1. The State is up, with no routes installed in the routing table. RSVP reservation style (Style) consists of two parts. The first is the number of active reservations (1). The second is the reservation style, which is FF (fixed filter). The reservation style can be FF, SE (shared explicit), or WF (wildcard filter). There are three incoming labels (Labelin) and no labels going out (Labelout) for this LSP.

There are no transit LSPs.

For more information on checking the LSP state, see Working with the Layered MPLS Troubleshooting Model.