Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show snmp rmon history

 

Syntax

Release Information

Command introduced in Junos OS Release 9.0.

Description

Display the contents of the RMON history group.

Options

noneDisplay all the entries in the RMON history group.
history-index(Optional) Display the contents of the specified entry in the RMON history group.
sample-index sample-index(Optional) Display the statistics collected for the specified sample within the specified entry in the RMON history group.

Required Privilege Level

view

List of Sample Output

show snmp rmon history 1

show snmp rmon history 1 sample-index 15

Output Fields

Table 1 lists the output fields for the show smp rmon history command. Output fields are listed in the approximate order in which they appear.

Table 1: show smp rmon history Output Fields

Field Name

Field Description

History Index

Identifies this RMON history entry within the RMON history group.

Owner

The entity that configured this entry. Range is 0 to 32 alphanumeric characters.

Status

The status of the RMON history entry.

Interface or Data Source

The ifndex object that identifies the interface that is being monitored.

Interval

The interval (in seconds) configured for this RMON history entry.

Buckets Requested

The requested number of buckets (intervals) configured for this RMON history entry.

Buckets Granted

The number of buckets granted for this RMON history entry.

Sample Index

The sample statistics taken at the specified interval.

  • Drop Events—Number of packets dropped by the input queue of the I/O Manager ASIC. If the interface is saturated, this number increments once for every packet that is dropped by the ASIC's RED mechanism.

  • Octets—Total number of octets and packets. For Gigabit Ethernet IQ PICs, the received octets count varies by interface type.

  • Packets—Total number of packets.

  • Broadcast Packets—Number of broadcast packets.

  • Multicast Packets—Number of multicast packets.

  • CRC errors—Total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, and had either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a nonintegral number of octets (alignment error).

  • Undersize Pkts—Number of packets received during this sampling interval that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.

  • Oversize Pkts—Number of packets received during the sampling interval that were longer than 1518 octets (excluding framing bits, but including FCS octets) but were otherwise well formed.

  • Fragments—Total number of packets that were less than 64 octets in length (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. Fragment frames normally increment because both runts (which are normal occurrences caused by collisions) and noise hits are counted.

  • Jabbers—Number of frames that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either an FCS error or an alignment error. This definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition in which any packet exceeds 20 ms. The allowed range to detect jabber is from 20 ms to 150 ms.

  • Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC supports only full-duplex operation, so for Gigabit Ethernet PICs, this number should always remain 0. If it is nonzero, there is a software bug.

  • Utilization(%)—The best estimate of the mean physical layer network utilization on this interface during this sampling interval, in hundredths of a percent.

Sample Output

show snmp rmon history 1

user@host> show snmp rmon history 1

show snmp rmon history 1 sample-index 15

user@host> show snmp rmon history 1 sample-index 15