Monitoring Rmon Statistics - Dell PowerConnect B-FCXs User Manual

Packets: Broadcast
Packets: Multicast
CRC Alignment Errors
Size Packets: Under
Size Packets: Over
Fragments
Jabbers
Collisions

Monitoring RMON statistics

RMON statistics provides count information on multicast and broadcast packets. This information
includes total packets sent, undersized and oversized packets, CRC alignment errors, jabbers,
collisions, fragments, and dropped events for each port on the system. RMON statistics collection
is activated automatically during system startup, and requires no configuration.
PowerConnect B-Series FCX Web Management Interface User Guide
53-1002268-01
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 longer than 1518 octets 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 be incremented, 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.
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.
The best estimate of the total number of collisions on this Ethernet segment.

Monitoring RMON statistics

3
45