This MX has a Minor alarm for fpc and it looks xmchip errors log consistently showing up in the logs. 

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

Jan 12 05:19:11 2006 re0.router  fpc0 XMCHIP(0): XMCHIP(0): WI1: Misc SRAM Protect: Multiple Errors 0x80 

Jan 12 05:19:11 2006 re0.router chassisd[21691]: CHASSISD_FPC_ASIC_ERROR: <FPC 0> ASIC Error detected errorno 0x00070359 (null)

Jan 12 05:19:11 2006 re0.router alarmd[42441]: Alarm set: FPC id=167772264, color=YELLOW, class=CHASSIS, reason=FPC 0 Minor Errors

Jan 12 05:19:11 2006 re0.router craftd[21695]: Minor alarm set, FPC 0 Minor Errors

Jan 12 05:19:11 2006 re0.router fpc0 CMError: /fpc/0/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM (0x70359), scope: pfe, category: functional, severity: minor, module: XMCHIP(0), type: WI_PROTECT: Detected: Parity error for ibuf ce

Jan 12 05:19:12 2006 re0.router fpc0 Performing action log for error /fpc/0/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM (0x70359) in module: XMCHIP(0) with scope: pfe category: functional level: minor 

Jan 12 05:19:13 2006 re0.router fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM (0x70359) in module: XMCHIP(0) with scope: pfe category: functional level: minor 

Jan 12 05:19:13 2006 re0.router fpc0 Cmerror Op Set: XMCHIP(0): XMCHIP(0): WI1: Misc SRAM Protect: Parity error for dequeue buffer SRAM (URI: /fpc/0/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM) 

The message "Misc SRAM Protect: Parity error for dequeue buffer SRAM" reports a temporary hardware memory error.
This is due to a transient SRAM hardware error on the XMCHIP. If there was a service impact, then other events would be reported.

Please 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 network pfe <fpc#>
  show nvram
  show syslog messages
  show cmerror module brief    <<< pick up X for xmchip0
  show cmerror module X error 0x070359
  exit

------------------------

For example:

RMPC4(waio-re0 vty)# show cmerror module  23 error 0x070359

Error-id              : 0x70359

Error Name                : XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM
Identifier                : /fpc/4/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM
Description               : WI_PROTECT: Detected: Parity error for ibuf central deq buffer
State                     : enabled
Scope                     : pfe
Category                  : functional
PFE                       : 0
Configured Level          : Minor
Default Level             : Minor
Count                     : 0
Threshold                 : 1
Error Limit               : 0
Occur Count               : 0
Clear Count               : 0
OverItemThres Occur Count : 0
OverItemThres Clear Count : 0
Last-occurred(ms ago) : 0

Logs:
----------------------------------------------------------
Index  Time                 Sub-Err   State    Description
----------------------------------------------------------

------------------------

Analyze the show command output.

In the 'show log messages', review the events that occurred at or just before the appearance of the "XMCHIP_CMERROR_WI_MISC_SRAM_PAR_PROTECT_FSET_REG_DETECTED_DEQ_IBUF_SRAM" message. 
Frequently these events help identify the cause.

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

#According to the technical documentation on  clear chassis fpc errors , this command is supported on Junos starting from 18.2R1.

If the error occurs multiple times, please restart the FPC during a maintenance window with a spare part on-site in case ithe fpc cannot boot up.

user@router> request chassis fpc slot <slot number> restart

Wait for a few minutes.

Further Assistance:

If the issue remains unresolved, please contact Juniper Technical Support for further investigation.

2026-01-23 : Article Created

2026-02-09 : Article Modified.

2026-02-09 : Published