show rsvp session
Syntax
Syntax (EX Series Switches)
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.5 for EX Series switches.
Description
Display information about Resource Reservation Protocol (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. |
interface interface-name | — | (Optional) Display RSVP sessions for the specified interface only. |
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:
|
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:
|
statistics | — | (Optional) Display packet statistics. |
te-link te-link | — | (Optional) Display sessions with reservations on the specified TE link. |
Required Privilege Level
view
List of Sample Output
show rsvp sessionshow rsvp session statistics
show rsvp session detail
show rsvp session detail (Path MTU Output Field)
show rsvp session detail (GMPLS)
show rsvp session extensive
show rsvp session p2mp (Ingress Router)
show rsvp session p2mp (Transit Router)
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 |
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:
| 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 |
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 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
user@host> show rsvp sessionIngress 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
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
user@host> show rsvp session detailIngress RSVP: 1 sessions 1.1.1.1 From: 2.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 (Path MTU Output Field)
user@host> show rsvp session detailIngress 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)
user@host> show rsvp session detailIngress 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: 100.100.100.100 93.93.93.93 Record route: <self> 100.100.100.100 93.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 extensive
user@host> show rsvp session extensiveIngress RSVP: 1 sessions 192.168.0.4 From: 192.168.0.5, LSPstate: Up, ActiveRoute: 0 LSPname: E-D, LSPpath: Primary LSPtype: Static Configured Suggested label received: -, Suggested label sent: - Recovery label received: -, Recovery label sent: 299808 Resv style: 1 FF, Label in: -, Label out: 299808 Time left: -, Since: Thu Sep 20 15:54:20 2012 Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500 Port number: sender 2 receiver 61576 protocol 0 Attrib flags: Non-PHP PATH rcvfrom: localclient Adspec: sent MTU 1500 Path MTU: received 1500 PATH sentto: 10.0.0.18 (lt-1/2/0.17) 41 pkts RESV rcvfrom: 10.0.0.18 (lt-1/2/0.17) 40 pkts Explct route: 10.0.0.18 10.0.0.22 Record route: <self> 10.0.0.18 10.0.0.22 Total 1 displayed, Up 1, Down 0 Egress RSVP: 1 sessions 192.168.0.5 From: 192.168.0.4, LSPstate: Up, ActiveRoute: 0 LSPname: E-D, LSPpath: Primary Suggested label received: -, Suggested label sent: - Recovery label received: -, Recovery label sent: - Resv style: 1 FF, Label in: 3, Label out: - Time left: 140, Since: Thu Sep 20 15:52:10 2012 Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500 Port number: sender 1 receiver 49601 protocol 0 PATH rcvfrom: 10.0.0.18 (lt-1/2/0.17) 44 pkts Adspec: received MTU 1500 PATH sentto: localclient RESV rcvfrom: localclient Record route: 10.0.0.22 10.0.0.18 <self> Total 1 displayed, Up 1, Down 0 Transit RSVP: 0 sessions Total 0 displayed, Up 0, Down 0
show rsvp session p2mp (Ingress Router)
user@host> show rsvp session p2mpIngress 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)
user@host> show rsvp session p2mpIngress 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
