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 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] . .
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 Rx Stats Parity Error
Dec 14 05:03:46 router0 : %PFE-3: fpc0 XMCHIP(0): XXLCE0: Port Interrupts: Ethernet Tx Stats Parity Error
Indications:
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.
{DIDYOUKNOWSERVICENOWTOKEN.EN_US} Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
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 exit
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.
Junos OS change was within PR954828 - Error messages "Port Interrupts: Ethernet Rx Stats Parity Error" might be seen to avoid one possible trigger.
No RMA is required
FPC restart during a maintenance window and monitor the errors.
Contact your technical support representative if this occurs again.
This article is indexed in KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; 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.
2019-10-14: Article reviewed for accuracy; no changes required.