This article explains how to troubleshoot increasing values in the "Framing errors" counter in the show interfaces extensive command output for Juniper Networks devices.
show interfaces extensive
The value in the "Framing errors" counter in the show interfaces extensive output is seen to be increasing as shown below:
user@srx>show interfaces extensive Physical interface: ge-0/0/0, Enabled, Physical link is Up Interface index: 134, SNMP ifIndex: 505, Generation: 137 Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Hold-times : Up 0 ms, Down 0 ms Current address: 00:26:88:eb:62:c0, Hardware address: 00:26:88:eb:62:c0 Last flapped : 2012-06-04 14:39:14 UTC (00:35:10 ago) Statistics last cleared: Never Traffic statistics: Input bytes : 30972 0 bps Output bytes : 0 0 bps Input packets: 427 0 pps Output packets: 0 0 pps Input errors: Errors: 0, Drops: 0, Framing errors: 156, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, 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 Egress queues: 12 supported, 5 in use Queue counters: Queued packets Transmitted packets Dropped packets 0 8188558616 8180261608 8297008 3 0 0 0 4 0 0 0 7 14833185 14833185 0 8 19892 19892 0
Output drops can also be seen due to the presence of framing errors on the affected interface.Note: See KB24601 - [MX/SRX] Meaning of the input and output errors in the 'show interface extensive' command [juniper.net] for more information about the input and output errors.
Framing errors" are the number of packets received with an invalid frame checksum (FCS). This is typically due to a physical issue [such as cabling, a bad port, or a bad Network Interface Card (NIC)], but can also indicate a duplex mismatch.
To resolve the issue, check the following:
If the framing error is resolved when SFP is changed, RMA needs to be processed for faulty SFP If framing errors is resolved when port is changed , RMA needs to be processed for faulty Chassis
If the issue occurs even after doing the above, check the peer device to see if its FCS error output counter is increasing and perform troubleshooting on the peer device.Please open a Jtac case if you still observing framing error after executing the above steps.
2020-02-27: Article reviewed for accuracy; no changes required.2023-03-21: Added all Junos to categories. 2023-07-24: Added technical points