Description

This article explains why a parity error with the error message "MQSS-CMERROR-WO-CIF-PAR-0-PROTECT-FSET-REG-DETECTED-COREIF-FIFO-DATA-0-4" is re-classified as a Minor error instead of a Major error.

Symptoms

If an odd number of bits (including the parity bit) are transmitted incorrectly, the parity bit will be incorrect, thus indicating that a parity error occurred in the transmission.

The parity bit is suitable only for detecting errors; it cannot correct any errors, because there is no way to determine which particular bit is corrupted.

The data must be discarded entirely, and re-transmitted from scratch.

root@LAB-RE0> show chassis alarms no-forwarding
1 alarms currently active
Alarm time               Class  Description
2023-05-15 20:50:20 UTC  Major  FPC 0 Major Errors

We may see the following errors with the PFE disable action since the error is classified as Major.

May 15 20:49:40 LAB-RE0 fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/MQSS(2)/2/MQSS_CMERROR_WO_CIF_PAR_0_PROTECT_FSET_REG_DETECTED_COREIF_FIFO_DATA_0_4 (0x220a77) in module: MQSS(2) with scope: pfe category: functional level: major, oc_category: default 

May 15 20:50:20 LAB-RE0 fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/MQSS(2)/2/MQSS_CMERROR_WO_CIF_PAR_0_PROTECT_FSET_REG_DETECTED_COREIF_FIFO_DATA_0_4 (0x220a77) in module: MQSS(2) with scope: pfe category: functional level: major, oc_category: default 

May 15 20:50:20 LAB-RE0 fpc0 Performing action disable-pfe for error /fpc/0/pfe/0/cm/0/MQSS(2)/2/MQSS_CMERROR_WO_CIF_PAR_0_PROTECT_FSET_REG_DETECTED_COREIF_FIFO_DATA_0_4 (0x220a77) in module: MQSS(2) with scope: pfe category: functional level: major, oc_category: default 

May 15 20:50:21 LAB-RE0 fpc0 Cmerror Op Set: MQSS(2): MQSS(2): WO: COREIF Parity Protect 0: Parity error detected for COREIF S&F data FIFO 0_4 - data32_log_err 0x80000, data32_log_address 0x345 (URI: /fpc/0/pfe/0/cm/0/MQSS(2)/2/MQSS_CMERROR_WO_CIF_PAR_0_PROTECT_FSET_REG_D"

Solution

This error does not cause a wedge condition; therefore the error severity has been re-classified from Major to Minor.

Meanwhile, you can manually classify this error as a minor error by using the following CLI command:

set chassis fpc <slot> error scope <scope> <category> <severity> action <action>

This statement was introduced from Junos OS Release 18.2R1. For more information about reclassification of errors, see Chassis-Level User Guide > error-id.

Modification History

2023-06-16: Initial version