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: EA.*Checksum error detected on

0

0

Article ID: KB32335 KB Last Updated: 11 Oct 2021Version: 3.0
Summary:

The "Checksum error detected on" messages are caused by corrupted cell received from the HMC (Hybrid Memory Cube) interfaces failing ECC Checksum.

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.

.

Symptoms:

When a 'Checksum error detected on event occurs', a message similar to the following is reported for both FO or WO side like:

  • HMCIF Rx: Checksum error detected on FO response‚Äč

  • HMCIF Rx: Checksum error detected on WO response‚Äč

Jul 19 16:42:17 MX2020-RE1 fpc19 eachip_hmcif_rx_intr_handler(7324): EA[3:0]: HMCIF Rx: Checksum error detected on FO response - Chunk Address 0xd7c599
Jul 19 16:42:18 MX2020-RE1 fpc10 MQSS(2): FI: Error cell sent to reorder engine - Stream 78, Count 37
Jul 19 16:42:18 MX2020-RE1 fpc10 MQSS(3): FI: Error cell sent to reorder engine - Stream 79, Count 11
Jul 19 16:42:18 MX2020-RE1 fpc19 MQSS(2): FO: Packet Error - Error Packets 28, Stream 42
Jul 19 16:42:18 MX2020-RE1 fpc19 eachip_hmcif_rx_intr_handler(7324): EA[2:0]: HMCIF Rx: Checksum error detected on FO response - Chunk Address 0xbad57b
Jul 19 16:42:18 MX2020-RE1 fpc19 MQSS(3): FO: Packet Error - Error Packets 11, Stream 43
Jul 19 16:42:18 MX2020-RE1 fpc19 eachip_hmcif_rx_intr_handler(7324): EA[3:0]: HMCIF Rx: Checksum error detected on FO response - Chunk Address 0x53d21e
Jul 19 16:42:19 MX2020-RE1 fpc10 MQSS(2): FI: Error cell sent to reorder engine - Stream 78, Count 32
Jul 19 16:42:19 MX2020-RE1 fpc10 MQSS(3): FI: Error cell sent to reorder engine - Stream 79, Count 7
Jul 19 16:42:19 MX2020-RE1 fpc19 MQSS(2): FO: Packet Error - Error Packets 39, Stream 42
Jul 19 16:42:19 MX2020-RE1 fpc19 eachip_hmcif_rx_intr_handler(7324): EA[2:0]: HMCIF Rx: Checksum error detected on FO response - Chunk Address 0x949175
Jul 19 16:42:19 MX2020-RE1 fpc19 MQSS(3): FO: Packet Error - Error Packets 4, Stream 43
Jul 19 16:42:19 MX2020-RE1 fpc19 eachip_hmcif_rx_intr_handler(7324): EA[3:0]: HMCIF Rx: Checksum error detected on FO response - Chunk Address 0x53d21e
Jul 19 16:42:19 MX2020-RE1 fpc10 Cmerror Op Set: CM[3]: MPC fabric remote PFE error (rate based) (1) exceed raising threshold (1) occurrance (3) for module/pfe (11:3)
Jul 19 16:42:19 MX2020-RE1 fpc10 Cmerror Op Set: CM[3]: MPC fabric remote PFE error (aggregate based) (1) exceed raising threshold (1) occurrance (3) for module/pfe (11:3)


Indications:

  • Packets will be dropped at the remote PFEs with error message, "Error sent to reorder engine".

  • The volume of packets being dropped is related to the number of Error cell sent to reorder engine counter.

  • Minor Alarm will be raised in FI block if the error rate is reaching the threshold of 100 per second.  The PFE reporting the FI errors is usually not the fault location.

Cause:

ECC validation has detected an error once receiving the cells from the HMC(Hybrid Memory Cube) interface

Solution:



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
    exit

  2. Analyze the show command output.

    In the 'show log messages', review the events that occurred at or just before the appearance of the "Checksum error detected" message. Frequently these events help identify the cause.

  • If  after FPC restart reporting the "Checksum error detected on"  and this FPC is not passing the internal Power on Self Test (POST) and reports "Error initializing PFE asics" Hardware Replacements needs to be initiated.

  • Contact your technical support representative if this issue is seen again after FPC restart.

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


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:

Note: KB Team - All changes to this article must be approved by the AI-Scripts Review team (pvs-scripts-review@juniper.net) before re-publishing.


AI-Scripts history:       (Updated by AI-Scripts team only)
 
Date KB Article Version AI-Scripts PR (optional) Notes
1/16/2018 1.0 1332634 New Syslog KB
       

 
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