close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

show rsvp session

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
show rsvp session
<brief | detail | extensive | terse>
<bidirectional | unidirectional>
<bypass>
<down | up>
<externally-provisioned>
<instance instance-name>
<interface interface-name> 
<logical-system (all | logical-system-name)>
<lsp-type>
<name session-name>
<p2mp> 
<session-type> 
<statistics>
<te-link te-link>

Syntax (EX and QFX Series Switches)

content_copy zoom_out_map
show rsvp session
<brief | detail | extensive | terse>
<bidirectional | unidirectional>
<bypass>
<down | up>
<externally-provisioned>
<interface interface-name> 
<lsp-type>
<name session-name>
<p2mp> 
<session-type> 
<statistics>
<te-link te-link>

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: user@host> `show rsvp session egress extensive \| match "PATH rcvfrom:" \| match interface-name \| count`
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: user@host> `show rsvp session egress extensive \| match "PATH rcvfrom:" \| match interface-name \| count` `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
show rsvp session extensive transit
show rsvp session p2mp (Ingress Router)
show rsvp session p2mp (Transit Router)

show rsvp session

content_copy zoom_out_map
user@host> show rsvp session
Ingress RSVP: 1 sessions
To              From            State   Rt Style Labelin Labelout LSPname
10.255.245.214  10.255.245.212  AdminDn  0  1 FF       -    22293 LSP Bidir
Total 1 displayed, Up 1, Down 0

Egress RSVP: 2 sessions
To              From            State Rt Style Labelin Labelout LSPname
10.255.245.194  10.255.245.195  Up     0  1 FF   39811        - Gpro3-ba Bidir
10.255.245.194  10.255.245.195  Up     0  1 FF       3        - pro3-ba
Total 2 displayed, Up 2, Down 0

Transit RSVP: 1 sessions
To              From            State Rt Style Labelin Labelout LSPname
10.255.245.198  10.255.245.197  Up     0  1 SE  100000        3 pro3-de
Total 1 displayed, Up 1, Down 0

show rsvp session statistics

content_copy zoom_out_map
user@host> show rsvp session statistics 
Ingress RSVP: 2 sessions 
To              From           State   Packets      Bytes    LSPname 
10.255.245.24   10.255.245.22     Up         0        0      pro3-bd 
10.255.245.24   10.255.245.22     Up     44868    2333136  pro3-bd-2 
Total 2 displayed, Up 2, Down 0 
Egress RSVP: 2 sessions 
To              From           State   Packets      Bytes    LSPname 
10.255.245.22   10.255.245.24     Up         0          0    pro3-db 
10.255.245.22   10.255.245.24     Up         0          0  pro3-db-2 
Total 2 displayed, Up 2, Down 0 
Transit RSVP: 0 sessions 
Total 0 displayed, Up 0, Down 0 

show rsvp session detail

content_copy zoom_out_map
user@host> show rsvp session detail
Ingress RSVP: 1 sessions
10.1.1.1
  From: 10.2.2.2, LSPstate: Up, ActiveRoute: 0
  LSPname: to-a, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 3
  Resv style: 1 FF, Label in: -, Label out: 3
  Time left:    -, Since: Fri Mar 26 18:42:42 2004
  Tspec: rate 300kbps size 300kbps peak Infbps m 20 M 1500
  DiffServ info: diffServ-TE LSP, bandwidth: <ct1 300kbps> 
  Port number: sender 1 receiver 15876 protocol 0
  PATH rcvfrom: localclient 
  Adspec: sent MTU 1500
  PATH sentto: 192.168.37.16 (t1-0/2/1.0) 1 pkt

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

content_copy zoom_out_map
user@host> show rsvp session detail
Ingress RSVP: 1 sessions
10.1.1.1
  From: 10.2.2.2, LSPstate: Up, ActiveRoute: 0
  LSPname: to-a, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 3
  Resv style: 1 FF, Label in: -, Label out: 3
  Time left:    -, Since: Fri Mar 26 18:42:42 2004
  Tspec: rate 300kbps size 300kbps peak Infbps m 20 M 1500
  DiffServ info: diffServ-TE LSP, bandwidth: <ct1 300kbps> 
  Port number: sender 1 receiver 15876 protocol 0
  Egress protection PLR as protector: Active
PATH rcvfrom: localclient 
  Adspec: sent MTU 1500
  PATH sentto: 192.168.37.16 (t1-0/2/1.0) 1 pkt

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

content_copy zoom_out_map
user@host> show rsvp session detail
Ingress RSVP: 1 sessions
10.1.1.1
  From: 10.2.2.2, LSPstate: Down, ActiveRoute: 0
  LSPname: to-a, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 3
  Resv style: 1 FF, Label in: -, Label out: 3
  Time left:    -, Since: Fri Mar 26 18:42:42 2004
  Tspec: rate 300kbps size 300kbps peak Infbps m 20 M 1500
  DiffServ info: diffServ-TE LSP, bandwidth: <ct1 300kbps> 
  Port number: sender 1 receiver 15876 protocol 0
Egress protection PLR as protector: In Use
PATH rcvfrom: localclient 
  Adspec: sent MTU 1500
  PATH sentto: 192.168.37.16 (t1-0/2/1.0) 1 pkt

show rsvp session detail (Path MTU Output Field)

content_copy zoom_out_map
user@host> show rsvp session detail
Ingress RSVP: 1 sessions
10.255.245.3
  From: 10.255.245.5, LSPstate: Up, ActiveRoute: 3
  LSPname: to-c, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 100432
  Resv style: 1 FF, Label in: -, Label out: 100432
  Time left:    -, Since: Mon Aug 16 17:54:40 2006
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 9192
  Port number: sender 1 receiver 57843 protocol 0
  FastReroute desired
  PATH rcvfrom: localclient 
  Adspec: sent MTU 4470
  Path mtu: received 4470, using 4458 for forwarding
  PATH sentto: 192.168.37.89 (so-0/2/3.0) 11 pkts
  RESV rcvfrom: 192.168.37.89 (so-0/2/3.0) 10 pkts
  Explct route: 192.168.37.89 
  Record route: <self> 192.168.37.89 192.168.37.87  
    Detour is Up
    Detour Tspec: rate 0bps size 0bps peak Infbps m 20 M 9192
    Detour adspec: sent MTU 1512
    Path mtu: received 1512, using 1500 for forwarding

show rsvp session detail (GMPLS)

content_copy zoom_out_map
user@host> show rsvp session detail
Ingress RSVP: 1 sessions
192.168.4.1
  From: 192.168.1.1, LSPstate: Dn, ActiveRoute: 0
  LSPname: gmpls-r1–to-r3, LSPpath: Primary
  Bidirectional, Upstream label in: 21253, Upstream label out: —
  Suggested label received: -, Suggested label sent: 21253
  Recovery label received: -, Recovery label sent: —
  Resv style: 0 —, Label in: -, Label out: —
  Time left:    -, Since: Mon Aug 16 17:54:40 2006
  Tspec: rate 0bps size 0bps peak 155.52Mbps m 20 M 1500
  Port number: sender 2 receiver 46115 protocol 0
  PATH rcvfrom: localclient 
  Adspec: sent MTU 1500
  PATH MTU: received 0
  PATH sentto: 10.35.1.5 (so-0/2/3.0) 11 pkts
  Explct route: 10.100.100.100 10.93.93.93
  Record route: <self> 10.100.100.100 10.93.93.93
  Total 1 displayed, Up 0, Down 1
  Egress RSVP: 0 sessions
  Total 0 displayed, Up 0, Down 0
  Transit RSVP: 0 sessions
  Total 0 displayed, Up 0, Down 0

show rsvp session detail (Fspec Output Field)

content_copy zoom_out_map
user@host> show rsvp session detail
IIngress RSVP: 2 sessions

192.168.255.4
  From: 192.168.255.1, LSPstate: Up, ActiveRoute: 0
  LSPname: R1-to-R4-1, LSPpath: Primary
  LSPtype: Static Configured
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 299840
  Resv style: 1 SE, Label in: -, Label out: 299840
  Time left:    -, Since: Mon May  4 21:33:34 2020
  Tspec: rate 500Mbps size 500Mbps peak Infbps m 20 M 1500
	 Fspec: rate 600Mbps size 600Mbps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 58554 protocol 0
  SelfID: RSVP-2, Route Statistics ID: RSVP-3
  SessionID: 2
  Link protection desired
  Type: Link protected LSP, using Bypass->10.1.2.18
      2 May  4 21:33:37 Link protection up, using Bypass->10.1.2.18
      1 May  4 21:33:36 New bypass Bypass->10.1.2.18
  Enhanced FRR: Enabled (Downstream), LP-MP is 192.168.255.2
  PATH rcvfrom: localclient
  Adspec: sent MTU 1500
  Path MTU: received 1500
  PATH sentto: 10.1.2.18 (ge-0/0/1.0) 4 pkts
       outgoing message state: refreshing, Message ID: 20, Epoch: 5199652
  RESV rcvfrom: 10.1.2.18 (ge-0/0/1.0) 7 pkts, Entropy label: Yes
       incoming message handle: R-1/7, Message ID: 77, Epoch: 5203461
  Explct route: 10.1.2.18 10.2.3.3 10.3.4.20
  Record route: 10.2.2.2 (node-id) 10.1.2.18 192.168.255.3 (node-id) 10.2.3.3 192.168.255.4 (node-id) 10.3.4.20
Total 1 displayed, Up 1, Down 0

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.

content_copy zoom_out_map
user@host> show rsvp session extensive
Ingress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 1 sessions

10.0.0.5
  From: 10.0.0.1, LSPstate: Up, ActiveRoute: 0
  LSPname: 1to5, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 299856
  Resv style: 1 SE, Label in: 299776, Label out: 299856
  Time left:  123, Since: Sat Nov 29 10:39:15 2014
  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 52631 protocol 0
  PATH rcvfrom: 10.1.2.1 (ge-0/0/0.0) 2 pkts
  incoming message handle: P-1/2, ID: 0xc82fd7/322
  Adspec: received MTU 1500 sent MTU 1500
  PATH sentto: 10.2.4.4 (ge-0/0/1.0) 1 pkts
  outgoing message state: refreshing, ID: 0xcacec0/22
  RESV rcvfrom: 10.2.4.4 (ge-0/0/1.0) 1 pkts, Entropy label: Yes
  incoming message handle: R-2/1, ID: 0xc82f3e/217
  RESV 
  outgoing message state: refreshing, ID: 0xcacec0/17
  Explct route: 10.2.4.4 10.99.0.5 
  Record route: 10.1.2.1 <self>  10.2.4.4 10.99.0.5
  Total 1 displayed, Up 1, Down 0 

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.

content_copy zoom_out_map
user@host> show rsvp session extensive
Ingress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 1 sessions
10.50.50.50
  From: 10.40.40.40, LSPstate: Up, ActiveRoute: 0
  LSPname: lsp1-40-to-50, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 299824
  Resv style: 1 SE, Label in: 299824, Label out: 299824
  Time left: 5336, Since: Mon Jun 29 20:53:06 2020
  Tspec: rate 100Mbps size 100Mbps peak Infbps m 20 M 1500
  Port number: sender 5 receiver 44412 protocol 0
  Link protection desired
  Type: Link protected LSP, using Bypass->10.21.31.31
      1 Jun 29 20:53:06 Link protection up, using Bypass->10.21.31.31
  Enhanced FRR: Enabled (Upstream), LP-MP for 10.40.40.40
  Enhanced FRR: Enabled (Downstream), LP-MP is 10.31.31.31
  PATH rcvfrom: 10.40.21.21 (ge-0/0/0.0) 2 pkts
       incoming message handle: P-13/2, Message ID: 31, Epoch: 430841
  Adspec: received MTU 1500 sent MTU 1500
  PATH sentto: 10.21.31.31 (ge-1/0/0.0) 3 pkts
       outgoing message state: refreshing, Message ID: 64, Epoch: 435515
  RESV rcvfrom: 10.21.31.31 (ge-1/0/0.0) 4 pkts, Entropy label: Yes
       incoming message handle: R-14/4, Message ID: 50, Epoch: 435661
  RESV
       outgoing message state: refreshing, Message ID: 63, Epoch: 435515
  Explct route: 10.21.31.31 10.28.31.28 10.28.33.33 10.23.33.23 10.28.23.23 10.23.50.50
  Explct hop 10.28.23.23 expanded
  Record route: 10.40.21.21 10.40.40.40 <self> 10.31.31.31 (node-id) 10.21.31.31 10.28.28.28 (node-id) 10.28.31.28 10.33.33.33 (node-id) 10.28.33.33 10.23.23.23 (node-id) 10.23.33.23 10.50.50.50 (node-id) 10.23.50.50

Total 1 displayed, Up 1, Down 0
 

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.

content_copy zoom_out_map
user@host> show rsvp session extensive transit
  From: 10.1.1.1, LSPstate: Up, ActiveRoute: 0
  LSPname: A-D-1, LSPpath: Primary
  Suggested label received: -, Suggested label sent: -
  Recovery label received: -, Recovery label sent: 299776
  Resv style: 1 SE, Label in: 299776, Label out: 299776
  Time left:  117, Since: Tue May  6 08:39:44 2014
  Tspec: rate 700Mbps size 700Mbps peak Infbps m 20 M 1500
  Port number: sender 1 receiver 24131 protocol 0
  Node/Link protection desired
  Type: Node/Link protected LSP, using Bypass->10.2.3.3->10.3.4.4
      2 May  6 08:39:47 Node protection up, using Bypass->10.2.3.3->10.3.4.4
      1 May  6 08:39:44 New bypass Bypass->10.2.3.3->10.3.4.4
  Enhanced Local Protection: Enabled, LP-MP for 10.2.2.2, NP-MP for 10.1.1.1
  PATH rcvfrom: 10.1.2.1 (lt-0/2/0.201) 5371 pkts
  Adspec: received MTU 1500 sent MTU 1500
  PATH sentto: 10.2.3.3 (lt-0/2/0.203) 5374 pkts
  RESV rcvfrom: 10.2.3.3 (lt-0/2/0.203) 5372 pkts, Entropy label: No
  Record route: 10.1.2.1 <self>  10.3.3.3 (node-id) 10.2.3.3 10.4.4.4 (node-id) 10.3.4.4 
  Total 1 displayed, Up 1, Down 0 

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:

content_copy zoom_out_map
Enhanced Local Protection: Disabled, Reason: User Config
Enhanced Local Protection: Disabled, Reason: Backward Compatibility 

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

content_copy zoom_out_map
Enhanced Local Protection: Enabled, Non-MP 

show rsvp session p2mp (Ingress Router)

content_copy zoom_out_map
user@host> show rsvp session p2mp
Ingress RSVP: 3 sessions
P2MP name: test, P2MP branch count: 1
To              From            State   Rt Style Labelin Labelout LSPname 
10.255.10.95    10.255.10.2     Up       0  1 SE    -           3 to-pe1
P2MP name: test2, P2MP branch count: 2
To              From            State   Rt Style Labelin Labelout LSPname 
10.255.10.23    10.255.10.2     Up       0  1 SE    -      299776 to-pe3
10.255.10.16    10.255.10.2     Up       0  1 SE    -      299776 to-pe4
Total 3 displayed, Up 3, Down 0

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

show rsvp session p2mp (Transit Router)

content_copy zoom_out_map
user@host> show rsvp session p2mp
Ingress RSVP: 1 sessions
P2MP name: test, P2MP branch count: 1
To              From            State   Rt Style Labelin  Labelout LSPname 
10.255.10.23    10.255.10.95    Up       0  1 SE    -       299792 to-pe2
Total 1 displayed, Up 1, Down 0

Egress RSVP: 1 sessions
P2MP name: test, P2MP branch count: 1
To              From            State   Rt Style Labelin Labelout  LSPname 
10.255.10.95    10.255.10.2     Up       0  1 SE    3        -     to-pe1
Total 1 displayed, Up 1, Down 0

Transit RSVP: 2 sessions
P2MP name: test2, P2MP branch count: 2
To              From            State   Rt Style Labelin Labelout  LSPname 
10.255.10.23    10.255.10.2     Up       0  1 SE  299776   299808  to-pe3
10.255.10.16    10.255.10.2     Up       0  1 SE  299776   299856  to-pe4
Total 2 displayed, Up 2, Down 0

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.

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

arrow_backward PREVIOUS show rsvp route-session-id

NEXT arrow_forward show rsvp statistics

Junos CLI Reference

ON THIS PAGE

show rsvp session

Syntax

Syntax (EX and QFX Series Switches)

Description

Options

Required Privilege Level

Output Fields

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

show rsvp session extensive transit

show rsvp session p2mp (Ingress Router)

show rsvp session p2mp (Transit Router)

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos CLI Reference

ON THIS PAGE

show rsvp session

Syntax

Syntax (EX and QFX Series Switches)

Description

Options

Required Privilege Level

Output Fields

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

show rsvp session extensive transit

show rsvp session p2mp (Ingress Router)

show rsvp session p2mp (Transit Router)

Release Information

Related Documentation

Stay in touch