DMPM@DUKEMC.BITNET (James Dryfoos- PostMaster) (02/02/90)
Was just wondering if there is anything out there that explains what each of the fields in the statistics screen of NETWATCH mean? In particular I am interested in the following as I seem to have a number of them. FCS errors, OVERUNs, and DRIBBLEs Appreciate any help. Thanks -Jim
jbvb@VAX.FTP.COM (James Van Bokkelen) (02/02/90)
FCS is another term for the 32 bits of CRC that follow the data in the Ethernet packet. It stands for Frame Check Sequence, I think. LANWatch calls this a CRC error when it displays the packet. An OVERRUN error indicates that data came off the net faster than the interface could store it on the PC (either via the PC's DMA channels to the PC's memory, or via the LAN chip's own DMA to shared memory on the card). DRIBBLE is a 3Com-ism (I think) for packets that didn't end on an even byte boundary. In LANWatch, at least, the only interface that can generate DRIBBLE errors is the 3C500, where I believe It is a synonym for "alignment errors". Other interfaces call the same condition an ALIGN error. James B. VanBokkelen 26 Princess St., Wakefield, MA 01880 FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901
hwajin@ganges.wrs.com (Hwa Jin Bae) (02/05/90)
In article <9002021451.AA16006@vax.ftp.com> jbvb@VAX.FTP.COM (James Van Bokkelen) writes: > DRIBBLE is a 3Com-ism (I think) for packets that didn't end on an even > byte boundary. In LANWatch, at least, the only interface that can > generate DRIBBLE errors is the 3C500, where I believe It is a synonym > for "alignment errors". Other interfaces call the same condition an > ALIGN error. Dribble error is part of the ethernet terminology and some ethernet chips support the generation/detection of this error (e.g. LANCE) so I don't think this is unique to the 3Com or more specifically the boards they manufacture. hwajin -- Hwa Jin Bae, Wind River Systems, Emeryville CA hwajin@wrs.com (uunet!wrs!hwajin) -- Hwa Jin Bae, Wind River Systems, Emeryville CA hwajin@wrs.com (uunet!wrs!hwajin)