You are managing a Juniper MX240 router at a small ISP. The router has been operating normally for months. This morning, a customer reports intermittent packet loss on their connection, which is served by interface ge-0/0/2. You SSH into the router and run 'show interfaces ge-0/0/2 extensive'. The output shows input errors increasing rapidly, including CRC errors and frame errors. The interface is up/up. You also notice that the interface statistics show a high number of carrier transitions. The cable connecting the router to the customer's CPE was recently replaced by the customer's technician. What is the most likely cause of the errors and the correct action to resolve the issue?
CRC and frame errors indicate that frames are receiving an invalid FCS, which is a classic symptom of a physical-layer issue such as a damaged cable, loose connector, or excessive signal attenuation. The problem appeared after a recent cable change, which strongly implicates the new cable or its seating. Replacing that cable with a known-good one is the correct first step because it directly tests the most likely failure point, and a clean interface afterward confirms the diagnosis.
Why this answer
CRC and frame errors increasing rapidly, combined with a high number of carrier transitions, are classic symptoms of a physical-layer issue. Since the cable was recently replaced by the customer's technician, the most likely cause is a faulty cable or a loose connector. Replacing the cable with a known good one directly addresses the physical layer problem, which is the root cause of these errors.
Exam trap
The trap here is that candidates may confuse CRC/frame errors with a speed/duplex mismatch (Option D) or think a simple interface reset (Option B) will fix the problem, when the rapid increase in carrier transitions and the recent cable replacement clearly indicate a physical cabling fault.
How to eliminate wrong answers
Option A is wrong because MAC address table clearing addresses MAC flapping, which is a Layer 2 issue unrelated to CRC/frame errors or carrier transitions. Option B is wrong because administratively resetting the interface (shutdown/no shutdown) would only temporarily clear counters and restart the line protocol, but it would not fix the underlying physical-layer problem causing the errors. Option D is wrong because while speed/duplex mismatch can cause errors, the presence of carrier transitions and the recent cable replacement strongly point to a physical cabling issue, not a negotiation mismatch; auto-negotiation is already the default on modern Juniper interfaces and would not resolve a faulty cable.