Description

This article discusses a scenario when FPC Minor Error: "XQCHIP(46): XQ-chip[]: CPQ Correctable ECC error" is reported on MX router and clarifies whether any actions need to be taken.

Symptoms

MX router reports the following FPC Minor Errors alarm:

  • show system alarms
user@device> show chassis alarms
1 alarms currently active
Alarm time Class Description
<date> <time> Minor FPC 5 Minor Errors
  • show chassis errors active detail fpc-slot 5
user@device> show chassis errors active detail fpc-slot 5
Slot 5

--------------------------------------------------
Location : FPC 5
Identifier : /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_XR_CORRECTABLE_ECC_ERR
Error : XQ_CMERROR_XR_CORRECTABLE_ECC_ERR
Scope : pfe
Category : functional
Severity : Minor
Details : XQ_CMERROR_XR_CORRECTABLE_ECC_ERR
Count : 12
Support : No help info provided
  • show log messages
alarmd[19887]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 5 Minor Errors
craftd[19169]: Minor alarm set, FPC 5 Minor Errors
fpc5 Performing action log for error /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_XR_CORRECTABLE_ECC_ERR (0x80320) in module: XQCHIP(46) with scope: pfe category: functional level: minor 
fpc5 Performing action cmalarm for error /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_XR_CORRECTABLE_ECC_ERR (0x80320) in module: XQCHIP(46) with scope: pfe category: functional level: minor 
fpc5 Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ Correctable ECC error (XRIF0_LM1_MEM)
  • The alarm is raised when 32 CPQ Correctable ECC errors have been reported:
%PFE-6: fpc5 XQ-chip[0]: XQ-chip[0]: CPQ Correctable ECC error (XRIF0_LM1_MEM)  
%PFE-6: fpc5 XQ-chip[0] Total correctable errors: 12 (today:12) 
%PFE-6: fpc5 XQ-chip[0]: XQ-chip[0]: CPQ Correctable ECC error (XRIF0_LM1_MEM)  
%PFE-6: fpc5 XQ-chip[0] Total correctable errors: 13 (today:13)
...
%PFE-6: fpc5 XQ-chip[0]: XQ-chip[0]: CPQ Correctable ECC error (XRIF0_LM1_MEM)  
%PFE-6: fpc5 XQ-chip[0] Total correctable errors: 31 (today:31)

Solution

These are the correctable ECC memory errors which are already corrected by the JUNOS software.

As the error log itself explained it was detected and corrected automatically when these error logs were written.

If these were logged just once at a specific time then you can clear the alarm through CLI command clear chassis fpc errors fpc-slot <> all.

If these were logged more often at different times and dates then we suggest FPC reset in a MW to clear the memory from this condition.

If the issue persists after FPC resetting, please open a case with JTAC to investigate further. For additional information, refer to TSB17946 - Queing Chip error handling enhancement for Subscriber Environment [juniper.net].

Modification History

2024-10-30: Major formatting changes.

2023-04-06: Initial Publication.