Juniper Ethernet Interface Troubleshooting Checklist

When a Juniper router or switch port stays down or drops packets, most engineers jump straight to swapping cables and transceivers. That approach wastes time: Junos gives you a precise, ordered set of diagnostic commands that isolate the fault in minutes. This guide condenses the official Juniper troubleshooting checklist for Ethernet physical interfaces on M, MX and T series platforms into a practical workflow with real CLI output.

Why Use a Structured Juniper Interface Checklist

Physical-layer faults account for the majority of "port down" tickets, but the root cause can be anything from a dirty optical connector to an unsupported transceiver. Working through the checklist from the physical layer upward prevents duplicate work and gives you evidence — interface statistics, alarm states, loopback results — before you escalate to JTAC.

Step 1: Verify the Physical Link Status

Start with the show interfaces ge-5/0/1 media operational command to check whether the physical link is up and whether alarms or defects are active. A healthy port shows Physical link is Up with Active alarms: None and Active defects: None. If the link is down, confirm cabling on both ends and swap in a known-good cable before going further.

user@router> show interfaces ge-5/0/1 media
Physical interface: ge-5/0/1, Enabled, Physical link is Up
Interface index: 317, SNMP ifIndex: 1602
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps
Active alarms  : None
Active defects : None

Step 2: Inspect Detailed Interface Statistics

If the link is up but traffic suffers from errors or loss, run show interfaces ge-5/0/1 extensive. Pay attention to input errors, framing errors and the physical-layer counters. Rising FCS or framing errors point to bad optics or marginal cable quality rather than configuration issues.

Step 3: Run Loopback Tests to Isolate the Fault

Loopback testing separates a faulty port/PIC from a faulty cable or remote peer. Configure the internal loopback under [edit interfaces ge-5/0/1 gigether-options] with the loopback statement; the link should come up cleanly with no alarms if the local hardware is healthy. For fiber interfaces you can also physically loop TX to RX on the port and re-check show interfaces ge-5/0/1 media.

Step 4: Check Administrative State and Auto-Negotiation

Use show interfaces ge-5/0/1 terse to confirm the interface is not administratively disabled, and verify that speed, duplex and auto-negotiation in the extensive output match the peer. Speed mismatches are a classic cause of intermittent links that no amount of cable swapping will fix.

Step 5: Validate Transceiver Compatibility

Transceivers that are not on the Juniper Hardware Compatibility Tool are a frequent hidden cause of flapping ports. Reseat and clean the optics at both ends, swap in a known-working module, and check the hold-time and damping configuration if the port flaps instead of staying down — damping can mask a marginal link for hours. If every step passes and the port still fails, collect show interfaces output and contact JTAC for an RMA assessment.

Related reading: how to identify a flapped interface with Junos CLI and troubleshooting a LAN where static hosts never answer.

原文链接：https://supportportal.juniper.net/s/article/Troubleshooting-Checklist-Ethernet-Physical-Interfaces