Description

Syslog error message "XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR(0x70033)"

Symptoms

Syslog error message XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR(0x70033) reports a CPQ Sram parity error. When this error occurs below logs maybe be observed:

From log messages:
Sep 6 20:41:05 mx960 : %PFE-3: fpc11 XMCHIP(0): : XMCHIP(0): DDRIF: Checksum error for WO1 - Channel 10, Address 0xc804c, Checksum Errors 1, Checksum Poison Count 0
Sep 6 20:41:05 mx960 : %PFE-3: fpc11 XMCHIP(0): XMCHIP(0): DDRIF: 2x32 Instance 2, Part 0 - Write rate: 20424096, Read rate: 20424147, Total rate: 40848243
Sep 6 20:41:05 mx960 : %PFE-3: fpc11 XMCHIP(0): XMCHIP(0): DDRIF: Packet memory - Write rate: 365649291, Read rate: 365649396, Total rate: 731298687
Sep 6 20:41:05 mx960 chassisd[23316]: %DAEMON-3-CHASSISD_FPC_ASIC_ERROR: <FPC 11> ASIC Error detected errorno 0x00070033 (null)
Sep 6 20:41:05 mx960 : %PFE-3: fpc11 XMCHIP(0): XMCHIP(0): DDRIF: Linkram memory - Write rate: 31735, Read rate: 31569, Total rate: 63304
Sep 6 20:41:05 mx960 : %PFE-3: fpc11 XMCHIP(0): XMCHIP(0): WO1: Packet error - Error Packets 1, Stream 30
Sep 6 20:41:06 mx960 : %PFE-5: fpc11 Error: /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033), scope: pfe, category: functional, severity: major, module: XMCHIP(0), type: CPQ: SRAM parity error
Sep 6 20:41:06 mx960 : %PFE-5: fpc11 Performing action log for error /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) in module: XMCHIP(0) with scope: pfe category: functional level: major
Sep 6 20:41:07 mx960 : %PFE-5: fpc11 Performing action get-state for error /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) in module: XMCHIP(0) with scope: pfe category: functional level: major
Sep 6 20:41:08 mx960 : %PFE-5: fpc11 Performing action cmalarm for error /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) in module: XMCHIP(0) with scope: pfe category: functional level: major
Sep 6 20:41:09 mx960 alarmd[23648]: %DAEMON-4: Alarm set: FPC id=150997864, color=RED, class=CHASSIS, reason=FPC 11 Major Errors
Sep 6 20:41:09 mx960 craftd[23321]: %DAEMON-4: Major alarm set, FPC 11 Major Errors
Sep 6 20:41:09 mx960 : %PFE-3: fpc11 Cmerror Op Set: XMCHIP(0): XMCHIP(0): CPQ0: SRAM parity error - data32_err_log 0x10, data32_err_loc 0xa1f (URI: /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR)

 

From FPC shell:
[Sep 5 20:18:22.264 LOG: Info] services_send_cfg_to_pic: LS[11], GS[11], PS[0]
[Sep 7 02:41:05.520 LOG: Err] XMCHIP(0): : XMCHIP(0): DDRIF: Checksum error for WO1 - Channel 10, Address 0xc804c, Checksum Errors 1, Checksum Poison Count 0
[Sep 7 02:41:05.520 LOG: Err] XMCHIP(0): XMCHIP(0): DDRIF: 2x32 Instance 2, Part 0 - Write rate: 20424096, Read rate: 20424147, Total rate: 40848243
[Sep 7 02:41:05.520 LOG: Err] XMCHIP(0): XMCHIP(0): DDRIF: Packet memory - Write rate: 365649291, Read rate: 365649396, Total rate: 731298687
[Sep 7 02:41:05.520 LOG: Err] XMCHIP(0): XMCHIP(0): DDRIF: Linkram memory - Write rate: 31735, Read rate: 31569, Total rate: 63304
[Sep 7 02:41:05.520 LOG: Err] XMCHIP(0): XMCHIP(0): WO1: Packet error - Error Packets 1, Stream 30
[Sep 7 02:41:05.529 LOG: Debug] Cmerror: Draining ASIC error message queue
[Sep 7 02:41:05.529 LOG: Debug] cmerror_process_queue: module = XMCHIP(0)
[Sep 7 02:41:05.529 LOG: Debug] Cmerror: processing the task op_type 1 for scope 1 and category 0 level 1 level_count 0 occur_count 0 clear_count 0 level_threshold 1 level_action 0x7 item errid 458803 item_threshold 1 item_count 0 item_sub_err_state 0 sub_item errid 0 sub_i[Sep 7 02:41:05.529 LOG: Debug] Cmerror: Level 1 count increment 1 occur_count 1 clear_count 0
[Sep 7 02:41:05.530 LOG: Notice] Error: /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033), scope: pfe, category: functional, severity: major, module: XMCHIP(0), type: CPQ: SRAM parity error
[Sep 7 02:41:05.530 LOG: Debug] Cmerror: Level 1 count 1 (occur_count 1 clear_count 0)crossed threshold 1 action 0x7
[Sep 7 02:41:05.530 LOG: Debug] alarm count for level 1 is incremented and set to 1
[Sep 7 02:41:05.530 LOG: Notice] Performing action log for error /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) in module: XMCHIP(0) with scope: pfe category: functional level: major
[Sep 7 02:41:05.530 LOG: Debug] cmerror_take_action_helper: performing action 1 for scope 1 category 0 level 1 err_id /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR(0x70033) module id 5
[Sep 7 02:41:05.530 LOG: Notice] Performing action get-state for error /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) in module: XMCHIP(0) with scope: pfe category: functional level: major
[Sep 7 02:41:05.530 LOG: Debug] cmerror_take_action_helper: performing action 2 for scope 1 category 0 level 1 err_id /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR(0x70033) module id 5
[Sep 7 02:41:08.935 LOG: Notice] Performing action cmalarm for error /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) in module: XMCHIP(0) with scope: pfe category: functional level: major
[Sep 7 02:41:08.935 LOG: Debug] cmerror_take_action_helper: performing action 4 for scope 1 category 0 level 1 err_id /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR(0x70033) module id 5
[Sep 7 02:41:08.935 LOG: Err] Cmerror Op Set: XMCHIP(0): XMCHIP(0): CPQ0: SRAM parity error - data32_err_log 0x10, data32_err_loc 0xa1f (URI: /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR)


too long# sh cmerror module 5 error 0x070033
Error-id      : 0x70033
Error Name     : XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR
Identifier     : /fpc/11/pfe/0/cm/0/XMCHIP(0)/0/XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR
Description     : CPQ: SRAM parity error
State        : enabled
Scope        : pfe
Category      : functional
PFE         : 0
Configured Level  : Major
Default Level    : Major
Count        : 1
Threshold      : 1
Error Limit     : 0
Occur Count     : 1
Clear Count     : 0
Last-occurred(ms ago) : 1967852

Logs:
----------------------------------------------------------
Index Time        Sub-Err State Description
----------------------------------------------------------
0  09/07/24 02:41:08 0    Set  unknown

Solution

Syslog error XMCHIP_CMERROR_CPQ_INT_REG_SRAM_PAR_ERROR (0x70033) reports a Sram parity error in CPQ block of XMCHIP. This is a transient hardware error. 

 

  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.
    show log messages
    show log chassisd
    start shell network pfe <fpc#>
    show nvram
    show syslog messages
    show cmerror modules brief     ---> check for XMCHIP id [In current example error is in "XMCHIP(0)"] 
    exit

  2. Analyze the show command output. In the 'show log messages', review the events that occurred at or just before the appearance of the "CPQ Sram parity error" message. Frequently these events help identify the cause. No RMA is required with the single occurrence

      3. If the error is seen repeatedly, an FPC restart  during a maintenance window should clear this error

       4. Contact your technical support representative if this issue transcends FPC reset.

 

Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.

Modification History

2024-09-21 : Article Created