[Contents] [Prev] [Next] [Index] [Report an Error]

show rsvp session

Syntax

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

Release Information

Command introduced before JUNOS Release 7.4.

Description

Display information about Resource Reservation Protocol (RSVP) sessions.

Options

none — Display standard information about all RSVP sessions on all logical systems.

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

Related Topics

clear rsvp session

List of Sample Output

show rsvp session
show 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

Output Fields

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

Table 161: 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 router) of the session.

All levels

From

Source (ingress router) 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 router) of the LSP.

detail

From

Source (ingress router) 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 routers. LSPpath can also indicate when a graceful LSP deletion has been triggered.

detail

Bypass

(Egress router) 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

FastReroute desired

Fast reroute has been requested by the ingress router.

detail

Soft preemption desired

Soft preemption has been requested by the ingress router.

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

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

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

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 routers 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) router or client, interface the neighbor used to reach this router, and number of packets received from the upstream neighbor.

detail

Adspec

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

detail

PATH sentto

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

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

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 detail 
Ingress 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 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)

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: 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 extensive 
10.255.245.13
    From: 10.255.245.48, LSPstate: Up, ActiveRoute: 0
    ....
    Link protection desired
    Type: Link protected LSP, using p2
       11 Feb  6 15:24:16 Backup LSP: Call was cleared by RSVP
       10 Feb  6 15:24:16 Backup LSP: Session preempted
        9 Feb  6 15:24:16 Deleting backup LSP, protected LSP restored
        8 Feb  6 15:23:22 Backup LSP: Up  192.168.208.117(Label=3)
        7 Feb  6 15:23:22 Backup LSP: Record Route:  192.168.208.117(Label=3)
        6 Feb  6 15:23:19 Backup LSP: Explicit Route: wrong delivery
        5 Feb  6 15:23:19 Creating backup LSP, link down
        4 Feb  6 12:36:03 Link protection up, using p2
        3 Feb  6 12:35:56 New bypass p2
        2 Feb  6 12:35:47 Bypass state down, p1[2 times]
        1 Feb  6 12:35:39 New bypass p1

show rsvp session p2mp

user@host> show rsvp session p2mp 
Ingress RSVP: 3 sessions
P2MP name: p2mp-lsp1, P2MP branch count: 1
To              From            State Rt Style Labelin Labelout LSPname 
10.255.245.34   10.255.245.25 Up     0 1 FF       -      100128 p2mp-branch-1
P2MP name: p2mp-lsp2, P2MP branch count: 1
To              From            State Rt Style Labelin Labelout LSPname 
10.255.245.34   10.255.245.25 Up     0 1 FF       -           3 p2mp-st-br1
P2MP name: lsp-a_b, P2MP branch count: 1
Total 2 displayed, Up 2, Down 0

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

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.