Nortel Networks 214393-A describes the RMON tab fields, Configuring and graphing ports, Field

Chapter 3 Configuring and graphing ports 95

Table 36 describes the RMON tab fields.

Table 36 RMON tab fields

Field	Description
Octets	The total number of octets of data (including those in bad packets)
	received on the network (excluding framing bits but including
	FCS octets). You can use this object as a reasonable estimate of
	Ethernet utilization. For greater precision, sample the etherStatsPkts
	and etherStatsOctets objects before and after a common interval.
Pkts	The total number of packets (including bad packets, broadcast
	packets, and multicast packets) received.
BroadcastPkts	The total number of good packets received that were directed to the
	broadcast address. Note that this does not include multicast packets.
MulticastPkts	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.
CRCAlignErrors	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 nonintegral
	number of octets (Alignment Error).
UndersizePkts	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.
OversizePkts	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	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 nonintegral number of octets
	(Alignment Error). It is entirely normal for etherStatsFragments to
	increment because it counts both runts (which are normal occurrences
	due to collisions) and noise hits.
Collisions	The best estimate of the total number of collisions on this Ethernet
	segment.
Jabbers	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). Jabber is defined as the condition where
	any packet exceeds 20 ms. The allowed range to detect jabber is
	between 20 ms and 150 ms.

Reference for the BayStack 380-24F Gigabit Switch Management Software