The "FI Protect Parity error for freepool SRAM" message reports a transient hardware memory error.

XM Chip Error codes: 0x70134 0x70133

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

Oct 14 23:55:05 router0 fpc0 XMCHIP(1):XMCHIP(1): FI: Protect: Parity error for CP freepool SRAM (List pointers get dropped)
Nov 5 00:20:59 router1 : %PFE-0: fpc0 :XMCHIP(0): FI: Protect: Parity error for L2 freepool SRAM (List pointers get dropped)

Another example with the XM error code as follow:

Oct 18 11:58:54.165 router0 craftd[12385]:  Major alarm set, FPC 1 Major Errors - XM Chip Error code: 0x70134
Oct 18 11:58:54.165 2021 router0 alarmd[13287]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 1 Major Errors - XM Chip Error code: 0x70134

Indications:

• A single occurrence in the Syslog, not seen with other events, indicates a one-time transient hardware error.
• Multiple continuous occurrences indicate persistent underlying issues.
• The MAJOR alarm will be raised. The default behavior for PFE MAJOR alarm is to disable interfaces of the PFE
• PFE disable action may be performed based on the junos version.

This is a transient hardware error. This is the only SRAM parity error that looks like a transient condition and does not compromise packet forwarding with simulations in-house. It causes a leak of the list pointers and affects the throughput performance of this pool at Fabric Input.  It is not clear how many pointers get affected and it is un-deterministic. In production, you may not see an impact. However, if you make 100% throughput performance measurements, then you could see an impact. The suggestion is to restart the MPC at next the convenient time.

RECOMMENDED ACTION

• No RMA is required.

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

  • clear chassis fpc errors fpc-slot <x> all

  • Note:  This command is available in Junos OS 14.2R8, 15.1R7, 15.1X49-D140, 16.1R4-S2, 16.1R5, 16.2R3, 17.1R2, and 17.2R1 or higher.

• If the interfaces were disabled, restart the FPC during a Maintenance Window to clear the alarm

• Contact your technical support representative for more analysis.

{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 " FI Protect Parity error for freepool SRAM " message. Frequently these events help identify the cause.

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.

2022-12-22: Update the format no change in content
2022-05-20: Update to include XM error code: 0x70134
2018-05-01: Updated list of Junos releases that have the "clear chassis fpc error" command available.