This article explains the meaning of the "XMCHIP_CMERROR_WO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70389)" alarm that is seen on MX Series routers and indicates if any actions need to be taken.

The following log messages are seen on the Flexible PIC Concentrator (FPC):

Jan 18 05:36:27 XXXX fpc9 CMError: /fpc/9/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70389), scope: pfe, category: functional, severity: major, module: XMCHIP(0), type: WO_PROTECT: Detected: Parity error for Output buffer data 

Jan 18 05:36:27 XXXX fpc9 Performing action offline for error /fpc/9/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70389) in module: XMCHIP(0) with scope: pfe category: functional level: major

Jan 18 05:36:27 XXXX chassisd[26726]: CHASSISD_FPC_ASIC_ERROR: <FPC 9> ASIC Error detected errorno 0x00070389 Offline action performed  

Jan 18 05:36:27 XXXX chassisd[26726]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 9 offline: Offlined due to major errors

Jan 18 05:36:28 XXXX fpc9 Cmerror Op Set: XMCHIP(0): XMCHIP(0): WO0: Protect: Parity error for Output buffer data (URI: /fpc/9/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA) 

Jan 18 05:36:30 XXXX chassisd[26726]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 7, jnxFruL1Index 10, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC4E 3D 32XGE @ 9/*/*, jnxFruType 3, jnxFruSlot 9, jnxFruOfflineReason 18, jnxFruLastPowerOff -19526207, jnxFruLastPowerOn 5986)

Jan 18 05:36:30 XXXX chassisd[26726]: CHASSISD_SNMP_TRAP10: SNMP trap generated: Fru Offline (jnxFruContentsIndex 7, jnxFruL1Index 10, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPC4E 3D 32XGE @ 9/*/*, jnxFruType 3, jnxFruSlot 9, jnxFruOfflineReason 18, jnxFruLastPowerOff -19526207, jnxFruLastPowerOn 5986)

Parity errors occur when there is a mismatch in the expected parity bit (used for error detection) and the actual data read from memory or transmitted. These errors typically indicate hardware issues or transient conditions like power fluctuations or interference.

Some parity errors can be corrected automatically (ECC). The error logs above indicate that the ASIC had a transient hardware failure. 

Recommended Action:

• No RMA is required.
• Restart the MPC in MW and monitor the errors.

Contact your technical support representative if the issue is seen after restarting the FPC.

2025-01-18 : Article Created

2025-01-27: Article edited to add more clarity and made public