CANOGA PERKINS 9145ELB NID Software Version 4.01 - Manual (Page 80)

9145ELB NID Software User’s Manual Port Information
RMON Group 1 Statistics
70
Multicasts Rcvd Reports the total number of good packets received that were directed to a
multicast address. Note that this number does not include packets directed to the broadcast
address.
Pkts 64 Reports the total number of packets (including bad packets) received that were 64
octets in length (excluding framing bits but including FCS octets).
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).
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).
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).
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).
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).
Type M and press Enter to see more statistics (Figure 5-16):
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.
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).
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.
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.
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.
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.
Collisions Reports the best estimate of the total number of collisions on this Ethernet segment.