show mpls lsp

Display information about configured and active dynamic Multiprotocol Label Switching (MPLS) label-switched paths (LSPs).

Options

none — Display standard information about all configured and active dynamic MPLS LSPs on all logical systems.

brief | detail | extensive | terse — (Optional) Display the specified level of output. The extensive option displays the same information as the detail option, but covers the most recent 50 events.

bidirectional | unidirectional — (Optional) Display bidirectional or unidirectional LSP information, respectively.

descriptions — Display the MPLS label-switched path (LSP) descriptions. To view this information, you must configure the description statement at the [edit protocol mpls lsp] hierarchy level. Only LSPs with a description are displayed. This command is only valid for the ingress router because the description is not propagated in RSVP messages.

down | up — (Optional) Display only LSPs that are inactive or active, respectively.

logical-system (all | logical-system-name) — (Optional) Perform this operation on all logical systems or on a particular logical system.

name name — (Optional) Display information about the specified LSP or group of LSPs.

statistics — (Optional) (Egress and transit routers only.) Display accounting information about LSPs. Statistics are not available for LSPs on the egress router, because the penultimate router in the LSP sets the label to 0. Also, as the packet arrives at the egress router, the hardware removes its MPLS header and the packet reverts to being an IPv4 packet. Therefore, it is counted as an IPv4 packet, not an MPLS packet.

Required Privilege Level

Field Name	Field Description	Level of Output
Ingress LSP	Information about LSPs on the ingress router. Each session has one line of output.	All levels
Egress LSP	Information about the LSPs on the egress router. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. Each session has one line of output.	All levels
Transit LSP	Number of LSPs on the transit routers and the state of these paths. MPLS learns this information by querying RSVP, which holds all the transit and egress session information.	All levels
P2MP name	Name of the point-to-multipoint LSP. Dynamically generated P2MP LSPs used for VPLS flooding use dynamically generated P2MP LSP names. The name uses the format identifier:vpls:router-id:routing-instance-name. The identifier automatically generated by JUNOS.	All levels
P2MP branch count	Number of destination LSPs the point-to-multipoint LSP is transmitting to.	All levels
P	An asterisk (*) under this heading indicates that the LSP is a primary path.	All levels
address	(Detail and Extensive) Destination (egress router) of the LSP.	detail extensive
To	Destination (egress router) of the session.	brief
From	Source (ingress router) of the session.	brief detail
State	State of the LSP handled by this RSVP session: Up, Dn (down), or Restart.	brief detail
Active Route	Number of active routes (prefixes) installed in the forwarding table. For ingress LSPs, the forwarding table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the forwarding table is the primary MPLS table (mpls.0).	detail extensive
P	Path. An asterisk (*) underneath this column indicates that the LSP is a primary path.	brief
LSPname	Name of the LSP.	brief detail
DiffServeInfo	Type of LSP: multiclass LSP (multiclass diffServ-TE LSP) or Differentiated-Services-aware traffic engineering LSP (diffServ-TE LSP).	detail
Bypass	(Bypass LSP) Destination address (egress router) for the bypass LSP.	All levels
LSPpath	Indicates whether the RSVP session is for the primary or secondary LSP path. LSPpath can be either primary or secondary and can be displayed on the ingress, egress, and transit routers.	detail
Bidir	(GMPLS) The LSP allows data to travel in both directions between GMPLS devices.	All levels
Bidirectional	(GMPLS) The LSP allows data to travel both ways between GMPLS devices.	All levels
Rt	Number of active routes (prefixes) installed in the routing table. For ingress RSVP sessions, the routing table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the routing table is the primary MPLS table (mpls.0).	brief
ActivePath	(Ingress LSP) Name of the active path: Primary or Secondary.	detail extensive
FastReroute desired	Fast reroute has been requested by the ingress router.	detail
Link protection desired	Link protection has been requested by the ingress router.	detail
LoadBalance	(Ingress LSP ) CSPF load-balancing rule that was configured to select the LSP's path among equal-cost paths: Most-fill, Least-fill, or Random.	detail extensive
Signal type	Signal type for GMPLS LSPs. The signal type determines the peak data rate for the LSP: DS0, DS3, STS-1, STM-1, or STM-4.	All levels
Encoding type	LSP encoding type: Packet, Ethernet, PDH, SDH/SONET, Lambda, or Fiber.	All levels
Switching type	Type of switching on the links needed for the LSP: Fiber, Lamda, Packet, TDM, or PSC-1.	All levels
GPID	Generalized Payload Identifier (identifier of the payload carried by an LSP): HDLC, Ethernet, IPv4, PPP, or Unknown.	All levels
Protection	Configured protection capability desired for the LSP: Extra, Enhanced, none, One plus one, One to one, or Shared.	All levels
Upstream label in	(Bidirectional LSPs) Incoming label for reverse direction traffic for this LSP.	All levels
Upstream label out	(Bidirectional LSPs) Outgoing label for reverse direction traffic for this LSP.	All levels
Suggested label received	(Bidirectional LSPs) Label the upstream node suggests to use in the Resv message that is sent.	All levels
Suggested label sent	(Bidirectional LSPs) Label the downstream node suggests to use in the Resv message that is returned.	All levels
Autobandwidth	(Ingress LSP) The LSP is performing autobandwidth allocation.	detail extensive
MinBW	(Ingress LSP) Configured minimum value of the LSP, in bps.	detail extensive
MaxBW	(Ingress LSP) Configured maximum value of the LSP, in bps.	detail extensive
AdjustTimer	(Ingress LSP) Configured value of the bandwidth adjustment timer, indicating the total amount of time allowed before bandwidth adjustment will take place, in seconds.	detail extensive
MaxAvgBW util	(Ingress LSP) Current value of the actual maximum average bandwidth utilization, in bps.	detail extensive
Overflow limit	(Ingress LSP) Configured value of the threshold overflow limit.	detail extensive
Overflow sample count	(Ingress LSP) Current value for the overflow sample count.	detail extensive
Bandwidth Adjustment in nnn second(s)	(Ingress LSP) Current value of the bandwidth adjustment timer, indicating the amount of time remaining until the bandwidth adjustment will take place, in seconds.	detail extensive
Active path indicator	(Ingress LSP) A value of * indicates that the path is active. The absence of * indicates that the path is not active. In the following example, "long" is the active path. `*Primary long Standby short`	detail extensive
Primary	(Ingress LSP) Name of the primary path.	detail extensive
Secondary	(Ingress LSP) Name of the secondary path.	detail extensive
Standby	(Ingress LSP) Name of the path in standby mode.	detail extensive
State	(Ingress LSP) State of the path: Up or Dn (down).	detail extensive
COS	(Ingress LSP) Class-of-service value.	detail extensive
Bandwidth per class	(Ingress LSP) Active bandwidth for the LSP path for each MPLS class type, in bps.	detail extensive
OptimizeTimer	(Ingress LSP) Configured value of the optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds.	detail extensive
SmartOptimizeTimer	(Ingress LSP) Configured value of the smart optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds.	detail extensive
Reoptimization in xxx seconds	(Ingress LSP) Current value of the optimize timer, indicating the amount of time remaining until the path will be reoptimized, in seconds.	detail extensive
Computed ERO (S [L] denotes strict [loose] hops)	(Ingress LSP) Computed Explicit Route. A series of hops, each with an address followed by a hop indicator. The value of the hop indicator can be strict (S) or loose (L).	detail extensive
CSPF metric	(Ingress LSP) Constrained Shortest Path First metric for this path.	detail extensive
Received RRO	(Ingress LSP) Received Record Route. A series of hops, each with an address followed by a flag. (In most cases, the Received Record Route is the same as the Computed Explicit Route. If Received RRO is different from Computed ERO, there is a topology change in the network, and the route is taking a detour.) The following flags identify the protection capability and status of the downstream node: 0x01—Local protection available. The link downstream from this node is protected by a local repair mechanism. This flag can be set only if the Local protection flag was set in the SESSION_ATTRIBUTE object of the corresponding Path message. 0x02—Local protection in use. A local repair mechanism is in use to maintain this tunnel (usually because of an outage of the link it was routed over previously). 0x03—Combination of 0x01 and 0x02. 0x04—Bandwidth protection. The downstream router has a backup path providing the same bandwidth guarantee as the protected LSP for the protected section. 0x08—Node protection. The downstream router has a backup path providing protection against link and node failure on the corresponding path section. If the downstream router can set up only a link-protection backup path, the Local protection available bit is set but the Node protection bit is cleared. 0x09—Detour is established. Combination of 0x01 and 0x08. 0x10—Preemption pending. The preempting node sets this flag if a pending preemption is in progress for the traffic engine LSP. This flag indicates to the ingress legacy edge router (LER) of this LSP that it should be rerouted. 0xb—Detour is in use. Combination of 0x01, 0x02, and 0x08.	detail extensive
Index number	(Ingress LSP) Log entry number of each LSP path event. The numbers are in chronological descending order, with a maximum of 50 index numbers displayed.	extensive
Date	(Ingress LSP) Date of the LSP event.	extensive
Time	(Ingress LSP) Time of the LSP event.	extensive
Event	(Ingress LSP) Description of the LSP event.	extensive
Created	(Ingress LSP) Date and time the LSP was created.	extensive
Resv style	(Bypass) RSVP reservation style. This field consists of two parts. The first is the number of active reservations. The second is the reservation style, which can be FF (fixed filter), SE (shared explicit), or WF (wildcard filter).	brief detail extensive
Labelin	Incoming label for this LSP.	brief detail
Labelout	Outgoing label for this LSP.	brief detail
LSPname	Name of the LSP.	brief detail
Time left	Number of seconds remaining in the lifetime of the reservation.	detail
Since	Date and time when the RSVP session was initiated.	detail
Tspec	Sender's traffic specification, which describes the sender's traffic parameters.	detail
Port number	Protocol ID and sender or receiver port used in this RSVP session.	detail
PATH rcvfrom	Address of the previous-hop (upstream) router or client, interface the neighbor used to reach this router, and number of packets received from the upstream neighbor.	detail
PATH sentto	Address of the next-hop (downstream) router or client, interface used to reach this neighbor, and number of packets sent to the downstream router.	detail
RESV rcvfrom	Address of the previous-hop (upstream) router or client, interface the neighbor used to reach this router, and number of packets received from the upstream neighbor. The output in this field, which is consistent with that in the PATH rcvfrom field, indicates that the RSVP negotiation is complete.	detail
Record route	Recorded route for the session, taken from the Record Route Object.	detail
Soft preempt	Number of soft preemptions that occurred on a path and when the last soft preemption occurred. Only successful soft preemptions are counted (those that actually resulted in a new path being used).	detail
Soft preemption pending	Path is in the process of being soft preempted. This display is removed once the ingress router has calculated a new path.	detail

show mpls lsp descriptions

user@host> show mpls lsp descriptions

Ingress LSP: 3 sessions
To              LSP name                              Description
10.0.0.195      to-sanjose                            to-sanjose-desc
10.0.0.195      to-sanjose-other-desc                 other-desc
Total 2 displayed, Up 2, Down 0

show mpls lsp detail

user@host> show mpls lsp detail

Ingress LSP: 1 sessions

10.255.245.3
  From: 10.255.245.5, State: Up, ActiveRoute: 1, LSPname: lsp-ec
  ActivePath: long-path (primary)
  LoadBalance: Random
  Autobandwidth
  MaxBW: 5Mbps
  AdjustTimer: 4800 secs AdjustThreshold: 1%
  Max AvgBW util: 0bps, Bandwidth Adjustment in 3383 second(s).
  Overflow limit: 5, Overflow sample count: 0
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary   long-path        State: Up
    SmartOptimizeTimer: 180
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 5)
 192.168.37.89 S 192.168.37.87 S
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
          192.168.37.89 192.168.37.87
Total 1 displayed, Up 1, Down 0

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

show mpls lsp extensive

user@host> show mpls lsp extensive

Ingress LSP: 5 sessions
 
10.255.71.242
  From: 10.255.71.238, State: Up, ActiveRoute: 1009, LSPname: sample-ccc
  ActivePath: path3 (primary)
  Link protection desired
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary   path3            State: Up
    OptimizeTimer: 30
    SmartOptimizeTimer: 180
    Reoptimization in 26 second(s).
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1)
 10.35.1.41 S
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
          10.35.1.41(Label=3)
   10 Dec  8 13:51:58.986 CSPF: computation result ignored
    9 Dec  8 13:51:30.547 Record Route:  10.35.1.41(Label=3)
    8 Dec  8 13:51:30.547 Up
    7 Dec  8 13:51:30.397 Originate make-before-break call
    6 Dec  8 13:51:30.397 CSPF: computation result accepted  10.35.1.41
    5 Dec  8 13:50:41.467 Selected as active path
    4 Dec  8 13:50:41.467 Record Route:  10.35.1.41(Label=3)
    3 Dec  8 13:50:41.466 Up
    2 Dec  8 13:50:41.371 Originate Call
    1 Dec  8 13:50:41.371 CSPF: computation result accepted  10.35.1.41
  Created: Fri Dec  8 13:50:40 2006
Total 1 displayed, Up 1, Down 0
 
Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
 
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

show mpls lsp p2mp

user@host> show mpls lsp p2mp

Ingress LSP: 2 sessions
P2MP name: p2mp-lsp1, P2MP branch count: 1
To              From            State Rt ActivePath       P     LSPname
10.255.245.51   10.255.245.50   Up     0 path1            *     p2mp-branch-1
P2MP name: p2mp-lsp2, P2MP branch count: 1
To              From            State Rt ActivePath       P     LSPname
10.255.245.51   10.255.245.50   Up     0 path1            *     p2mp-st-br1
Total 2 displayed, Up 2, Down 0

Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

show mpls lsp p2mp detail

user@host> show mpls lsp p2mp detail

Ingress LSP: 2 sessions
P2MP name: p2mp-lsp1, P2MP branch count: 1

10.255.245.51
  From: 10.255.245.50, State: Up, ActiveRoute: 0, LSPname: p2mp-branch-1
  ActivePath: path1 (primary)
  P2MP name: p2mp-lsp1
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary   path1            State: Up
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 25)
 192.168.208.17 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
          192.168.208.17
P2MP name: p2mp-lsp2, P2MP branch count: 1

10.255.245.51
  From: 10.255.245.50, State: Up, ActiveRoute: 0, LSPname: p2mp-st-br1
  ActivePath: path1 (primary)
  P2MP name: p2mp-lsp2
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary   path1            State: Up
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 25)
 192.168.208.17 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
          192.168.208.17
Total 2 displayed, Up 2, Down 0

Syntax

Release Information

Description