D-Link DFE-2616X User Guide - Page 113
Octets, Packets, Broadcast, Multicast, CRC Align, Undersize, Oversize, Fragment
UPC - 790069212604
View all D-Link DFE-2616X manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 113 highlights
val. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected. ♦ Octets The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). ♦ Packets The number of packets (including bad packets) received during this sampling interval. ♦ 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 non-integral 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 (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Note that it is entirely normal for History Fragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits. Web-Based Network Management 101