Junos OS

I get these errors on FPC card when under heavy attacks anything I can do to minimize these a large packet lost occur as well

Feb  6 18:28:15   fpc3 MQCHIP(2) FI Error-cell sent to reorder engine
Feb  6 18:28:16   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:16   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error
Feb  6 18:28:16   fpc3 MQCHIP(1) DDRIF WO Checksum Error
Feb  6 18:28:16   fpc3 MQCHIP(1) DDRIF WO Checksum Error Information Quantum 0 bank num 59, ddrio[3].dmcN[1].bank[3] Error bcount 32, error addr 0x1000bf => cell addr 0x1000b => row:col 0400:0b
Feb  6 18:28:16   fpc3 MQCHIP(1) DDRIF Poison Cnts  Current 35, Total 7858
Feb  6 18:28:16   fpc3 MQCHIP(1) DDRIF Chksum Cnts  Current 35, Total 7857
Feb  6 18:28:16   fpc3 MQCHIP(1) FO half 0 packet error
Feb  6 18:28:16   fpc3 MQCHIP(1) FI Error-cell sent to reorder engine
Feb  6 18:28:16   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:16   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:16   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 3 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x5082f383
Feb  6 18:28:17   fpc3 MQCHIP(1) WO Packet error
Feb  6 18:28:17   fpc3 MQCHIP(2) FI Error-cell sent to reorder engine
Feb  6 18:28:17   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:19   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:20   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error
Feb  6 18:28:20   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error Information Quantum 0 bank num 49, ddrio[3].dmcN[0].bank[1] Quantum 1 bank num 50, ddrio[3].dmcN[0].bank[2] Error bcount 34, error addr 0x3a0032 => cell addr 0x3a003 => row:col 0e80:03
Feb  6 18:28:20   fpc3 MQCHIP(1) DDRIF WO Checksum Error
Feb  6 18:28:20   fpc3 MQCHIP(1) DDRIF Poison Cnts  Current 255, Total 8113
Feb  6 18:28:20   fpc3 MQCHIP(1) DDRIF Chksum Cnts  Current 255, Total 8112
Feb  6 18:28:20   fpc3 MQCHIP(1) FO half 0 packet error
Feb  6 18:28:20   fpc3 MQCHIP(1) FI Error-cell sent to reorder engine
Feb  6 18:28:20   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:20   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:20   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 1 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x800000
Feb  6 18:28:21   fpc3 MQCHIP(1) WO Packet error
Feb  6 18:28:21   fpc3 MQCHIP(2) FI Error-cell sent to reorder engine
Feb  6 18:28:21   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:21   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error
Feb  6 18:28:21   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error Information Quantum 0 bank num 41, ddrio[2].dmcN[1].bank[1] Error bcount 32, error addr 0x4a0022 => cell addr 0x4a002 => row:col 1280:02
Feb  6 18:28:21   fpc3 MQCHIP(1) DDRIF WO Checksum Error
Feb  6 18:28:21   fpc3 MQCHIP(1) DDRIF Poison Cnts  Current 255, Total 8368
Feb  6 18:28:21   fpc3 MQCHIP(1) DDRIF Chksum Cnts  Current 255, Total 8367
Feb  6 18:28:21   fpc3 MQCHIP(1) FO half 0 packet error
Feb  6 18:28:21   fpc3 MQCHIP(1) FI Error-cell sent to reorder engine
Feb  6 18:28:21   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:22   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:22   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 1 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x800000
Feb  6 18:28:22   fpc3 MQCHIP(1) WO Packet error
Feb  6 18:28:22   fpc3 MQCHIP(2) FI Error-cell sent to reorder engine
Feb  6 18:28:22   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:22   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error
Feb  6 18:28:22   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error Information Quantum 0 bank num 60, ddrio[3].dmcN[1].bank[4] Error bcount 32, error addr 0x5a0009 => cell addr 0x5a000 => row:col 1680:00
Feb  6 18:28:22   fpc3 MQCHIP(1) DDRIF WO Checksum Error
Feb  6 18:28:22   fpc3 MQCHIP(1) DDRIF Poison Cnts  Current 255, Total 8623
Feb  6 18:28:22   fpc3 MQCHIP(1) DDRIF Chksum Cnts  Current 255, Total 8622
Feb  6 18:28:22   fpc3 MQCHIP(1) FO half 0 packet error
Feb  6 18:28:23   fpc3 MQCHIP(1) FI Error-cell sent to reorder engine
Feb  6 18:28:23   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:23   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:23   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 1 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x800000
Feb  6 18:28:23   fpc3 MQCHIP(1) WO Packet error
Feb  6 18:28:23   fpc3 MQCHIP(2) FI Error-cell sent to reorder engine
Feb  6 18:28:23   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:23   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error
Feb  6 18:28:23   fpc3 MQCHIP(1) DDRIF FO0 Checksum Error Information Quantum 0 bank num 16, ddrio[1].dmcN[0].bank[0] Error bcount 32, error addr 0x3a004d => cell addr 0x3a004 => row:col 0e80:04
Feb  6 18:28:23   fpc3 MQCHIP(1) DDRIF WO Checksum Error
Feb  6 18:28:23   fpc3 MQCHIP(1) DDRIF Poison Cnts  Current 255, Total 8878
Feb  6 18:28:24   fpc3 MQCHIP(1) DDRIF Chksum Cnts  Current 255, Total 8877
Feb  6 18:28:24   fpc3 MQCHIP(1) FO half 0 packet error
Feb  6 18:28:24   fpc3 MQCHIP(1) FI Error-cell sent to reorder engine
Feb  6 18:28:24   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:24   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:24   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 3 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x5082f8ad
Feb  6 18:28:24   fpc3 MQCHIP(1) WO Packet error
Feb  6 18:28:24   fpc3 MQCHIP(2) FI Error-cell sent to reorder engine
Feb  6 18:28:24   fpc3 MQCHIP(0) FI Error-cell sent to reorder engine
Feb  6 18:28:25   fpc3 CM:C3������C��^X
Feb  6 18:28:25   fpc3 CM:MPC fabric remote PFE error (rate based) (1) exceed raising threshold (1) occurrance (0) for module/pfe (4:2)
Feb  6 18:28:26   fpc3 CM:M-^DM-^HM-^@M-^DM-^DM-^HM-^@M-^DDM-^HM-^@M-^DM-^DM-^HM-^@M-^DM-^DM-^HM-^@M-^D$M-^HM-^@M-^DFn=pD
Feb  6 18:28:27   fpc3 CM:MPC fabric remote PFE error (rate based) (1) exceed raising threshold (1) occurrance (0) for module/pfe (4:1)
Feb  6 18:28:31   fpc3 PFE 0: Possible Remote PFE fault detected, total 3 times since up.
Feb  6 18:28:31   fpc3 PFE 0: exceeding aggr threshold 100 curr/last err_cell (3608/2829)
Feb  6 18:28:31   fpc3 CM:
Feb  6 18:28:31   fpc3 CM:/2829)

Hi,

As there are lot of parity errors reported, it looks to be a hardware issue with this FPC. You can try resetting the card once to see if these errors go away. If not, you may have to replace this line card.

Feb  6 18:28:16   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:16   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:16   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 3 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x5082f383
Feb  6 18:28:20   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:20   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:20   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 1 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x800000
Feb  6 18:28:21   fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Feb  6 18:28:22   fpc3 MQCHIP(1) OCM Lo Parity Error
Feb  6 18:28:22   fpc3 MQCHIP(1) OCM Parity Error Log: rddst 1 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x800000

Hope this helps:

Thanks

--------------------------------------------------------------------------------------------------------
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
--------------------------------------------------------------------------------------------------------

The reseat resolved it but the error came back.

Should we put the card up for RMA?

What would you do?

Mar  3 20:16:32  fpc3 MQCHIP(1) DDRIF WO Checksum Error
Mar  3 20:16:32  fpc3 MQCHIP(1) DDRIF WO Checksum Error Information Quantum 0 bank num 17, ddrio[1].dmcN[0].bank[1] Error bcount 32, error addr 0x500028 => cell addr 0x50002 => row:col 1400:02
Mar  3 20:16:32  fpc3 MQCHIP(1) DDRIF Poison Cnts  Current 1, Total 716446
Mar  3 20:16:32  fpc3 MQCHIP(1) DDRIF Chksum Cnts  Current 1, Total 716576
Mar  3 20:16:32  fpc3 MQCHIP(1) OCM Fo0/Ddrif Parity Error
Mar  3 20:16:33  fpc3 MQCHIP(1) OCM Lo Parity Error
Mar  3 20:16:33  fpc3 MQCHIP(1) OCM Parity Error Log: rddst 1 bnk_vec 0x8000 addr 0x72ae bank 15 data 0x2e626f785fe56469
Mar  3 20:16:33  fpc3 MQCHIP(1) WO Packet error

Generally if the errors recur after resets or reseating the card there is an underlying hardware failure.

I have seen this twice on two different routers in our network.  After doing a software reset of the card the issue seems to be resolved.  If this is a one time issue, do you think its software or hardware?