This article explains the meaning of the "XMCHIP-CMERROR-FO-MEM-PROTECT-FSET-REG-DETECTED-OBUF-DATA (0x70160)" syslog message.

The following logs are seen:

May 29 01:21:58 2025  re0.labrouter fpc1 XMCHIP(1): XMCHIP(1): FO: Packet error - Error Packets 13, Stream 132 
May 29 01:21:58 2025  re0.labrouter fpc2 MQSS(0): FI: Error cell sent to reorder engine - Stream 5, Count 4 
May 29 01:21:58 2025  re0.labrouter fpc1 XMCHIP(0): XMCHIP(0): FI: Error cell sent to reorder engine - Stream 133, Count 9 
May 29 01:21:59 2025  re0.labrouter fpc1 XMCHIP(1): XMCHIP(1): FO: Protect: Log Error 0x4, Log Address 0x7ca, Multiple Errors 0x4 
May 29 01:21:59 2025  re0.labrouter fpc1 CMError: /fpc/1/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70160), scope: pfe, category: functional, severity: major, module: XMCHIP(1), type: FO_PROTECT: Detected: Parity error for Output buffer data 
May 29 01:22:00 2025  re0.labrouter fpc1 Performing action get-state for error /fpc/1/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70160) in module: XMCHIP(1) with scope: pfe category: functional level: major 
May 29 01:22:06 2025  re0.labrouter fpc1 Performing action cmalarm for error /fpc/1/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70160) in module: XMCHIP(1) with scope: pfe category: functional level: major 
May 29 01:22:06 2025  re0.labrouter fpc1 Performing action disable-pfe for error /fpc/1/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA (0x70160) in module: XMCHIP(1) with scope: pfe category: functional level: major 
May 29 01:22:06 2025  re0.labrouter mib2d[27609]: SNMP_TRAP_LINK_DOWN: ifIndex 543, ifAdminStatus up(1), ifOperStatus down(2), ifName et-1/3/1
May 29 01:22:06 2025  re0.labrouter mib2d[27609]: SNMP_TRAP_LINK_DOWN: ifIndex 544, ifAdminStatus up(1), ifOperStatus down(2), ifName et-1/3/2
May 29 01:22:07 2025  re0.labrouter fpc1 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-1/3/0 181 
May 29 01:22:07 2025  re0.labrouter fpc1 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-1/3/1 182 
May 29 01:22:07 2025  re0.labrouter kernel: if_msg_ifd_cmd_tlv_decode ifd et-1/3/0 #181 down with ASIC Error
May 29 01:22:07 2025  re0.labrouter kernel: if_msg_ifd_cmd_tlv_decode ifd et-1/3/1 #182 down with ASIC Error
May 29 01:22:07 2025  re0.labrouter kernel: if_msg_ifd_cmd_tlv_decode ifd et-1/3/2 #183 down with ASIC Error
May 29 01:22:08 2025  re0.labrouter alarmd[27605]: Alarm set: FPC id=150995304, color=RED, class=CHASSIS, reason=FPC 1 Major Errors
May 29 01:22:08 2025  re0.labrouter craftd[23227]:  Major alarm set, FPC 1 Major Errors
May 29 01:22:08 2025  re0.labrouter fpc1 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-1/3/2 183 
May 29 01:22:08 2025  re0.labrouter fpc1 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-1/3/1 182 
May 29 01:22:08 2025  re0.labrouter fpc1 Cmerror Op Set: XMCHIP(1): XMCHIP(1): FO: Protect: Parity error for output buffer data  (URI: /fpc/1/pfe/0/cm/0/XMCHIP(1)/1/XMCHIP_CMERROR_FO_MEM_PROTECT_FSET_REG_DETECTED_OBUF_DATA) 

This cmerror is reported due to a parity protected memory error.  This error will be reported as a Major followed by the pfe-disable action. An FPC reboot will be required to recover the pfe-disable state.

If the pfe-disable action has not been initiated, then the errors can be cleared by using the command "clear chassis fpc errors fpc-slot <x> all."

If the PFE has been disabled or using the clear command did not help, you can use the following steps:

• Reset the FPC by using the CLI reset command.

• If you see the error logs even after reboot of the FPC, then try re-seating the FPC.

• If the logs are seen even after re-seat, then consider replacing the FPC.

2024-01-09: Minor non-technical edit.
2023-07-06: Initial version