This article explains about the syslog message 'MQSS(#): FI: Protect #: Parity error detected for bank # of CP table' when a minor FPC alarm is found and how to resolve the issue.

When a "Parity error detected for bank # of CP table" event occurs, messages similar to the following is reported:

show chassis alarms no-forwarding

1 alarms currently active

Alarm time       Class Description

2024-11-26 03:46:23 CET Minor FPC 9 Minor Errors

Nov 26 03:46:23 MX960 fpc9 MQSS(1): FI: Protect 2: Multiple Errors 0x0

Nov 26 03:46:23 MX960 fpc9 CMError: /fpc/9/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B7 (0x2204bf), scope: pfe, category: functional, severity: minor, module: MQSS(1), type: FI_PAR2_PROTECT: Detected: Bank 7 of CP table

Nov 26 03:46:23 MX960 fpc9 Performing action log for error /fpc/9/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B7 (0x2204bf) in module: MQSS(1) with scope: pfe category: functional level: minor

Nov 26 03:46:23 MX960 fpc9 Performing action cmalarm for error /fpc/9/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B7 (0x2204bf) in module: MQSS(1) with scope: pfe category: functional level: minor

Nov 26 03:46:23 MX960 fpc9 Cmerror Op Set: MQSS(1): MQSS(1): FI: Protect 2: Parity error detected for bank 7 of CP table - data32_log_err 0x80, data32_log_address 0x349 (URI: /fpc/9/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B7)

Nov 26 03:46:23 MX960 chassisd[24703]: CHASSISD_FPC_ASIC_ERROR: <FPC 9> ASIC Error detected errorno 0x002204bf (null)

Nov 26 03:46:25 MX960 craftd[24708]: Minor alarm set, FPC 9 Minor Errors

Nov 26 03:46:25 MX960 alarmd[35010]: Alarm set: FPC id=167774568, color=YELLOW, class=CHASSIS, reason=FPC 9 Minor Errors

Impact:

• A single occurrence of this memory parity error in the log indicates a one-time transient hardware issue. There won’t be any operational impact due to this issue - No Action is required, only a minor alarm will be raised. 
• Multiple occurrence of the above syslog messages occurring frequently on this device, indicates persistent underlying issues and possibly service impact might happen.

Recommendation:

If it is a single occurrence, it can be cleared manually by using the following command in operational mode:

host@router> clear chassis fpc errors fpc-slot fpc-slot all

If this error occurs multiple times on the router, then we may need to restart the affected FPC during the MW time:

host @router> request chassis fpc slot <slot number> offline

Wait for a few minutes.

host@router> request chassis fpc slot <slot number> online

KB32088 [juniper.net]: https://supportportal.juniper.net/s/article/Syslog-message-MQSS-FI-Parity-error-detected-for-bank-of-CP-table