The "Parity error corrected for buffer free list memory for bank" message reports a transient hardware error which was automatically corrected. 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 "Parity error corrected for buffer free list memory for bank" event occurs, messages similar to the following is reported:
Oct 10 14:50:12 router-0 fpc1 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x8000Oct 10 14:50:12 router-0 fpc1 MQSS(1):MQSS(1): BCMF CBUF: SRAM ECC Protect: Parity error corrected for buffer free list memory for bank *
The following log messages also seen on the Flexible PIC Concentrator (FPC) for the same error:
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0<Date> <Time> mx960 Error: /fpc/4/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK0_FMEM (0x22009d), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0 <Date> <Time> mx960 Error: /fpc/0/pfe/0/cm/0/MQSS(3)/3/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK1_FMEM (0x22009e), scope: pfe, category: functional, severity: minor, module: MQSS(3), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(0): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0 <Date> <Time> mx960 Error: /fpc/17/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK2_FMEM (0x22009f), scope: pfe, category: functional, severity: minor, module: MQSS(0), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0<Date> <Time> mx960 Error: /fpc/9/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK3_FMEM (0x2200a0), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0<Date> <Time> mx960 Error: /fpc/2/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK4_FMEM (0x2200a1), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0<Date> <Time> mx960 Error: /fpc/4/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK5_FMEM (0x2200a2), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0<Date> <Time> mx960 Error: /fpc/1/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK6_FMEM (0x2200a3), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
<Date> <Time> mx960 MQSS(1): BCMF CBUF: SRAM ECC Protect: Multiple Errors 0x0<Date> <Time> mx960 Error: /fpc/1/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK7_FMEM (0x2200a4), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: BCMF_CBUF_SRAM_ECC_PROTECT: Corrected: Buffer free
Same errors with similar tags:
MQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK0_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK1_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK2_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK3_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK4_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK5_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK6_FMEMMQSS_CMERROR_BCMF_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED_BNK7_FMEM
Indications:
Single occurrence of the syslog message and is not seen with other events indicate a one time transient hardware error with no operational impact
Multiple continuous occurrences indicate persistent underlying issues
Minor Alarm will be raised
This is due to a transient hardware SRAM error with EACHIP.
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 "Parity error corrected for buffer free list memory for bank" message. Frequently these events help identify the cause.
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 16.1R4-S2, 16.1R5, 16.2R2, 17.1R2, and 17.2R1 or higher.
Wait for a few minutes.
OR
Further Assistance:
If the issue remains unresolved, please contact Juniper Technical Support for further investigation.
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.
Updated the KB with different MQSS_CMERROR_BCM F_CBUF_FI_SRAM_ECC_PROTECT_FSET_REG_CORRECTED error logs.