Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!think.com!cass.ma02.bull.com!mips2!granite!piacenti
From: piacenti@granite.ma30.bull.com (Paul Piacentini)
Newsgroups: comp.protocols.tcp-ip
Subject: ethernet alignment errors
Message-ID: <1991May30.022715.22240@granite.ma30.bull.com>
Date: 30 May 91 02:27:15 GMT
Sender: piacenti@granite.ma30.bull.com (Paul Piacentini)
Organization: Bull HN Information Systems Inc.
Lines: 22


  Most of our ethernet equipment, analyzers, etc report counters on bytes,
packets, CRC errors, collisions, runts, giants, and frame alignment errors.
I'm a little fuzzy on exactly what consistutes a frame alignment error.
Is it a packet that was transmitted within the minimum IEEE inter-packet delay
spec window (9.6 usec?) ?
If that's the case, is it tallied up as an aligment error by every device that
saw it, ALONG with being tallied as a transmitted packet? Or does it count as
an error and get discarded as a non-valid packet? Does the destination ignore
it and wait for a retransmit?
Are they caused by a bad transceiver? controller timing problems? bad carrier
detection? software greedy for the bandwidth?

Can anyone enlighten me on this .. an inquiring mind wants to know

thanks, Paul

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 _\ /_              Paul E. Piacentini |  Bull Worldwide Info Systems
  / \   piacenti@granite.ma30.bull.com |  300 Concord Rd. MA30-857     _\ /_
                        (508) 294-3450 |  Billerica, Mass 01821         / \