Support Support Downloads Knowledge Base Juniper Support Portal 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

Syslog message: XMCHIP.*XXLCE.*Port Interrupts.*Ethernet *x Stats Parity Error



Article ID: KB31681 KB Last Updated: 06 Oct 2021Version: 4.0

The "Ethernet Rx Stats Parity Error"  or "Ethernet Tx Stats Parity Error" message reports a transient hardware issue.

This is a Troubleshooting Article for a PFE ASIC Syslog Event.
To view other documented syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, see KB31893 - Index of Articles for Troubleshooting PFE ASIC Syslog Events.



When a "Ethernet Rx Stats Parity Error"  or "Ethernet Tx Stats Parity Error" event occurs, a message similar to the following is reported:

Dec 14 05:03:46 router0 : %PFE-3: fpc0 XMCHIP(0): XXLCE0: Port Interrupts: Ethernet Rx Stats Parity Error

Dec 14 05:03:46 router0 : %PFE-3: fpc0 XMCHIP(0): XXLCE0: Port Interrupts: Ethernet Tx Stats Parity Error


  • Single occurrence of syslog may not cause any service impact.

  • Traffic impact or PFE permanent impact on packet forwarding may happen if errors are seen frequently.



The is due to a parity error detected internal to the XMCHIP statistics tracking.



Perform these steps to determine the cause and resolve the problem (if any).  Continue through each step until the problem is resolved.

  1. Collect the show command output.

    Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

    show log messages
    show log chassisd
    start shell network pfe <fpc#>
    show nvram
    show syslog messages

  2. Analyze the show command output.

    In the 'show log messages', review the events that occurred at or just before the appearance of the "Ethernet Rx Stats Parity Error" message. Frequently, these events help identify the cause.

This article is indexed in KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; tag XMCHIPTSG

Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.

Modification History:
2019-10-14: Article reviewed for accuracy; no changes required.
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