show mpls lsp

Ingress LSP

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

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.

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.

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.

P2MP branch count

Number of destination LSPs the point-to-multipoint LSP is transmitting to.

P

An asterisk (*) under this heading indicates that the LSP is a primary path.

address

(detail and extensive) Destination (egress routing device) of the LSP.

To

Destination (egress routing device) of the session.

From

Source (ingress routing device) of the session.

State

State of the LSP handled by this RSVP session: Up, Dn (down), or Restart.

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

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

P

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

ActivePath

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

LSPname

Name of the LSP.

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

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.

Packets

Displays the number of packets transmitted over the LSP.

NA is shown on egress LSP if incoming label is in the reserved range of 0 -15

Bytes

Displays the number of bytes transmitted over the LSP.

NA is shown on egress LSP if incoming label is in the reserved range of 0 -15

DiffServeInfo

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

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.

Bypass

(Bypass LSP) Destination address (egress routing device) for the bypass LSP.

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.

Bidir

(GMPLS) The LSP allows data to travel in both directions between GMPLS devices.

Bidirectional

(GMPLS) The LSP allows data to travel both ways between GMPLS devices.

FastReroute desired

Fast reroute has been requested by the ingress routing device.

Link protection desired

Link protection has been requested by the ingress routing device.

Node/Link protection desired

Link protection has been requested by the ingress routing device.

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.

External Path CSPF status

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

• Local

• External

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

EXTCTRL_LSP

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

flap counter

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

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.

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.

Encoding type

LSP encoding type: Packet, Ethernet, PDH, SDH/SONET, Lambda, or Fiber.

Switching type

Type of switching on the links needed for the LSP: Fiber, Lamda, Packet, TDM, or PSC-1.

GPID

Generalized Payload Identifier (identifier of the payload carried by an LSP): HDLC, Ethernet, IPv4, PPP, or Unknown.

Protection

Configured protection capability desired for the LSP: Extra, Enhanced, none, One plus one, One to one, or Shared.

Upstream label in

(Bidirectional LSPs) Incoming label for reverse direction traffic for this LSP.

Upstream label out

(Bidirectional LSPs) Outgoing label for reverse direction traffic for this LSP.

Suggested label received

(Bidirectional LSPs) Label the upstream interface suggests to use in the Resv message that is sent.

Suggested label sent

(Bidirectional LSPs) Label the downstream node suggests to use in the Resv message that is returned.

Autobandwidth

(Ingress LSP) The LSP is performing autobandwidth allocation.

Mbb counter

Counts the number of times a LSP incurs MBB.

MinBW

(Ingress LSP) Configured minimum value of the LSP, in bps.

MaxBW

(Ingress LSP) Configured maximum value of the LSP, in bps.

Dynamic MinBW

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

Dynamic MinBW

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

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.

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.

Time for Next Adjustment

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

Time of Last Adjustment

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

MaxAvgBW util

(Ingress LSP) Current value of the actual maximum average bandwidth utilization, in bps.

Overflow limit

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

Overflow sample count

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

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.

In-place Update Count

Current value of the in-place LSP bandwidth update counter indicating the number of times an LSP-ID is reused when LSP-ID re-use is enabled for an LSP.

Underflow limit

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

Underflow sample count

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

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.

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

Primary

(Ingress LSP) Name of the primary path.

Secondary

(Ingress LSP) Name of the secondary path.

Standby

(Ingress LSP) Name of the path in standby mode.

State

(Ingress LSP) State of the path: Up or Dn (down).

COS

(Ingress LSP) Class-of-service value.

Bandwidth per class

(Ingress LSP) Active bandwidth for the LSP path for each MPLS class type, in bps.

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

OptimizeTimer

(Ingress LSP) Configured value of the optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds.

SmartOptimizeTimer

(Ingress LSP) Configured value of the smart optimize timer, indicating the total amount of time allowed before path reoptimization, in seconds.

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.

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

CSPF metric

(Ingress LSP) Constrained Shortest Path First metric for this path.

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.

Labels

Labels of pop-and-forward LSP tunnel:

• P—Pop labels.

• D—Delegation labels.

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.

Date

(Ingress LSP) Date of the LSP event.

Time

(Ingress LSP) Time of the LSP event.

Event

(Ingress LSP) Description of the LSP event.

Created

(Ingress LSP) Date and time the LSP was created.

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

Labelin

Incoming label for this LSP.

Labelout

Outgoing label for this LSP.

LSPname

Name of the LSP.

Time left

Number of seconds remaining in the lifetime of the reservation.

Since

Date and time when the RSVP session was initiated.

Tspec

Sender's traffic specification, which describes the sender's traffic parameters.

Port number

Protocol ID and sender or receiver port used in this RSVP session.

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.

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.

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.

Record route

Recorded route for the session, taken from the record route object.

Pop-and-forward

Attributes of the pop-and-forward LSP tunnel.

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.

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.

Delegation hop

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

• Yes

• No

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

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.

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.