Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show mpls lsp

 

List of Syntax

Syntax

Syntax (EX Series Switches)

Syntax

Syntax (EX Series Switches)

Release Information

Command introduced before Junos OS Release 7.4.

defaults option added in Junos OS Release 8.5.

Command introduced in Junos OS Release 9.5 for EX Series switches.

autobandwidth option added in Junos OS Release 11.4.

externally-controlled option added in Junos OS Release 12.3.

externally-provisioned option added in Junos OS Release 13.3.

Command introduced in Junos OS Release 13.2X51-D15 for QFX Series.

instance instance-name option added in Junos OS Release 15.1.

Description

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

Options

noneDisplay standard information about all configured and active dynamic MPLS LSPs.
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.

In the extensive command output, the duplicate back-to-back messages are recorded as aggregated messages. An additional timestamp is included for these aggregated messages, where if the aggregated messages are five or less, timestamp deltas are recorded for each message, and if the aggregated messages are greater than five, the first and last timestamp is recorded.

For example:

  • All timestamps

  • Timestamp deltas

  • First and last timestamp

abstract-computation(Optional) Display abstract computation preprocessing for LSPs.

See show mpls lsp abstract-computation for more details.

autobandwidth(Optional) Display automatic bandwidth information. This option is explained separately (see show mpls lsp autobandwidth).
bidirectional | unidirectional(Optional) Display bidirectional or unidirectional LSP information, respectively.
bypass(Optional) Display LSPs used for protecting other LSPs.
count-active-routes(Optional) Display active routes for LSPs.
defaults(Optional) Display the MPLS LSP default settings.
descriptions(Optional) 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 routing device, because the description is not propagated in RSVP messages.
down | up(Optional) Display only LSPs that are inactive or active, respectively.
externally-controlled(Optional) Display the LSPs that are under the control of an external Path Computation Element (PCE).
externally-provisioned(Optional) Display the LSPs that are generated dynamically and provisioned by an external Path Computation Element (PCE).
instance instance-name(Optional) Display MPLS LSP information for the specified instance. If instance-name is omitted, MPLS LSP information is displayed for the master instance.
locally-provisioned(Optional) Display LSPs that have been provisioned locally by the Path Computation Client (PCC).
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.
lsp-type(Optional) Display information about a particular LSP type:
  • bypass—Sessions for bypass LSPs.

  • egress—Sessions that terminate on this routing device.

  • ingress—Sessions that originate from this routing device.

  • pop-and-forward—Sessions that originate from RSVP-TE pop-and-forward LSP tunnels.

  • transit—Sessions that pass through this routing device.

name name(Optional) Display information about the specified LSP or group of LSPs.
p2mp(Optional) Display information about point-to-multipoint LSPs.
reverse-statistics(Optional) Display packet statistics for reverse direction of LSPs.
segment(Optional) Display segment identifier (SID) labels.
statistics(Optional) (Ingress and transit routers only) Display accounting information about LSPs. Statistics are not available for LSPs on the egress routing device, because the penultimate routing device in the LSP sets the label to 0. Also, as the packet arrives at the egress routing device, 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.
Note

If a bypass LSP is configured for the primary static LSP, display cumulative statistics of packets traversing through the protected LSP and bypass LSP when traffic is re-optimized when the protected LSP link is restored. (Bypass LSPs are not supported on QFX Series switches.)

When used with the bypass option (show mpls lsp bypass statistics), display statistics for the traffic that flows only through the bypass LSP.

transit(Optional) Display LSPs transiting this routing device.

Required Privilege Level

view

List of Sample Output

show mpls lsp defaults

show mpls lsp descriptions

show mpls lsp detail

show mpls lsp detail (When Egress Protection Is in Standby Mode)

show mpls lsp detail (When Egress Protection Is in Effect During a Local Repair)

show mpls lsp extensive

show mpls lsp ingress extensive

show mpls lsp extensive (automatic bandwidth adjustment enabled)

show mpls lsp bypass extensive

show mpls lsp p2mp

show mpls lsp p2mp detail

show mpls lsp detail count-active-routes

show mpls lsp statistics extensive

Output Fields

Table 1 describes the output fields for the show mpls lsp command. Output fields are listed in the approximate order in which they appear.

Table 1: show mpls lsp Output Fields

Field Name

Field Description

Level of Output

Ingress LSP

Information about LSPs on the ingress routing device. Each session has one line of output.

All levels

Egress LSP

Information about the LSPs on the egress routing device. 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 routing devices 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 is automatically generated by Junos OS.

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 routing device) of the LSP.

detail extensive

To

Destination (egress routing device) of the session.

brief

From

Source (ingress routing device) 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

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

P

Path. An asterisk (*) underneath this column indicates that the LSP is a primary path.

brief

ActivePath

(Ingress LSP) Name of the active path: Primary or Secondary.

detail extensive

LSPname

Name of the LSP.

brief detail

Statistics

Displays the number of packets and the number of bytes transmitted over the LSP. These counters are reset to zero whenever the LSP path is optimized (for example, during an automatic bandwidth allocation).

extensive

Aggregate statistics

Displays the number of packets and the number of bytes transmitted over the LSP. These counters continue to iterate even if the LSP path is optimized. You can reset these counters to zero using the clear mpls lsp statistics command.

extensive

Packets

Displays the number of packets transmitted over the LSP.

brief extensive

Bytes

Displays the number of bytes transmitted over the LSP.

brief extensive

DiffServeInfo

Type of LSP: multiclass LSP (multiclass diffServ-TE LSP) or Differentiated-Services-aware traffic engineering LSP (diffServ-TE LSP).

detail

LSPtype

Type of LSP:

  • Static configured—Static

  • Dynamic configured—Dynamic

  • Externally controlled—External path computing entity

Also indicates if the LSP is a Penultimate hop popping LSP or an Ultimate hop popping LSP.

detail extensive

Bypass

(Bypass LSP) Destination address (egress routing device) 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 routing devices.

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

FastReroute desired

Fast reroute has been requested by the ingress routing device.

detail

Link protection desired

Link protection has been requested by the ingress routing device.

detail

Node/Link protection desired

Link protection has been requested by the ingress routing device.

detail

LSP Control Status

(Ingress LSP) LSP control mode:

  • External—By default, all PCE-controlled LSPs are under external control. When an LSP is under external control, the PCC uses the PCE-provided parameters to set up the LSP.

  • Local—A PCE-controlled LSP can come under local control. When the LSP switches from external control to local control, path computation is done using the CLI-configured parameters and constraint-based routing. Such a switchover happens only when there is a trigger to re-signal the LSP. Until then, the PCC uses the PCE-provided parameters to signal the PCE-controlled LSP, although the LSP remains under local control.

A PCE-controlled LSP switches to local control from its default external control mode in cases such as no connectivity to a PCE or when a PCE returns delegation of LSPs back to the PCC.

extensive

External Path CSPF status

(PCE-controlled LSPs) Status of the PCE-controlled LSP with per path attributes:

  • Local

  • External

extensive

Externally Computed ERO

(PCE-controlled LSPs) Externally computed explicit route when the route object is not null or empty. 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).

extensive

EXTCTRL_LSP

(PCE-controlled LSPs) Display path history including the bandwidth, priority, and metric values received from the external controller.

extensive

flap counter

Counts the number of times a LSP flaps down or up.

extensive

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 interface 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

Mbb counter

Counts the number of times a LSP incurs MBB.

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

Dynamic MinBW

(Ingress LSP) Displays the current dynamically specified minimum bandwidth allocation for the LSP, in bps.

detail extensive

Dynamic MinBW

(Ingress LSP) Displays the current dynamically specified minimum bandwidth allocation for the LSP, in bps.

detail extensive

AdjustTimer

(Ingress LSP) Configured value for the adjust-timer statement, indicating the total amount of time allowed before bandwidth adjustment will take place, in seconds.

detail extensive

Adjustment Threshold

(Ingress LSP) Configured value for the adjust-threshold statement. Specifies how sensitive the automatic bandwidth adjustment for an LSP is to changes in bandwidth utilization.

detail extensive

Time for Next Adjustment

(Ingress LSP) Time in seconds until the next automatic bandwidth adjustment sample is taken.

detail extensive

Time of Last Adjustment

(Ingress LSP) Date and time since the last automatic bandwidth adjustment was completed.

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

Underflow limit

(Ingress LSP) Configured value of the threshold underflow limit.

detail extensive

Underflow sample count

(Ingress LSP) Current value for the underflow sample count.

detail extensive

Underflow Max AvgBW

(Ingress LSP) The highest sample bandwidth among the underflow samples recorded currently. This is the signaling bandwidth if an adjustment occurs because of an underflow.

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

Priorities

(Ingress LSP) Configured value of the setup priority and the hold priority respecitively (the setup priority is displayed first), where 0 is the highest priority and 7 is the lowest priority. If you have not explicitly configured these values, the default values are displayed (7 for the setup priority and 0 for the hold priority).

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 routing device has a backup path providing the same bandwidth guarantee as the protected LSP for the protected section.

  • 0x08—Node protection. The downstream routing device has a backup path providing protection against link and node failure on the corresponding path section. If the downstream routing device 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.

  • 0x20—Node ID. Indicates that the address specified in the RRO’s IPv4 or IPv6 sub-object is a node ID address, which refers to the router address or router ID. Nodes must use the same address consistently.

  • 0xb—Detour is in use. Combination of 0x01, 0x02, and 0x08.

detail extensive

Labels

Labels of pop-and-forward LSP tunnel:

  • P—Pop labels.

  • D—Delegation labels.

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) routing device 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) routing device or client, interface used to reach this neighbor, and number of packets sent to the downstream routing device.

detail

RESV rcvfrom

Address of the previous-hop (upstream) routing device or client, interface the neighbor used to reach this routing device, 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

Pop-and-forward

Attributes of the pop-and-forward LSP tunnel.

extensive

ETLD In

Number of transport labels that the LSP-Hop can potentially receive from its upstream hop. It is recorded as Effective Transport Label Depth (ETLD) at the transit and egress devices.

extensive

ETLD Out

Number of transport labels the LSP-Hop can potentially send to its downstream hop. It is recorded as ETLD at the transit and ingress devices.

extensive

Delegation hop

Specifies if the transit hop is selected as a delegation label:

  • Yes

  • No

extensive

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

MPLS-TE LSP Defaults

Default settings for MPLS traffic engineered LSPs:

  • LSP Holding Priority—Determines the degree to which an LSP holds on to its session reservation after the LSP has been set up successfully.

  • LSP Setup Priority—Determines whether a new LSP that preempts an existing LSP can be established.

  • Hop Limit—Specifies the maximum number of routers the LSP can traverse (including the ingress and egress).

  • Bandwidth—Specifies the bandwidth in bits per second for the LSP.

  • LSP Retry Timer—Length of time in seconds that the ingress router waits between attempts to establish the primary path.

defaults

The XML tag name of the bandwidth tag under the auto-bandwidth tag has been updated to maximum-average-bandwidth . You can see the new tag when you issue the show mpls lsp extensive command with the | display xml pipe option. If you have any scripts that use the bandwidth tag, ensure that they are updated to maximum-average-bandwidth.

Sample Output

show mpls lsp defaults

user@host> show mpls lsp defaults

show mpls lsp descriptions

user@host> show mpls lsp descriptions

show mpls lsp detail

user@host> show mpls lsp detail

show mpls lsp detail (When Egress Protection Is in Standby Mode)

user@host> show mpls lsp detail

show mpls lsp detail (When Egress Protection Is in Effect During a Local Repair)

user@host> show mpls lsp detail

show mpls lsp extensive

user@host> show mpls lsp extensive

show mpls lsp ingress extensive

user@host> show mpls lsp ingress extensive

show mpls lsp extensive (automatic bandwidth adjustment enabled)

user@host> show mpls lsp extensive

show mpls lsp bypass extensive

user@host # show mpls lsp bypass extensive

show mpls lsp p2mp

user@host> show mpls lsp p2mp

show mpls lsp p2mp detail

user@host> show mpls lsp p2mp detail

show mpls lsp detail count-active-routes

user@host> show mpls lsp detail count-active-routes

show mpls lsp statistics extensive

user@host> show mpls lsp statistics extensive