Description

The "WI CPQ Free Pointer SRAM Protect: Parity error" message reports a transient hardware memory parity error.


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 CPQ Free Pointer SRAM Protect: Parity error" event occurs, a message similar to the following is reported:

Feb 14 16:29:07 router0 fpc19 XMCHIP(3):XMCHIP(3): WI0: WI CPQ Free Pointer SRAM Protect: Parity error (0x4)

Indications:

  • A single occurrence of the syslog, not seen with other events, indicates one time hardware error. Multiple continuous occurrences indicates persistent underlying issues.

  • No permanent impact of packet forwarding

  • Alarm will be raised.

  • For each error entry, few data traffic packet drops could be seen, but the losses aren’t persistent and traffic should resume at 100% as before.

 

Solution

The cause is due to a transient hardware parity error detected on the chip. If there is a service impact, then other events will be reported.

 

{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

Analyze the show command output.

In the 'show log messages', review the events that occurred at or just before the appearance of the "WI CPQ Free Pointer SRAM Protect: Parity error" message. Frequently these events help identify the cause.

  1. ​No RMA required.

  2. With the single occurrence, the alarm can be cleared using command, clear chassis fpc errors fpc-slot <x> all

  3. This alarm is reclassified to minor via PR1388998

  4. The multiple continuous occurrences of errors require FPC restart during MW window to clear the alarms.


Contact your Juniper support representative if the issue is seen after a FPC restart.

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.

 

Modification History

2019-09-30: Article reviewed for accuracy; no changes required.
2021-09-23: Added 3rd point "This alarm is reclassified to minor via PR1388998" in the solution Tab
2023-10-11: updated categories section.