Hi all, I'm trying to confirm (or debunk) my current understanding of FCS errors. An FCS error is a layer 2 error. In Ethernet spake, the 4 bytes of FCS data within each Ethernet frame is validated by a CRC check, which is done by the device receiving said frame. If the CRC check fails, an FCS error is reported by that receiving device. If that understanding is true and presuming a "circuit" was made up of many layer 2 devices between the A and Z side of said circuit, it would be impossible for a CRC error somewhere along the path of that circuit to register on the receiving device of either the A or Z side. Perhaps in simpler terms, a CRC error is a localized thing and would never be forwarded from one device to another. Is that fair and/or accurate? Thanks in advance.
On 2012-12-19, at 10:02 AM, Saku Ytti <saku@ytti.fi> wrote:
On (2012-12-19 09:53 -0500), Jason Lixfeld wrote:
Perhaps in simpler terms, a CRC error is a localized thing and would never be forwarded from one device to another.
It would be forwarded in cut-through switching.
... until the bad frame reached the first store-and-forward switch (or most any router) which would log the FCS error, correct?
On 12/19/12 7:02 AM, Saku Ytti wrote:
On (2012-12-19 09:53 -0500), Jason Lixfeld wrote:
Perhaps in simpler terms, a CRC error is a localized thing and would never be forwarded from one device to another. It would be forwarded in cut-through switching.
I have cut-through switches (arista) that log these as TX errors, they have already left the barn at that point.
On 24/12/2012 00:39, joel jaeggli wrote:
I have cut-through switches (arista) that log these as TX errors, they have already left the barn at that point.
it's a real pain when this happens because you have no idea of the ingress port and consequently the source of the data corruption source. The same happens for regular packet drops on some cut-thru switches (e.g. brocade ti-24x). Annoying. Nick
participants (4)
-
Jason Lixfeld -
joel jaeggli -
Nick Hilliard -
Saku Ytti