This article will explain the meaning of the parity error message: %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo.

Model: qfx5200-32c-32q

Junos: 21.4R3-S5.17

The switch has detected continuous parity errors, indicated by the message: %PFE-3: fpc0 Parity.

Sep 22 03:00:00 Switch : %PFE-3: fpc0 Parity error..

Sep 22 03:00:00 Switch : %PFE-3: fpc0 Parity errors generated

The switch has been up for the last three months without generating any alarms or core files. The CPU usage is normal.

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo:  <<<<

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Unit: 0  

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Multiple: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Reg: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Parity error..  <<<<<<<<<

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Parity errors generated  <<<<

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:_soc_tomahawk_print_ser_fifo_details: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Error in: SOP cell. 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:_soc_tomahawk_print_ser_fifo_details: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Blk: 2, Pipe: 1, Address: 0x28000432, base: 0x4, stage: 10, index: 50 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_ser_correction:  <<<<<<

Sep 2 03:29:58 Switch : %PFE-3: fpc0 SER_CORRECTION: reg/mem:85848 btype:19 sblk:2 at:-1 stage:10 addr:0x28000432 port: 0 index: 50 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:_soc_ser_reg_correction: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 reg: 85848=TDBGC4 port: 50 index: 0 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:_soc_ser_reg_correction: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 COUNTER_CLEAR: TDBGC4[85848] blk: epipe0 index: 0 : port[50] 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Unit: 0  

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Multiple: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Reg: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Parity error.. 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Parity errors generated 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Reg: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 0:soc_tomahawk_process_ser_fifo: 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Parity error.. 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Parity errors generated 

Sep 2 03:29:58 Switch : %PFE-3: fpc0 Error in: SOP cell. 

• Based on the log message, we see that parity errors have been recorded on the device and have been corrected by the software.
• To verify that all detected parity errors have been addressed, please run the command below.

start shell

% cprod -A fpc0 -c 'set dcbcm bcmshell "soc"'

• If the parity errors are cleared completely and the logs are not repetitive, there is nothing that needs to be done from our end. 
• However if the logs are continuous, then we can power drain the device. If the issue persists post power drain as well, Please contact JTAC for further investigation.