Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SRX] How to troubleshoot increase in "Framing errors" counter value

0

0

Article ID: KB27597 KB Last Updated: 27 Feb 2020Version: 7.0
Summary:

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

 

Symptoms:

The value in the "Framing errors" counter in the show interface extensive output is seen to be increasing as shown below:

user@srx>show interface 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

Note: See KB24601 - [MX/SRX] Meaning of the input and output errors in the 'show interface extensive' command for more information about the input and output errors.

 

Cause:

"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.

 

Solution:

To resolve the issue, check the following:

  1. Check the duplex setting on both sides of the devices. Make sure that both are using full duplex.

  2. Change to another good cable to exclude bad or damaged cable issues.

  3. Change to another port to exclude NIC card issues.

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.

 

Modification History:

2020-02-27: Article reviewed for accuracy; no changes required.

 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search