This article explains why a parity error with "MQSS Error code: 0x2203b7” is seen on MX Series routers and what should be done to resolve the error.
When a parity error is detected on a DRD (Dispatch and Reorder) block, the following chassis alarm is generated:
> show chassis alarms no-forwarding
1 alarms currently active
Alarm time Class Description
<Date/Timestamp> Minor FPC <slot no.> Major Errors
You may observe log messages similar to the following as well:
Nov 4 08:02:20 Device : %PFE-3: fpc10 MQSS(0): DRD: RORD0 Protect: Multiple Errors 0x10 Nov 4 08:02:20 Device : %PFE-5: fpc10 Error: /fpc/10/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_NPTR_B (0x2203b7), scope: pfe, category: functional, severity: major, module: MQSS(0), type: DRD_RORD: Detected: next pointer memory port B Nov 4 08:02:20 Device : %PFE-5: fpc10 Performing action get-state for error /fpc/10/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_NPTR_B (0x2203b7) in module: MQSS(0) with scope: pfe category: functional level: major Nov 4 08:02:20 Device tftpd[23447]: %FTP-6: Filename: '/var/tmp/pfe_debug_commands' Nov 4 08:02:20 Device tftpd[23447]: %FTP-6: Mode: 'octet' Nov 4 08:02:20 Device tftpd[23447]: %FTP-6: 128.0.0.26: read request for /var/tmp/pfe_debug_commands: success Nov 4 08:02:20 Device inetd[17459]: %DAEMON-4: Number of tftp connections at max limit (1) Nov 4 08:02:20 Device tftpd[23449]: %FTP-6: Filename: '/var/tmp/pfe_debug_info_SMPC10' Nov 4 08:02:20 Device tftpd[23449]: %FTP-6: Mode: 'octet' Nov 4 08:02:20 Device tftpd[23449]: %FTP-6: 128.0.0.26: write request for /var/tmp/pfe_debug_info_SMPC10: success Nov 4 08:02:32 Device : %PFE-5: fpc10 Performing action cmalarm for error /fpc/10/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_NPTR_B (0x2203b7) in module: MQSS(0) with scope: pfe category: functional level: major Nov 4 08:02:32 Device eventd[17108]: %SYSLOG-6-EVENTD_ESCRIPT_EXECUTION: Trying to execute the script 'MPC_event_script_18_2.py' from '/var/db/scripts/event/' Nov 4 08:02:32 Device : %PFE-5: fpc10 Performing action disable-pfe for error /fpc/10/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_NPTR_B (0x2203b7) in module: MQSS(0) with scope: pfe category: functional level: major Nov 4 08:02:32 Device : %PFE-5: fpc10 PFE 0: 'PFE Disable' action performed. Bringing down ifd et-10/0/2 456 Nov 4 08:02:32 Device : %PFE-5: fpc10 PFE 0: 'PFE Disable' action performed. Bringing down ifd et-10/0/5 457 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Timeout:0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Thread Stopped, interval = 0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Timeout:0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Thread Stopped, interval = 0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Timeout:0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Thread Stopped, interval = 0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Timeout:0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE[0] Liveness Thread Stopped, interval = 0 Nov 4 08:02:32 Device : %PFE-6: fpc10 PFE:pfe_set_fe_down_flag First active PFE ID changed from 0 to 1 Nov 4 08:02:32 Device : %PFE-3: fpc10 Cmerror Op Set: MQSS(0): MQSS(0): DRD: RORD0 Protect: Parity error detected for next pointer memory port B - data32_log_err 0x10, data32_log_address 0x147
This Major error is caused by the Parity error detected for next pointer memory port B on a DRD (Dispatch and Reorder) block of MQSS chip, which is seen on MX routers installed with MPCs that use EACHIP.
To resolve the above error, perform the following steps:
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
Before Junos OS Release 20.3, this error was classified as major and permanent packet forwarding on the Packet Forwarding Engine (PFE) may be impacted as it disables the PFE in which the error is seen. Restart of the FPC will enable the PFE again and will clear the error.
Prior to Junos OS Release 20.3, the level of this error can be manually changed to minor by using the following CLI configuration:
set chassis fpc 10 error "/fpc/10/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_SRAM_PAR_PROTECT_FSET_REG_DETECTED_NPTR_B" severity minor
A single occurrence of minor 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. This command is available starting in Junos OS 16.1R4-S2, 16.1R5, 16.2R2, 17.1R2, and 17.2R1 as a hidden command. It is unhidden in Junos OS 18.2R1 and later.
user@mx> clear chassis fpc errors fpc-slot fpc-slot (all | error-id error-id)
Note: It is suggested to use all instead of a particular error-id to work around the complicated error-id format, which is represented as a Uniform Resource Identifier (URI).
If the error occurs multiple times, take the FPC offline, and bring it online again or restart the FPC during a maintenance window.
user@mx> request chassis fpc slot <slot number> offline Wait for a few minutes. user@mx> request chassis fpc slot <slot number> online OR Execute: user@mx> request chassis fpc slot <slot number> restart
Note: If the issue is seen repeatedly even after restarting the FPC, open a Support case for further investigation and assistance.