CANOGA PERKINS 9145E NID Software Version 3.0 - Manual (Page 84)

9145E NID Software User’s Manual Port Information
RMON Group 1 Statistics
70
20, Pkts 65-127 reports the total number of packets (including bad packets) received that
were between 65 and 127 octets in length inclusive (excluding framing bits but including
FCS octets).
21, Pkts 128-255 reports the total number of packets (including bad packets) received that
were between 128 and 255 octets in length inclusive (excluding framing bits but including
FCS octets).
22, 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).
23, 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).
24, Pkts 1024-1518reports 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).
25, 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.
26, 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,
inclusive, 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).
27, 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.
28, 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.
29, 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 that 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.
30, 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.
31, Collisions reports the best estimate of the total number of collisions on this Ethernet
segment.