D-Link D-View 5.1 User Manual page 175

Network management system
Hide thumbs Also See for D-View 5.1:
Table of Contents

Advertisement

D-View 5.1 User's Guide
♦ Broadcast – The number of good packets received during this sampling interval
that were directed to the broadcast address.
♦ Multicast – The number of good packets received during this sampling interval
that were directed to a multicast address. Note that this number does not
include packets addressed to the broadcast address.
♦ CRC Align – The number of packets received during this sampling interval that
had a length (excluding framing bits but including FCS octets) 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).
♦ Undersize – The number of packets received during this sampling interval that
were less than 64 octets long (excluding framing bits but including FCS octets)
and were otherwise well formed.
♦ Oversize – The number of packets received during this sampling interval that
were longer than 1518 octets (excluding framing bits but including FCS octets)
but were otherwise well formed.
♦ Fragment – The total number of packets received during this sampling interval
that were less than 64 octets in length (excluding framing bits but including
FCS octets) had either a bad Frame Check Sequence (FCS) with an integral
number of octets (F CS Error) or a bad FCS with a non-integral number of octets
(Alignment Error). Note that it is entirely normal for etherHistoryFragments to
increment. This is because it counts both runts (which are normal occurrences
due to collisions) and noise hits.
♦ Jabber – The number of packets received during this sampling interval 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). Note that this definition of jabber is different than the definition in IEEE-
802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition where any packet exceeds 20 ms. The
allowed range to detect jabber is between 20 ms and 150 ms.
♦ Collision – The best estimate of the total number of collisions on this Ethernet
segment during this sampling interval.
♦ Utilization – The best estimate of the mean physical layer network utilization
on this interface during this sampling interval, in hundredths of a percent.
169

Advertisement

Table of Contents
loading

Table of Contents