Which interface counter can you use to diagnose a duplex mismatch problem?

Question:
Which interface counter can you use to diagnose a duplex mismatch problem?

• no carrier
• late collisions
• giants
• CRC errors
• deferred
• runts

Explanation: A late collision is defined as any collision that occurs after the first 512 bits of the frame have been transmitted. The usual possible causes are full-duplex/half-duplex mismatch, exceeded Ethernet cable length limits, or defective hardware such as incorrect cabling, non-compliant number of hubs in the network, or a bad NIC.

We can check the interface counter with the “show interface <interface>” command on a Cisco device. For example:

On an Ethernet connection, a duplex mismatch is a condition where two connected devices operate in different duplex modes, that is, one operates in half duplex while the other one operates in full duplex.

Note:
+ Runts are frames which do not meet the minimum frame size of 64 bytes. Runts are usually created by collisions.
+ Giants: frames that are larger than 1,518 bytes

Exam with this question: CCNA v3.0 (200-125) Study Guide – Exam Dumps