/stats/port <port number>/rmon
RMON Statistics
This menu option lets you display the remote monitor statistics of the selected port.
 
RMON statistics for port 1:
etherStatsDropEvents: 0
etherStatsOctets: 129677
etherStatsPkts: 1485
etherStatsBroadcastPkts: 734
etherStatsMulticastPkts: 712
etherStatsCRCAlignErrors: 0
etherStatsUndersizePkts: 0
etherStatsOversizePkts: 0
etherStatsFragments: 0
etherStatsJabbers: 0
etherStatsCollisions: 0
etherStatsPkts64Octets: 954
etherStatsPkts65to127Octets: 578
etherStatsPkts128to255Octets: 35
etherStatsPkts256to511Octets: 26
etherStatsPkts512to1023Octets: 16
etherStatsPkts1024to1518Octets: 8
RMON statistics are described in the following table:
 
Remote Monitor Statistics (/stats/port/rmon) 
Statistics
Description
etherStatsDrop Events
The total number of events in which packets were dropped by the probe due to lack of resources.
Note: This number is not necessarily the number of packets dropped — it is just the number of times this condition has been detected.
etherStatsOctets
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
This object can be used as a reasonable usage estimate (which is the percent usage of the Ethernet segment). If you require greater precision, the etherStatsPkts and etherStatsOctets objects should be sampled before and after a common interval.
As shown in the following example, the differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values calculate the usage, as follows:
The result of this equation is the percent value of usage.
etherStatsPkts
The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
etherStatsBroadcastPkts
The total number of good packets received that were directed to the broadcast address.
Note: This does not include multicast packets.
etherStatsMulticastPkts
The total number of good packets received that were directed to a multicast address.
Note: This number does not include packets directed to the broadcast address.
etherStatsCRCAlign Errors
The total number of packets received that had a length (excluding framing bits, but including Frame Check Sequence [FCS] octets) of between 64 and 1518 octets, inclusive, but had either a bad FCS with an integral number of octets (FCS Error), or a bad FCS with a non-integral number of octets (Alignment Error).
etherStatsUndersizePkts
The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well-formed.
etherStatsOversizePkts
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
etherStatsFragments
The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad FCS with an integral number of octets (FCS Error). or a bad FCS with a non-integral number of octets (Alignment Error).
Note: It is expected that etherStatsFragments increments. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits. A runt is a packet that is less than 64 bytes.
etherStatsJabbers
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS Error), or a bad FCS with a non-integral number of octets (Alignment Error).
Note: This definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10Base-5) and section 10.3.1.4 (10Base-2). These documents define jabber as the condition where any packet exceeds 20 milliseconds. The allowed range to detect jabber is between 20 milliseconds and 150 milliseconds.
etherStats-Collisions
The best estimate of the total number of collisions on this Ethernet segment.
The value returned depends on the location of the RMON probe. Section 8.2.1.3 (10Base-5) and section 10.3.1.3 (10Base-2) of IEEE standard 802.3 state that a station must detect a collision in the receive mode if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. As a result, a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would.
Probe location plays a much smaller role when considering 10Base-T. 14.2.1.4 (10Base-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10Base-T station can only detect collisions when it is transmitting. As a result, probes placed on a station and a repeater should report the same number of collisions.
Note: An RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k), plus receiver collisions observed on any coaxial segments to which the repeater is connected.
etherStatsPkts64-Octets
The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits, but including FCS octets).
etherStatsPkts65-to127Octets
The total number of packets (including bad packets) received that were between 65 and 127 octets in length (excluding framing bits, but including FCS octets).
etherStatsPkts128-to255Octets
The total number of packets (including bad packets) received that were between 128 and 255 octets in length (excluding framing bits but including Frame Check Sequence (FCS) octets).
etherStatsPkts256-to511Octets
The total number of packets (including bad packets) received that were between 256 and 511 octets in length (excluding framing bits but including FCS octets).
etherStatsPkts512-to1023Octets
The total number of packets (including bad packets) received that were between 512 and 1023 octets in length (excluding framing bits but including FCS octets).
etherStatsPkts-1024to1518Octets
The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length (excluding framing bits but including FCS octets).