Tuesday 3 February 2015

Handling CRC errors

When a CRC error is seen in the FCS on a cut-through port, the Rx CRC counter of the show interface command is incremented. However, the frame cannot be dropped because the FCS is at the end of the Ethernet frame on the wire.

The egress interface increments a Tx CRC error and it propagates through to the next device in the path.

You can use the show hardware internal gatos counters interrupt match stomp command to determine if the Nexus 5000 is propagating CRCs or generating them.

•If stomp values exist, they should have matching CRC values on that interface.

•If Rx CRC values exist, then you know it entered the switchport with the error already. You can move on to the connected device to trace it back.

No comments:

Post a Comment