Description

The "WI parity error detected" 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] .

.

Symptoms

When a "WI parity error detected" event occurs, a message similar to the following is reported:

Apr 6 06:57:06 router0 member1-fpc3 MQCHIP:MQCHIP(0) WI parity error detected when read from ibuf

Indications:

  • Traffic loss or packet forwarding impact may be seen.
  • Alarm will be raised.

 

Solution

The cause is due to a parity error detected in the internal MQCHIP memory.

 

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

  1. Collect the show command output.

    {SYSLOGSERVICENOWTOKEN.EN_US}

    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 "WI parity error detected" message. Frequently these events help identify the cause.

    • No RMA required with the single occurrence. 

      With the single occurrence, the alarm can be cleared using the command:

      clear chassis fpc errors fpc-slot <x> all

      Note: This command is available in Junos OS 16.1R4-S2, 16.1R5, 16.2R2, 17.1R2, and 17.2R1 or higher.

    • Collect the debugging information using scripts as described in KB31922 [juniper.net] . Restart the FPC and contact your technical support representative if the issue is seen after a FPC restart. RMA may be required.
 

This article is indexed in  KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; tag MQCHIPTSG.


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

2022-10-21 Update KB to be public - missing from previous review
2019-10-14: Article reviewed for accuracy; no changes required.