Dell PowerConnect B-RX Configuration Manual page 1089

Syntax: show rmon statistics [<num> | ethernet <slot/port> | management <num> | | begin
The <portnum> parameter specifies the port number. You can use the physical port number or the
SNMP port number. The physical port number is based on the product:
•
•
The SNMP numbers of the ports start at 1 and increase sequentially. For example, if you are using
a Chassis device and slot 1 contains an 8-port module, the SNMP number of the first port in slot 2
is 9. The physical port number of the same port is 2/1.
This command shows the following information.
TABLE 166
This line...
Octets
Drop events
Packets
Broadcast pkts
Multicast pkts
CRC alignment errors
Undersize pkts
Fragments
BigIron RX Series Configuration Guide
53-1001986-01
<expression> | exclude <expression> | include <expression>]
If the product is a Stackable device, the ports are numbered sequentially starting with 1.
If the product is a Chassis device, the ports are numbered according to slot and port. For
example, the first port in slot 1 is 1/1. The third port in slot 7 is 7/3.
Export configuration and statistics
Displays...
The total number of octets of data received on the network.
This number includes octets in bad packets. This number does not
include framing bits but does include Frame Check Sequence (FCS)
octets.
Indicates an overrun at the port. The port logic could not receive the
traffic at full line rate and had to drop some packets as a result.
The counter indicates the total number of events in which packets were
dropped by the RMON probe due to lack of resources. This number is
not necessarily the number of packets dropped, but is the number of
times an overrun condition has been detected.
The total number of packets received.
This number includes bad packets, broadcast packets, and multicast
packets.
The total number of good packets received that were directed to the
broadcast address.
This number does not include multicast packets.
The total number of good packets received that were directed to a
multicast address.
This number does not include packets directed to the broadcast
address.
The total number of packets received that were from 64 – 1518 octets
long, 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).
The packet length does not include framing bits but does include FCS
octets.
The total number of packets received that were less than 64 octets long
and were otherwise well formed.
This number does not include framing bits but does include FCS octets.
The total number of packets received that were less than 64 octets long
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).
It is normal for this counter to increment, since it counts both runts
(which are normal occurrences due to collisions) and noise hits.
This number does not include framing bits but does include FCS octets.
38
RMON support
1017