This article provides guidance on identifying and resolving the `MQSS_CMERROR_BCMF_ICM_FI_RORD_PROTECT_FSET_REG_DETECTED_HRORD1` error observed on a FPC indicating a Packet Forwarding Engine (PFE) issue.

FPC detected a memory parity error in the MQSS fabric-side Input Chunk Mover(ICM) Reorder (HRORD1) memory block

The following error message is observed in the system logs, pointing to a hardware error on the PFE:

fpc2 MQSS(1): BCMF ICM: RORD Protect: Multiple Errors 0x4
fpc2 CMError: /fpc/2/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_BCMF_ICM_FI_RORD_PROTECT_FSET_REG_DETECTED_HRORD1 (0x220047), scope: pfe, category: functional, severity: major, module: MQSS(0), type: BCMF_ICM_RORD_PROTECT: Detected: HRORD1 memory 
fpc2 Performing action get-state for error /fpc/2/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_BCMF_ICM_FI_RORD_PROTECT_FSET_REG_DETECTED_HRORD1 (0x220047) in module: MQSS(0) with scope: pfe category: functional level: major 
fpc2 Performing action cmalarm for error /fpc/2/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_BCMF_ICM_FI_RORD_PROTECT_FSET_REG_DETECTED_HRORD1 (0x220047) in module: MQSS(0) with scope: pfe category: functional level: major 
fpc2 Performing action disable-pfe for error /fpc/2/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_BCMF_ICM_FI_RORD_PROTECT_FSET_REG_DETECTED_HRORD1 (0x220047) in module: MQSS(0) with scope: pfe category: functional level: major 
alarmd[28879]: Alarm set: FPC id=150996328, color=RED, class=CHASSIS, reason=FPC 2 Major Errors
craftd[28003]: Major alarm set, FPC 2 Major Errors

Symptoms:

• Error message appears in system logs
• Potential impact on traffic or forwarding on the impacted FPC
• System stability may be affected

Data Collection Steps:

Before performing any recovery steps, collect the following outputs for further analysis:

1. Check system messages:

 Router>show log messages

2. Review chassis-level events:

 Router>show log chassisd

3. Enter the shell on the specific FPC:  

 Router>start shell pfe network <fpc-slot-number>

4. From within the PFE shell, collect:

 SMPC0(Router vty)#show nvram

 SMPC0(Router vty)#show syslog messages

 SMPC0(Router vty)#show cmerror module

* Replace `<fpc-slot-number>` with the actual slot number of the affected FPC.

Resolution:

After collecting the above information, proceed with restarting the affected FPC during a maintenance window (MW) to recover from the fault:

Restart the FPC

 Router>request chassis fpc slot <fpc-slot-number> restart

Ensure the restart is done during a scheduled MW to avoid service disruption.

• If the alarm persists, then perform a physical reseat of the line card.
• If the alarm is still noticed, then replace with the spare FPC. 

Next Steps:

If the issue recurs after the FPC restart, consider reaching out to your technical support team with the collected outputs for deeper analysis and possible RMA evaluation.