This article explains how to troubleshoot increasing values in the "Framing errors" counter in the show interfaces extensive command output for Juniper Networks devices.

The value in the "Framing errors" counter in the show interfaces extensive output is seen as shown below:

> show interfaces xe-10/0/0 extensive | match error

Link-level type: Ethernet, MTU: 8980, MRU: 8988, LAN-PHY mode, Speed: 10Gbps, BPDU Error: None, Loop Detect PDU Error: None, Ethernet-Switching Error: None, MAC-REWRITE Error: None, Loopback: None,

Input errors:

Errors: 217928, Drops: 0, Framing errors: 217928, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 1, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0

Output errors:

Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0

Bit errors 2

Errored blocks 16790491

CRC/Align errors 217928 0

FIFO errors 0 0

Output packet error count 0

Flow error statistics (Packets dropped due to):

Incoming NAT errors: 0

User authentication errors: 0

In general Bit errors occur at random intervals due to various reasons which can be counted as PCS Errors. Typically, the PCS errors are attributed to physical processing elements, such as fiber/patch panels / ODF / CFP optics.

Perform the following during a MW

• Check the physical layer.
• Try reseating the port and check the status.
• Try changing the SFP with a spare.