This Document helps in troubleshooting "MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B13 (0x2204c5)"FPC minor error.

Log messages:

Dec 24 03:56:16 2024 re0.LabRouter fpc1 MQSS(0): FI: Protect 2: Multiple Errors 0x2000 
Dec 24 03:56:16 2024 re0.LabRouter fpc1 Error: /fpc/1/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B13 (0x2204c5), scope: pfe, category: functional, severity: minor, module: MQSS(0), type: FI_PAR2_PROTECT: Detected: Bank 13 of CP table 
Dec 24 03:56:16 2024 re0.LabRouter fpc1 Performing action log for error /fpc/1/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B13 (0x2204c5) in module: MQSS(0) with scope: pfe category: functional level: minor 
Dec 24 03:56:16 2024 re0.LabRouter fpc1 Performing action cmalarm for error /fpc/1/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B13 (0x2204c5) in module: MQSS(0) with scope: pfe category: functional level: minor 
Dec 24 03:56:16 2024 re0.LabRouter fpc1 Cmerror Op Set: MQSS(0): MQSS(0): FI: Protect 2: Parity error detected for bank 13 of CP table - data32_log_err 0x2000, data32_log_address 0x1ac (URI: /fpc/1/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_FI_PAR2_PROTECT_FSET_REG_DETECTED_LUT_CP_B13) 
Dec 24 03:56:17 2024 re0.LabRouter chassisd[8307]: CHASSISD_FPC_ASIC_ERROR: <FPC 1> ASIC Error detected errorno 0x002204c5 (null)
Dec 24 03:56:17 2024 re0.LabRouter craftd[8310]: Minor alarm set, FPC 1 Minor Errors
Dec 24 03:56:17 2024 re0.LabRouter alarmd[33372]: Alarm set: FPC id=167772520, color=YELLOW, class=CHASSIS, reason=FPC 1 Minor Errors

Indications: 

• A single occurrence of syslog and not seen with other events indicate a one-time transient hardware error with no operational impact - No Action is needed
• Multiple Syslog entries per second indicate persistent underlying issues and possibly service impact - Recommend Action - to RMA the affected MPC
• The Minor Alarm will be raised

This is due to a transient hardware SRAM error within EACHIP Fabric input block.

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.

1. 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.
2. show log messages
3. show log chassisd
4. start shell pfe network <fpc#>
5. show cmerror module brief
6. show nvram
7. show syslog messages
8. 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 detected for bank .. of CP table" message. Frequently these events help identify the cause.

• No RMA is required
• With a single occurrence, the alarm can be cleared using the command:
  • clear chassis fpc errors fpc-slot  <x> all