Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

show mpls container-lsp

Syntax

Description

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

Options

none

Display standard information about all configured and active member LSPs of the container LSP.

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.

count-active-routes

(Optional) Show active routes for the container LSP.

defaults

(Optional) Display the default settings of the container LSP.

descriptions

(Optional) Display the container LSP descriptions. To view this information, you must configure the description statement at the [edit protocol mpls container-lsp] hierarchy level. Only the 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.

egress

(Optional) Display the LSPs ending at this device.

Note:

The egress option displays all the LSPs including regular LSPs, members of container LSPs, and transit LSPs. This is an expected behavior for all platforms.

ingress

(Optional) Display the member LSPs originating from this device.

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

transit

(Optional) Display LSPs transiting this routing device.

unidirectional

(Optional) Display unidirectional LSP information.

Required Privilege Level

view

Output Fields

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

Table 1: show mpls container-lsp Output Fields

Field Name

Field Description

Level of Output

Ingress LSP

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

All levels

Container LSP name

Name of the container LSP.

All levels

Member LSP count

Number of member LSPs in the container LSP.

All levels

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)

  • Restart

brief detail

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 member LSP.

brief detail

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

Min LSPs

Minimum number of member LSPs.

Default: 1

extensive

Max LSPs

Number of member LSPs that the container LSP can have at maximum.

Default: 64 (due to ECMP limit)

extensive

Aggregate bandwidth

Sum of the bandwidths of all member LSPs.

extensive

NormalizeTimer

Duration between two normalization events.

When not configured, 21600 seconds (6 hours) is set as the default value.

extensive

NormalizeThreshold

Change in aggregate LSP utilization to trigger splitting or merging expressed in percentage.

extensive

Max Signaling BW

Maximum bandwidth used to signal LSPs after a normalization event.

Default value is 0 bps. When not configured, the value is inherited from the splitting bandwidth configuration.

Note:

Between two normalization events, when auto-bandwidth adjustment happens, the per-LSP auto-bandwidth configuration and thresholds are used, instead of the maximum signaling bandwidth threshold.

extensive

Min Signaling BW

Minimum bandwidth used to signal LSPs after a normalization event.

Default value is 0 bps. When not configured, the value is inherited from the merging bandwidth configuration.

Note:

Between two normalization events, when auto-bandwidth adjustment happens, the per-LSP auto-bandwidth configuration and thresholds are used, instead of the minimum signaling bandwidth threshold.

extensive

Splitting BW

Bandwidth used for LSP splitting and merging.

Default value is 0 bps. When not configured, the value is inherited from the auto-bandwidth maximum bandwidth configuration.

extensive

Merging BW

Bandwidth used for LSP splitting and merging.

Default value is 0 bps. When not configured, the value is inherited from the auto-bandwidth minimum bandwidth configuration.

extensive

LSPtype

Type of LSP.

extensive

LoadBalance

Loadbalanced bandwidth.

extensive

MinBW

Minimum LSP bandwidth in bps related to auto-bandwidth.

extensive

AdjustTimer

Total amount of time in seconds allowed before LSP bandwidth adjustment take place.

Range: 300 through 315360000 seconds

extensive

Max AvgBW util

Current value of the actual maximum average bandwidth utilization in bps.

extensive

Overflow limit

Threshold overflow limit.

extensive

Underflow limit

Threshold underflow limit.

extensive

Priorities

Setup priority and hold priority values.

For setup priority, 0 and 7 is the highest and lowest priority, respectively.

When not explicitly configured, 7 and 0 are set as the default values for the setup priority and hold priority, respectively.

extensive

SmartOptimizeTimer

Time in seconds allowed before path reoptimization.

extensive

Computed ERO

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

extensive

Received RRO

Received record route.

RRO is a series of hops, each with an address followed by a flag. In most cases, the received RRO is the same as the computed ERO. If the received RRO is different from the 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.

extensive

Created

Date and time the LSP was created.

extensive

Sample Output

show mpls container-lsp

show mpls container-lsp extensive

Release Information

Command introduced in Junos OS Release 14.2.

Statement introduced for QFX Switches in Junos OS Release 15.1X53-D30.