This article explains log "PECHIP_CMERROR_DT_PARITY_PROTECT_FSET_REG_DETECTED_OQB_FBM_SRAM_PARITY 0x210593" on FPC and steps to mitigate the same.

A fatel error is generated when the SRAM parity error is detected in OQB (output queue block) and it results in disabling the affected pfe in order to stop the impact from spreading the other pfe's.

Jan 29 22:09:56.796 lab_router fpc6 Error: /fpc/6/pfe/0/cm/0/PE_Chip/3/PECHIP_CMERROR_DT_PARITY_PROTECT_FSET_REG_DETECTED_OQB_FBM_SRAM_PARITY (0x210593), scope: pfe, category: functional, severity: fatal, module: PE Chip, type: Description for PECHIP_CMERROR_DT_PARITY_PROTECT_FSE

Jan 29 22:09:56.809 lab_router fpc6 Performing action get-state for error /fpc/6/pfe/0/cm/0/PE_Chip/3/PECHIP_CMERROR_DT_PARITY_PROTECT_FSET_REG_DETECTED_OQB_FBM_SRAM_PARITY (0x210593) in module: PE Chip with scope: pfe category: functional level: fatal 

Jan 29 22:09:56.870 lab_router inetd[16600]: Number of tftp connections at max limit (1)

Jan 29 22:09:56.942 lab_router fpc6 Performing action disable-pfe for error /fpc/6/pfe/0/cm/0/PE_Chip/3/PECHIP_CMERROR_DT_PARITY_PROTECT_FSET_REG_DETECTED_OQB_FBM_SRAM_PARITY (0x210593) in module: PE Chip with scope: pfe category: functional level: fatal 

All the interface's on the affected Pfe go down and then the pfe is disabled.

Jan 29 22:09:56.942 lab_router fpc6 ISSUING ifd-down for et-6/0/11 (356) on pfe-3 

Jan 29 22:09:57.041 lab_router fpc6 ISSUING ifd-down for et-6/0/13 (358) on pfe-3 

Jan 29 22:09:57.234 lab_router fpc6 ISSUING ifd-down for et-6/0/15 (360) on pfe-3 

Jan 29 22:09:57.438 lab_router fpc6 ISSUING ifd-down for et-6/0/17 (362) on pfe-3 

Jan 29 22:09:57.536 lab_router fpc6 ISSUING ifd-down for et-6/0/19 (364) on pfe-3 

Jan 29 22:09:57.543 lab_router fpc6 pechip_set_pfe_disabled:976: PECHIP[3]: PFE Marked Disabled !!! 

Jan 29 22:09:57.544 lab_router fpc6 JPRDS_FDB:ERR:jprds_fdb_set_pfe_disabled(),8275: pfe 3 marked disabled  

Jan 29 22:09:57.544 lab_router fpc6 Cmerror Op Set: PE Chip::FATAL ERROR!! from PE3[3]: DT:par_intr: 0x00000001: OQB FBM SRAM Parity Error  

The parity error is self corrected mostly however the pfe remains down as it required a FPC reboot to bring the pfe back up.

Jan 29 22:11:18.209 blab_router fpc6 Performing action log for error /fpc/6/pfe/0/cm/0/PE_Chip/3/PECHIP_CMERROR_DT_PARITY_PROTECT_FSET_REG_DETECTED_OQB_FBM_SRAM_PARITY (0x210593) in module: PE Chip with scope: pfe category: functional level: fatal 

Jan 29 22:11:18.236 lab_router fpc6 Cmerror Op Clear: PE Chip::FATAL ERROR!! from PE3[3]: DT: Clear OQB FBM SRAM Parity Error 

Schedule a FPC reboot to bring up the disabled FPC.

If the issue does not resolve after a restart, that is, if the errors persist after FPC restart, collect the following logs to provide to Support for further investigation.

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