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

show rsvp statistics

Syntax

show rsvp statistics
<logical-system (all | logical-system-name)>

Release Information

Command introduced before JUNOS Release 7.4.

Description

Display Resource Reservation Protocol (RSVP) packet and error statistics.

Options

none — Display RSVP packet and error statistics on all logical systems.

logical-system (all | logical-system-name) — (Optional) Perform this operation on all logical systems or on a particular logical system.

Required Privilege Level

view

Related Topics

clear rsvp statistics

List of Sample Output

show rsvp statistics

Output Fields

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

Table 157: show rsvp statistics Output Fields

Field Name

Field Description

Packet Type

Statistics about different RSVP messages.

Total Sent

Total number of packets sent since RSVP was enabled.

Total Received

Total number of packets received since RSVP was enabled.

Last 5 seconds Sent

Total number of packets sent in the last 5 seconds.

Last 5 seconds Received

Number of packets received in the last 5 seconds.

Path

Statistics about Path messages, which are sent from the RSVP sender along the data paths and which store path state information in each node along the path.

PathErr

Statistics about PathErr messages, which are advisory messages that are sent upstream to the sender.

PathTear

Statistics about PathTear messages, which remove path states and dependent reservation states in any routers along a path.

Resv FF

Statistics about fixed-filter reservation style messages, which consist of distinct reservations among explicit senders.

Resv WF

Statistics about wildcard-filter reservation style messages, which consist of shared reservations among wildcard senders.

Res SE

Statistics about shared-explicit reservation style messages, which consist of shared reservations among explicit senders.

ResvErr

Statistics about ResvErr messages, which are advisory messages that are sent when an attempt to establish a reservation fails.

ResvTear

Statistics about ResvTear messages, which remove reservation states along a path.

ResvConf

Statistics about ResvConfirm messages, which are responses to confirm a reservation request.

Ack

Acknowledge message for refresh reductions.

SRefresh

Summary refresh messages.

Hello

Number of RSVP hello packets that have been sent to and received from the neighbor.

EndtoEnd RSVP

Statistics for the number of End-to-end RSVP messages.

Errors

Statistics about errored RSVP packets.

Rcv pkt bad length

The packet was not processed because its length is inappropriate.

Rcv pkt unknown type

The packet is not one of the well-known RSVP types, as defined in RFC 2205, Resource ReSerVation Protocol (RSVP).

Rcv pkt bad version

The packet is not an RSVP version 1 packet.

Rcv pkt auth fail

The packet failed authentication checks.

Rcv pkt bad cksum

The RSVP checksum check failed.

Rcv pkt bad format

General packet processing failed because the packet was badly formed.

Memory alloc fail

An internal resource failure occurred.

No path info

A reservation was received, but no sender is active.

Resv style conflict

The same session contains inconsistent reservation styles.

Port conflict

There were inconsistent port numbers for the same session.

Resv no interface

An interface for the receive reservation packets cannot be located.

PathErr to client

Number of PathErr packets delivered to the local client.

ResvErr to client

Number of ResvErr packets delivered to the local client.

Path timeout

Number of times the sender timed out because the path was removed.

Resv timeout

Number of times the receiver timed out because the reservation was removed.

Message out-of-order

Records the number of RSVP incoming messages that are considered out of order. This is detected from the message ID object's sequence number.

Unknown ack msg

A neighboring router replies with an ACK object that contains an unknown message ID. This can indicate a message ID handshake problem.

Recv nack

A neighboring router explicitly rejects a message ID in a summary refresh message. This can happen if that neighbor has been rebooted. In this case, the router sends a regular RSVP refresh message to recover the state, and starts the message-ID handshake process again

Recv duplicated msg-id

Number of times the same message ID is used by two different RSVP messages. This duplication is usually caused when a neighboring router restarts.

No TE-link to recv Hop

Counter of packets discarded because a TE link was not found.

show rsvp statistics

user@host> show rsvp statistics
   PacketType              Total                  Last 5 seconds
                    Sent      Received        Sent      Received
   Path               355           408           0             0
   PathErr              2            13           0             0
   PathTear           101           139           0             0
   Resv FF              0             0           0             0
   Resv WF              0             0           0             0
   Resv SE            419           225           0             0
   ResvErr              0             0           0             0
   ResvTear             0            13           0             0
   ResvConf             0             0           0             0
   Ack                682          1414           0             0
   SRefresh        395198        236030           5             2
   Hello           578809        578221           4             4
   EndtoEnd RSVP        0             0           0             0
  
   Errors                          Total            Last 5 seconds
   Rcv pkt bad length                0                         0
   Rcv pkt unknown type              0                         0
   Rcv pkt bad version               0                         0
   Rcv pkt auth fail                 0                         0
   Rcv pkt bad checksum              0                         0
   Rcv pkt bad format                0                         0
   Memory allocation fail            0                         0
   No path information              10                         0
   Resv style conflict               0                         0
   Port conflict                     0                         0
   Resv no interface                 0                         0
   PathErr to client                38                         0
   ResvErr to client                 0                         0
   Path timeout                      8                         0
   Resv timeout                     57                         0
   Message out-of-order              0                         0
   Unknown ack msg                2978                         0
   Recv nack                        86                         0
   Recv duplicated msg-id            5                         0
   No TE-link to recv Hop            0                         0

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