Courseiva

Duplex Mismatch Troubleshooting: Late Collisions and CRC Errors

Exhibit

R1# show interfaces FastEthernet0/0
FastEthernet0/0 is up, line protocol is up
  Hardware is Gt96k FE, address is 00ab.cd12.3456 (bia 00ab.cd12.3456)
  Internet address is 192.168.1.1/24
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 100Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  5 minute input rate 31000 bits/sec, 40 packets/sec
  5 minute output rate 28000 bits/sec, 36 packets/sec
     12345 packets input, 987654 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     5678 packets output, 345678 bytes, 0 underruns
     0 output errors, 41 collisions, 0 interface resets
     0 babbles, 17 late collision, 0 deferred

Refer to the exhibit. A network engineer is troubleshooting intermittent connectivity between a branch router and the upstream switch. The switch port is manually configured for 100 Mb/s full duplex, and the Ethernet cable has been tested and is working properly. The router interface was left at its default settings. The engineer runs show interfaces FastEthernet0/0 on the router. Based on the output, what is the most likely cause of the problem?

Quick Answer

The answer is a duplex mismatch, specifically that the router interface is operating in half-duplex while the upstream switch port is set to full-duplex. This is the most likely cause because the show interfaces output reveals 'Half-duplex, 1000Mb/s' alongside 17 late collisions and 23 input CRC errors—classic symptoms of duplex mismatch troubleshooting scenarios where one side expects to transmit and receive simultaneously while the other cannot. On the CCNA 200-301 v2 exam, this question tests your ability to correlate interface statistics with configuration mismatches, often using a trap where a bad cable is blamed first; however, the cable is already verified as working. The presence of late collisions on a GigabitEthernet link is the definitive clue, as full-duplex links should never have collisions. Memory tip: Late collisions = duplex confusion; if you see them, check both sides for speed and duplex agreement.

⚠ Common exam trap

Late collisions on a link that looks healthy at Layer 1 are the duplex mismatch signature. The cable has been ruled out and the switch is known to be full duplex, so the router side is the one that is wrong.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The router interface is operating in half duplex while the switch port is full duplex, causing a duplex mismatch.

The router shows Half-duplex, 100Mb/s with collisions and 17 late collisions, while the switch port is hard-coded to full duplex. A hard-coded port does not negotiate, so the router's auto-negotiating interface detects the speed but falls back to half duplex. The full-duplex switch transmits without carrier sense, causing the router to see late collisions. This duplex mismatch causes intermittent connectivity under load. Set both sides to the same duplex, ideally full duplex.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    The switch port is configured for half-duplex instead of the expected full-duplex.

    Why it's wrong here

    The stem states the switch port is manually set to full duplex. If both sides were half duplex there would be no mismatch and late collisions would not be expected.

  • ✗

    The cable is faulty, causing excessive late collisions and CRC errors.

    Why it's wrong here

    The cable has already been tested and works. Late collisions here come from the duplex mismatch between the auto-negotiated half-duplex router and the forced full-duplex switch.

  • ✓

    The router interface is operating in half duplex while the switch port is full duplex, causing a duplex mismatch.

    Why this is correct

    The output shows Half-duplex, 100Mb/s with 41 collisions and 17 late collisions. With the switch hard-coded to full duplex, this is a classic duplex mismatch.

  • ✗

    The excessive input errors are a result of a broadcast storm on the network.

    Why it's wrong here

    A broadcast storm would show a very high number of broadcasts received. The exhibit shows zero broadcasts, and storms do not cause late collisions.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.

✓The router interface is operating in half duplex while the switch port is full duplex, causing a duplex mismatch.Correct answer▾

Why this is correct

The output shows Half-duplex, 100Mb/s with 41 collisions and 17 late collisions. With the switch hard-coded to full duplex, this is a classic duplex mismatch.

✗The switch port is configured for half-duplex instead of the expected full-duplex.Wrong answer — click to see why▾

Why this is wrong here

Users often think any collision indicator points to both sides being half-duplex, ignoring the known switch configuration.

✗The cable is faulty, causing excessive late collisions and CRC errors.Wrong answer — click to see why▾

Why this is wrong here

Late collisions are commonly associated with physical layer issues, leading candidates to assume a cable problem even when explicitly ruled out.

✗The excessive input errors are a result of a broadcast storm on the network.Wrong answer — click to see why▾

Why this is wrong here

Candidates see input errors and CRC and prematurely conclude a loop or broadcast storm, overlooking that the output shows no broadcast activity and contains late collisions specific to duplex issues.

Analysis generated from the official 200-301 blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

About these practice questions

Courseiva writes every 200-301 question from scratch — 1,352 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on 200-301

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You are troubleshooting connectivity between R1 and R2. The link is up but users report intermittent packet loss. Examine the provided show interface output on R1, identify the root cause, and apply the necessary fix to restore normal operation. R1# show interface GigabitEthernet0/0 GigabitEthernet0/0 is up, line protocol is up (connected) Hardware is Gigabit Ethernet, address is 0011.2233.4455 MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is RJ45 input flow-control is off, output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:01, output 00:00:01, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 1000 bits/sec, 1 packets/sec 5 minute output rate 1000 bits/sec, 1 packets/sec 2453 packets input, 213456 bytes, 0 no buffer Received 500 broadcasts (0 multicasts) 0 runts, 0 giants, 0 throttles 312 input errors, 312 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 3211 packets output, 345678 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 unknown protocol drops 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out

hard
  • A.Configure 'duplex auto' and 'speed auto' on interface G0/0 of R1.
  • ✓ B.Replace the faulty cable between R1 and R2.
  • C.Increase the MTU size on interface G0/0 of R1.
  • D.Disable CDP on interface G0/0 of R1.

Why B: The output shows the interface is operating at Full-duplex, 1000Mb/s, but is experiencing a high number of input errors and CRC errors. On Gigabit Ethernet, a duplex mismatch is not possible because 1000BASE-T operates in full-duplex mode only. The CRC and input errors point to physical layer problems, such as a faulty cable or connector, causing intermittent packet loss. Replacing the cable between R1 and R2 is the appropriate fix.

You might also like

Similar 200-301 questions

Written and reviewed by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

Last reviewed November 2026 · checked against the official Cisco exam blueprint

This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.