Which interface counter can you use to diagnose a duplex mismatch problem?
A. runts
B. CRC errors
C. no carrier
D. late collisions
E. deferred
F. giants
Which interface counter can you use to diagnose a duplex mismatch problem?
Which interface counter can you use to diagnose a duplex mismatch problem?
A. runts
B. CRC errors
C. no carrier
D. late collisions
E. deferred
F. giants
FROM WIKI: ” In normal half-duplex operations late collisions do not occur. However, in a duplex mismatch the collisions seen on the half-duplex side of the link are often late collisions. The full-duplex side usually will register frame check sequence errors, or runt frames”.
Correct answer B, D.
Answer could be either B. CRC errors or D. Late Collisions
Descriptions: Cisco IOS sh interfaces counter. The number of times a collision occurred before the interface transmitted a frame to the media successfully. Common Causes: Collisions are normal for interfaces configured as half duplex but must not be seen on full duplex interfaces. If collisions increase dramatically, this points to a highly utilized link or possibly a duplex mismatch with the attached device.
CRC Description: Cisco IOS sh interfaces counter. This increments when the CRC generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. Common Causes: This usually indicates noise or transmission problems on the LAN interface or the LAN itself. A high number of CRCs is usually the result of collisions but can also indicate a physical issue (such as cabling, bad interface or NIC) or a duplex mismatch.
Note that they specify late collisions, not collisions. Late collisions occur because of cales beeing too long or a malfunctionning NIC. Collisions are more common in duplex missmatch, Collisions NOT Late Collisions(collision after the 512th bit). Even though CRC errors are less common in duplex mismatches, they are the only other eligible answear.
http://www.firewall.cx/networking-topics/ethernet/195-late-ethernet-collisions.html