This article explains about the Syslog message: fpc* MQSS(*): DRD: RORD* Protect: Multiple Errors

When a parity error is detected on a DRD (Dispatch and Reorder) block, a minor chassis alarm is generated, and you may observe messages log similar to the following as well:

Feb 15 11:05:40 MX_TEST-RE0 : %PFE-3: fpc5 MQSS(1): DRD: RORD1 Protect: Multiple Errors 0x0

Feb 15 11:05:40 MX_TEST-RE0 : %PFE-5: fpc5 Error: /fpc/5/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQMEM1_B (0x2203bd), scope: pfe, category: functional, severity: major, module: MQSS(1), type: DRD_RORD: Detected: SQMEM1 memory port B

Feb 15 11:05:40 MX_TEST-RE0 : %PFE-5: fpc5 Performing action get-state for error /fpc/5/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQMEM1_B (0x2203bd) in module: MQSS(1) with scope: pfe category: functional level: major

Feb 15 11:05:52 MX_TEST-RE0 : %PFE-5: fpc5 Performing action cmalarm for error /fpc/5/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQMEM1_B (0x2203bd) in module: MQSS(1) with scope: pfe category: functional level: major

Feb 15 11:05:52 MX_TEST-RE0 : %PFE-5: fpc5 Performing action disable-pfe for error /fpc/5/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQMEM1_B (0x2203bd) in module: MQSS(1) with scope: pfe category: functional level: major

Feb 15 11:05:52 MX_TEST-RE0 : %PFE-5: fpc5 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-5/1/2 181

Feb 15 11:05:52 MX_TEST-RE0 : %PFE-5: fpc5 PFE 1: 'PFE Disable' action performed. Bringing down ifd et-5/1/5 182

Feb 15 11:05:52 MX_TEST-RE0 craftd[22476]: %DAEMON-4: Major alarm set, FPC 5 Major Errors

Feb 15 11:05:52 MX_TEST-RE0 alarmd[26209]: %DAEMON-4: Alarm set: FPC id=150996328, color=RED, class=CHASSIS, reason=FPC 5 Major Errors

Feb 15 11:05:52 MX_TEST-RE0 : %PFE-3: fpc5 Cmerror Op Set: MQSS(1): MQSS(1): DRD: RORD1 Protect: Parity error detected for SQMEM1 memory port B - data32_log_err 0x400, data32_log_address 0x98e (URI: /fpc/5/pfe/0/cm/0/MQSS(1)/1/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTE

Feb 15 11:05:52 MX_TEST-RE0 kernel: %KERN-3: if_msg_ifd_cmd_tlv_decode ifd et-5/1/2 #181 down with ASIC Error

Feb 15 11:05:52 MX_TEST-RE0 kernel: %KERN-3: if_msg_ifd_cmd_tlv_decode ifd et-5/1/5 #182 down with ASIC Error

Similar logs may observe:

Feb 9 12:13:43.183 2025 Lab_MX2020 fpc15 Cmerror Op Set: MQSS(3): MQSS(3): DRD: RORD0 Protect: Parity error detected for SQ pointer memory - data32_log_err 0x2, data32_log_address 0x950 (URI: /fpc/15/pfe/0/cm/0/MQSS(3)/3/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQ
Feb 9 12:13:44.183 2025 Lab_MX2020 fpc15 MQSS(3): DRD: RORD0 Protect: Multiple Errors 0x2 
Feb 9 12:13:44.191 2025 Lab_MX2020 fpc15 Cmerror Op Set: MQSS(3): MQSS(3): DRD: RORD0 Protect: Parity error detected for SQ pointer memory - data32_log_err 0x2, data32_log_address 0x950 (URI: /fpc/15/pfe/0/cm/0/MQSS(3)/3/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQ
Feb 9 12:13:45.180 2025 Lab_MX2020 fpc15 MQSS(3): DRD: RORD0 Protect: Multiple Errors 0x2 
Feb 9 12:13:45.184 2025 Lab_MX2020 fpc15 Cmerror Op Set: MQSS(3): MQSS(3): DRD: RORD0 Protect: Parity error detected for SQ pointer memory - data32_log_err 0x2, data32_log_address 0x950 (URI: /fpc/15/pfe/0/cm/0/MQSS(3)/3/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_SQ

This major error is caused by an SQ pointer memory parity error detected on the MQSS chip, which is seen on MX routers installed with MPCs that use EACHIP. To resolve the above error, perform the following steps:

1. Collect the following show command outputs to investigate further:

> show log messages
> show log chassisd
> start shell network pfe <fpc#>
> show nvram
> show syslog messages

Analyze the show command outputs matching the time when the alarm was triggered. Observe what parity error was reported and on which block it was detected on the EACHIP.

A single occurrence of this memory parity error in the log indicates a transient hardware issue. If it is a single occurrence, it can be cleared manually by using the following command in operational mode:

TEST@router> clear chassis fpc errors fpc-slot fpc-slot all

2. If the error occurs multiple times, take the FPC offline, and bring it online again or restart the FPC during a maintenance window or if PFE got disabled, need to restart the FPC.

TEST@router> request chassis fpc slot <slot number> offline
Wait for a few minutes.
TEST@router> request chassis fpc slot <slot number> online