The article discusses about the FPC major errors alarm caused by the XQSS_CMERROR_CPQW_SRAM_PROTECT_LOG_ERR (0x2300e2) error

2 alarms currently active

Alarm time    Class Description

2023-12-07 09:27:54 UTC Minor FPC 10 Minor Errors

2023-12-07 09:27:36 UTC Major FPC 10 Major Errors

Dec 7 09:27:23 MX960_RE0 fpc10 Error: /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CPQW_SRAM_PROTECT_LOG_ERR (0x2300e2), scope: pfe, category: functional, severity: major, module: XQSS(0), type: XQSS CPQW SRAM PROTECT LOG

Dec 7 09:27:23 MX960_RE0 fpc10 Performing action log for error /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CPQW_SRAM_PROTECT_LOG_ERR (0x2300e2) in module: XQSS(0) with scope: pfe category: functional level: major

Dec 7 09:27:23 MX960_RE0 fpc10 Performing action get-state for error /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CPQW_SRAM_PROTECT_LOG_ERR (0x2300e2) in module: XQSS(0) with scope: pfe category: functional level: major

Dec 7 09:27:35 MX960_RE0 fpc10 Performing action cmalarm for error /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CPQW_SRAM_PROTECT_LOG_ERR (0x2300e2) in module: XQSS(0) with scope: pfe category: functional level: major

Dec 7 09:27:35 MX960_RE0 fpc10 Cmerror Op Set: XQSS(0): XQ-SS[0]: CPQW protect mem error (status=0x8) err_address=0x2d75

Dec 7 09:27:36 MX960_RE0 alarmd[19874]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 10 Major Errors

Dec 7 09:27:36 MX960_RE0 craftd[19159]: Major alarm set, FPC 10 Major Errors

Sometimes followed by a minor alarm:

Dec 7 09:27:54 MX960_RE0 fpc10 Error: /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CORRECTABLE_MEM_ERR (0x230190), scope: pfe, category: functional, severity: minor, module: XQSS(0), type: XQSS correctable memory error

Dec 7 09:27:54 MX960_RE0 fpc10 Performing action log for error /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CORRECTABLE_MEM_ERR (0x230190) in module: XQSS(0) with scope: pfe category: functional level: minor

Dec 7 09:27:54 MX960_RE0 fpc10 Performing action cmalarm for error /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CORRECTABLE_MEM_ERR (0x230190) in module: XQSS(0) with scope: pfe category: functional level: minor

Dec 7 09:27:54 MX960_RE0 fpc10 Cmerror Op Set: XQSS(0): XQ-SS[0]: CPQW ocm-sram mem parity error

Dec 7 09:27:54 MX960_RE0 alarmd[19874]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 10 Minor Errors

Dec 7 09:27:54 MX960_RE0 craftd[19159]: Minor alarm set, FPC 10 Minor Errors

Dec 7 09:27:55 MX960_RE0 fpc10 Error: /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CORRECTABLE_MEM_ERR (0x230190), scope: pfe, category: functional, severity: minor, module: XQSS(0), type: XQSS correctable memory error

Dec 7 09:27:55 MX960_RE0 fpc10 Performing action log for error /fpc/10/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_CORRECTABLE_MEM_ERR (0x230190) in module: XQSS(0) with scope: pfe category: functional level: minor

Dec 7 09:27:55 MX960_RE0 fpc10 Cmerror Op Set: XQSS(0): XQ-SS[0]: CPQW ocm-sram mem parity error

Module Name    Active Errors PFE  Callback ModuleData

Specific Function     

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

19  XQSS(0)   13    No  0x00000000 0xdeaff348

A single occurrence of this message indicates a one-time condition. This is a transient hardware error in CPQW block of XQ-SS chip, usually a one-time occurrence.

Perform these steps to determine the cause and resolve the problem:

• Collect the following show command output. Capture the output to a file (in case you have to open a technical support case). To do this, configure the SSH client/terminal emulator to log your session.

show chassis alarms

show log messages

show log chassisd

show chassis errors active detail fpc-slot <fpc#>

show chassis fpc

show chassis fpc detail

start shell pfe network <fpc#>

show nvram 

show syslog messages 

show cmerror module brief

• Analyze the show command output. In the 'show log messages', review the events that occurred at or just before the appearance of the "XQSS_CMERROR_CPQW_SRAM_PROTECT_LOG_ERR" message. Frequently these events help identify the cause.
• No RMA required.
• FPC restart during a maintenance window should clear this error and alarm.
• Contact your technical support representative if the issue is seen after a FPC restart.