Device Manager - Online Help # Go back one pageGo to the next page#Go to this book's Index

Rmon tab fields


Field Description
Octets
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
Number of packets (including bad packets, broadcast packets, and multicast packets) received.
BroadcastPkts
Number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
MulticastPkts
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
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).
UndersizePkts
Number of packets received that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.
OversizePkts
Number of packets received that were longer than 1518 octets (excluding framing bits but including FCS octets) and were otherwise well formed.
Fragments
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). It is entirely normal for etherStatsFragments to increment because it counts both runts (which are normal occurrences due to collisions) and noise hits.
Collisions
Best estimate of the number of collisions on this Ethernet segment.
Jabbers
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.
1..64
Number of packets (including bad packets) received that were less than or equal to 64 octets in length (excluding framing bits but including FCS octets).
65..127
Number of packets (including bad packets) received that were greater than 65 octets in length inclusive (excluding framing bits but including FCS octets).
128..255
Number of packets (including bad packets) received that were greater than 128 octets in length inclusive (excluding framing bits but including FCS octets).
256..511
Number of packets (including bad packets) received that were greater than 256 octets in length inclusive (excluding framing bits but including FCSoctets).
512..1023
Number of packets (including bad) received that were greater than 512 octets in length inclusive (excluding framing bits but including FCS octets).
1024..1518
Number of packets (including bad) received that were greater than 1024 octets in length inclusive (excluding framing bits but including FCS octets).

See also


Go back one pageGo to the next page##Go to this book's Index