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

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

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 routing device.

detail

Link protection desired

Link protection has been requested by the ingress routing device.

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.

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

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