# Ethernet Errors

From this dialog box, you can view the Ethernet error details for an interface.

## Navigation

Right-click the port and then select Monitor > Ethernet Errors.

The following information is displayed:

> MAC Tx (dot3StatsInternalMacTransmitErrors)

> MAC Rx (dot3StatsInternalMacReceiveErrors)

> SQE Test (dot3StatsSQETestErrors)

> Carrier Sense (dot3StatsCarrierSenseErrors)

> Giant Frames (dot3StatsFrameTooLongs)

> Alignment Check Errors (dot3StatsAlignmentErrors)

> Deferred Transmissions (dot3StatsDeferredTransmissions)

> FCS Errors (dot3StatsFCSErrors)

> Symbol Errors (dot3StatsSymbolErrors)

### MAC Tx (dot3StatsInternalMacTransmitErrors)

Number of frames for which transmission failed because of an internal MAC layer transmit error. (These are transmit errors that were not picked up in any other count.)

### MAC Rx (dot3StatsInternalMacReceiveErrors)

Number of frames for which reception failed because of an internal MAC layer receive error. (These are receive errors that were not picked up in any other count.)

### SQE Test (dot3StatsSQETestErrors)

Number of times the PLS sub-layer generated the Signal Quality Error for a particular interface.

### Carrier Sense (dot3StatsCarrierSenseErrors)

Number of transmission attempts that failed because the carrier sense condition was lost or never asserted.

### Giant Frames (dot3StatsFrameTooLongs)

Number of received frames that are bigger than maximum permitted size.

A giant frame indicates that a nonlocal software error occurred or that a protocol using nonstandard frame lengths is in use.

### Alignment Check Errors (dot3StatsAlignmentErrors)

Number of frames with alignment errors. An alignment error occurs when the frame length is not an integral number of octets and the frame cannot pass the FCS test.

Alignment errors are usually caused by a nonlocal network problem.

### Deferred Transmissions (dot3StatsDeferredTransmissions)

A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

### FCS Errors (dot3StatsFCSErrors)

A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. Note: Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the frame to fail the FCS check. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

### Symbol Errors (dot3StatsSymbolErrors)

For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.