Brocade Multi-Service IronWare Administration Guide (Supporting R05.6.00) - Manual (Page 119)

Multi-Service IronWare Administration Guide 101
53-1003028-02
RMON support
4
This command shows the following information.
TABLE 23 Export configuration and statistics
This line... Displays...
Octets 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.
Drop events 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.
Packets The total number of packets received.
This number includes bad packets, broadcast packets, and multicast packets.
Broadcast pkts The total number of good packets received that were directed to the
broadcast address.
This number does not include multicast packets.
Multicast pkts 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.
CRC alignment errors 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.
Undersize pkts 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.
Fragments 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.
Oversize packets The total number of packets received that were longer than 1518 octets and
were otherwise well formed.
This number does not include framing bits but does include FCS octets.
Jabbers The total number of packets received that were longer than 1518 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 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 where any packet exceeds
20 ms. The allowed range to detect jabber is between 20 ms and 150
ms.
This number does not include framing bits but does include FCS octets.
Collisions The best estimate of the total number of collisions on this Ethernet segment.
64 octets pkts The total number of packets received that were 64 octets long.
This number includes bad packets.
This number does not include framing bits but does include FCS octets.