Dell PowerConnect B-RX Configuration Manual page 1094

38
RMON support
TABLE 161
This line...
CRC alignment errors
Undersize pkts
Fragments
Oversize packets
Jabbers
Collisions
64 octets pkts
65 to 127 octets pkts
128 to 255 octets pkts
256 to 511 octets pkts
1022
Export configuration and statistics (Continued)
Displays...
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.
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 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
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.
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.
NOTE: Not supported in BigIron RX
The total number of packets received that were 65 – 127 octets long.
This number includes bad packets.
This number does not include framing bits but does include FCS
NOTE: Not supported in BigIron RX
The total number of packets received that were 128 – 255 octets long.
This number includes bad packets.
This number does not include framing bits but does include FCS octets
NOTE: Not supported in BigIron RX.
The total number of packets received that were 256 – 511 octets long.
This number includes bad packets.
This number does not include framing bits but does include FCS octets.
NOTE: Not supported in BigIron RX.
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.
BigIron RX Series Configuration Guide
53-1001810-01