Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

show rsvp session

Syntax

Syntax (EX and QFX Series Switches)

Description

Display information about RSVP sessions.

Options

none

Display standard information about all RSVP sessions.

brief | detail | extensive | terse

(Optional) Display the specified level of output.

bidirectional | unidirectional

(Optional) Display information about bidirectional or unidirectional RSVP sessions only, respectively.

bypass

(Optional) Display RSVP sessions for bypass LSPs.

down | up

(Optional) Display only LSPs that are inactive or active, respectively.

externally-provisioned

(Optional) Display the LSPs that are generated dynamically and provisioned by an external Path Computation Element (PCE).

instance instance-name

(Optional) Display RSVP sessions for the specified instance. If instance-name is omitted, RSVP session information is displayed for the master instance.

interface interface-name

(Optional) Display RSVP sessions for the specified interface only.

RSVP reserves resources only for outgoing LSPs of an interface. Because resources are not reserved for incoming LSPs, the show rsvp sessions interface interface-name command output displays only those RSVP sessions whose next hops correspond to the specified interface.

To identify the number of RSVP sessions formed over the uplink interface on the egress label-switching router (LSR), you can use the following command:

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 RSVP sessions with regard to LSPs:

  • bypass—Sessions used for bypass LSPs.

  • lsp—Sessions used to set up LSPs.

  • nolsp—Sessions not used to set up LSPs.

name session-name

(Optional) Display information about the named session.

p2mp

(Optional) Display point-to-multipoint information.

session-type

(Optional) Display information about a particular session type:

  • egress—Sessions that terminate on this routing device.

    To identify the number of RSVP sessions formed over the uplink interface on the egress label-switching router (LSR), you can use the following command:

  • ingress—Sessions that originate from this routing device.

  • transit—Sessions that transit through this routing device.

statistics

(Optional) Display packet statistics.

te-link te-link

(Optional) Display sessions with reservations on the specified TE link.

Required Privilege Level

view

Output Fields

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

Table 1: show rsvp session Output Fields

Field Name

Field Description

Level of Output

Ingress RSVP

Information about ingress RSVP sessions.

detail

Ingress RSVP

Information about ingress RSVP sessions. Each session has one line of output.

All levels

Egress RSVP

Information about egress RSVP sessions.

All levels

Transit RSVP

Information about the transit RSVP sessions.

All levels

P2MP name

(Appears only when the p2mp option is specified). Name of the point-to-multipoint LSP path.

All levels

P2MP branch count

(Appears only when the p2mp option is specified). Number of LSPs receiving packets from the point-to-multipoint LSP.

All levels

To

Destination (egress routing device) of the session.

All levels

From

Source (ingress routing device) of the session.

All levels

State

State of the path: Up, Down, or AdminDn. AdminDn indicates that the LSP is being taken down gracefully.

All levels

Address

Destination (egress routing device) of the LSP.

detail

From

Source (ingress routing device) of the session.

detail

LSPstate

State of the LSP that is being handled by this RSVP session. It can be either Up, Dn (down), or AdminDn. AdminDn indicates that the LSP is being taken down gracefully.

brief detail

Rt

Number of active routes (prefixes) that have been 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

Active Route

Number of active routes (prefixes) that have been installed in the forwarding table. For ingress RSVP sessions, 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

LSPname

Name of the LSP.

brief detail

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. LSPpath can also indicate when a graceful LSP deletion has been triggered.

detail

Bypass

(Egress routing device) Destination address for the bypass LSP.

detail

Bidir

(When LSP is bidirectional) LSP will allow data to travel in both directions between GMPLS devices.

detail

Bidirectional

(When LSP is bidirectional) LSP will allow data to travel both ways between GMPLS devices.

detail

Upstream label in

(When LSP is bidirectional) Incoming label for reverse direction traffic for this LSP.

detail

Upstream label out

(When LSP is bidirectional) Outgoing label for reverse direction traffic for this LSP.

detail

Recovery label received

(When LSP is bidirectional) Label the upstream node suggests for use in the Resv message that is sent.

detail

Recovery label sent

(When LSP is bidirectional) Label the downstream node suggests for use in its Resv messages that is returned.

detail

Suggested label received

(When LSP is bidirectional) Label the upstream node suggests for use in the Resv message that is sent.

detail

Suggested label sent

(When LSP is bidirectional) Label the downstream node suggests for use in its Resv message that is returned.

detail

Resv style or Style

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

Label in

Incoming label for this LSP.

brief detail

Label out

Outgoing label for this LSP.

brief detail

Time left

Number of seconds remaining in the lifetime of the reservation.

brief 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

Fspec

Indicates signaling of LSP bandwidth change with the same lsp-id completion within a stipulated time duration

detail

DiffServ info

Indicates whether the LSP is a multiclass LSP (multiclass diffServ-TE LSP) or a Differentiated-Services-aware traffic engineering LSP (diffServ-TE LSP).

detail

bandwidth

Bandwidth for each class type (ct0, ct1, ct2, or ct3).

detail

Port number

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

detail

Attrib flags

Non-PHP indicates that ultimate hop popping has been requested by the LSP using this RSVP session

extensive

FastReroute desired

Fast reroute has been requested by the ingress routing device.

detail

Soft preemption desired

Soft preemption has been requested by the ingress routing device.

detail

FastReroute desired

(Data [not a bypass or backup] LSP when the protection scheme has been requested) Fast reroute (one-to-one backup) has been requested by the ingress routing device.

detail extensive

Link protection desired

(Data [not a bypass or backup] LSP when the protection scheme has been requested) Link protection (many-to-one backup) has been requested by the ingress routing device.

detail extensive

Node/Link protection desired

(Data [not a bypass or backup] LSP when the protection scheme has been requested) Node and link protection (many-to-one backup) has been requested by the ingress routing device.

detail extensive

Type

LSP type:

  • Link protected LSP—LSP has been protected by link protection at the outgoing interface. The name of the bypass used is also listed here (extensive).

  • Node/Link protected LSP—LSP has been protected by node and link protection at the outgoing interface. The name of the bypass used is also listed here (extensive).

  • Protection down—LSP is not currently protected.

  • Bypass LSP—LSP that is used to protected one or more user LSPs in case of link failure.

  • Backup LSP at Point-of-Local-Repair (PLR)—LSP that has been temporarily established to protected a user LSP at the ingress of a failed link.

  • Backup LSP at Merge Point (MP)—LSP that has been temporarily established to protected a user LSP at the egress of a failed link.

detail extensive

New bypass

New bypass (the bypass name is also displayed) has been activated to protect the LSP.

extensive

Link protection up, using bypass-name

Link protection (the bypass name is also displayed) has been activated for the LSP.

extensive

Creating backup LSP, link down

A link down event occurred, and traffic is being switched over to the bypass LSP.

extensive

Deleting backup LSP, protected LSP restored

Link has come back up and the LSP has been restored. Because the backup LSP is no longer needed, it is deleted.

extensive

Path mtu

Displays the value of the path MTU received from the network (through signaling) and the value used for forwarding. This value is only displayed on ingress routing devices with the allow-fragmentation statement configured at the [edit protocols mpls path-mtu] hierarchy level. If there is a detour LSP, the path MTU for the detour is also displayed.

detail

Egress protection PLR as protector

RSVP state on the Protector or the point-of-local-repair (PLR) routing device:

  • Active— Egress protection is available at the Protector or the PLR routing device.

  • In Use— Local repair has been completed.

detail

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

detail

Adspec

MTU signaled from the ingress routing device to the egress routing device by means of the adspec object.

detail

PATH sentto

Address of the next-hop (downstream) routing device or client, interface used to reach this neighbor (or peer-name in the GMPLS LSP case), and number of packets sent to the downstream routing device.

detail

Explct hop <ip-address> expanded

Displays the specific hop in the EROs that has been expanded by the router.

extensive

Explct route

Explicit route for the session. Normally this value will be the same as that of record route. Differences indicate that path rerouting has occurred, typically during fast reroute.

detail

Record route

Recorded route for the session, taken from the record route object. Normally this value will be the same as that of explct route. Differences indicate that path rerouting has occurred, typically during fast reroute.

detail

Sample Output

show rsvp session

show rsvp session statistics

show rsvp session detail

show rsvp session detail (When Egress Protection Is in Standby Mode)

show rsvp session detail (When Egress Protection Is in Effect During a Local Repair)

show rsvp session detail (Path MTU Output Field)

show rsvp session detail (GMPLS)

show rsvp session detail (Fspec Output Field)

show rsvp session extensive

Starting in Junos OS Release 16.1, this command includes additional details for both the incoming and outgoing Path and Resv messages. The information includes the internal message handle and revision number, as well as the message ID included by the neighbor in the signaling message.

Starting in Junos OS Release 21.2, this command displays the specific hop in the incoming Explicit Route Objects (EROs) that has been expanded by the router.

show rsvp session extensive transit

Starting in Junos OS Release 16.1, this command also shows node-related details, including whether enhanced local protection is enabled for the LSP and whether the node is a merge point. If the latter is true, both the IP address of the Point of Local Repair (PLR) and the status (LP-MP, NP-MP, or Non-MP) are shown.

If enhanced FRR is not enabled (either because it is disabled on the router itself or one of the neighbors along the LSP path does not support it), either of the following lines might be displayed:

If enhanced FRR is not enabled and the router is not an MP, the following line is displayed:

 

 

show rsvp session p2mp (Ingress Router)

show rsvp session p2mp (Transit Router)

Release Information

Command introduced before Junos OS Release 7.4.

externally-provisioned option added in Junos OS Release 13.3.

instance option added in Junos OS Release 15.1 for the MX Series.

Explct hop <ip-address> expanded fields are introduced in the output field of the show rsvp session command in Junos OS Release 21.2R1.