Determining LSP Statistics

Purpose

Display detailed information about RSVP objects to assist the diagnosis of an LSP problem.

Action

To verify RSVP objects, enter the following JUNOS CLI operational mode command:

user@host> show rsvp session detail

Sample Output

user@R1> show rsvp session detail

Ingress RSVP: 1 sessions

10.0.0.6

  From: 10.0.0.1, LSPstate: Up, ActiveRoute: 1

  LSPname: R1-to-R6, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 100064

  Resv style: 1 FF, Label in: -, Label out: 100064

  Time left:    -, Since: Tue Aug 17 12:22:52 2004

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 12 receiver 44251 protocol 0

  PATH rcvfrom: localclient 

  Adspec: sent MTU 1500

  PATH sentto: 10.1.13.2 (so-0/0/2.0) 182 pkts

  RESV rcvfrom: 10.1.13.2 (so-0/0/2.0) 159 pkts

  Explct route: 10.1.13.2 10.1.36.2 

  Record route: <self> 10.1.13.2 10.1.36.2  

Total 1 displayed, Up 1, Down 0

Egress RSVP: 1 sessions

10.0.0.1

  From: 10.0.0.6, LSPstate: Up, ActiveRoute: 0

  LSPname: R6-to-R1, 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:  135, Since: Tue Aug 17 12:23:14 2004

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 39024 protocol 0

  PATH rcvfrom: 10.1.15.2 (so-0/0/1.0) 158 pkts

  Adspec: received MTU 1500 

  PATH sentto: localclient

  RESV rcvfrom: localclient 

  Record route: 10.1.56.2 10.1.15.2 <self>  

Total 1 displayed, Up 1, Down 0

Transit RSVP: 0 sessions

Total 0 displayed, Up 0, Down 0

What It Means

The sample output shows that there is one ingress and one egress RSVP session. The ingress session has a source address of 10.0.0.1 (R1), and the session is up, with one active route. The LSP name is R1-to-R6 and it is the primary path for the LSP.

The recovery label (100064) is sent by a graceful restart router to its neighbor to recover a forwarding state. It is probably the old label that the router advertised before it went down.

This session is using the fixed filter (FF) reservation style (Resv style). Since this is an ingress router, there is no inbound label. The outbound label (provided by the next downstream router) is 100064.

The Time Left field provides the number of seconds remaining in the RSVP session, and the Tspec object provides information about the controlled load rate (rate) and maximum burst size (peak), an infinite value (Infbps) for the guaranteed delivery option, and the indication that packets smaller than 20 bytes are treated as 20 bytes, while packets larger than 1500 bytes are treated as 1500 bytes.

The port number is the IPv4 tunnel ID, while the sender/receiver port number is the LSP ID. The IPv4 tunnel ID is unique for the life of the LSP, while the sender/receiver LSP ID can change, for example, with an SE style reservation.

The PATH rcvfrom field includes the source of the path message. Since this is the ingress router, the local client originated the path message.

The PATH sentto field includes the path message destination (10.1.13.2) and outgoing interface (so-0/0/2.0). The RESV rcvfrom field includes both the source of the Resv message received (10.1.13.2) and the incoming interface (so-0/0/2.0).

The RSVP explicit route and the route record values are identical: 10.1.13.2 and 10.1.36.2. In most cases, the explicit route and the record route values are identical. Differences indicate that some path rerouting has occurred, typically during Fast-Reroute.

The Total fields indicate the total number of ingress, egress, and transit RSVP sessions, with the total being equal to the sum of the up and down sessions. In this example, there is one ingress session, one egress session, and no transit RSVP sessions.