CANOGA PERKINS 9145E10G NID Software Version 1.0 - Manual (Page 81)

Port Information 9145E10G NID Software User’s Manual
RMON Group 1 Statistics
69
8. Pkts 256-511 - reports the total number of packets (including bad packets) received that
were between 256 and 511 octets in length inclusive (excluding framing bits but including
FCS octets).
9. Pkts 512-1023 - reports the total number of packets (including bad packets) received
that were between 512 and 1023 octets in length inclusive (excluding framing bits but
including FCS octets).
10. Pkts 1024-1518 - reports the total number of packets (including bad packets) received
that were between 1024 and 1518 octets in length inclusive (excluding framing bits but
including FCS octets).
11. Drop Events - reports the total number of events in which packets were dropped by the
probe due to lack of resources. Note that this number is not necessarily the number of
packets dropped; it is just the number of times this condition has been detected.
12. CRC/Align Errors - reports the total number of packets received that had a length
(excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclu-
sive, but had either a bad Frame Check Sequence (FCS) with an integral number of
octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
13. Undersize - reports 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.
14. Oversize - reports the total number of packets received that were longer than 1518
octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
15. Fragments - reports 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 Frame
Check Sequence (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 entirely normal for Fragments to increment. This is because it
counts both runts (which are normal occurrences due to collisions)
and noise hits.
16. Jabbers - reports the total number of packets received that were longer than 1518 octets
(excluding framing bits, but including FCS octets), and had either a bad Frame Check
Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-
integral number of octets (Alignment Error). The allowed range to detect jabber is
between 20 ms and 150 ms.
17. Collisions - reports the best estimate of the total number of collisions on this Ethernet
segment.