The "CBO[.] parity error" message is caused by a transient hardware issue which is automatically repaired. This is a Troubleshooting Article for a PFE ASIC Syslog Event. To view other documented syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, see KB31893 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] . .
When a "CBO[.] parity error" event occurs, messages similar of the following are reported: XLCHIP:
XLCHIP:
Sep 7 17:11:38.269 router : %PFE-3: fpc8 XL[0:0]_PPE 2 Errors CBO[43] parity error
EACHIP:
Sep 7 17:11:38.269 router : %PFE-3: fpc8 EA[0:0]_PPE 0 Errors CBO[50] parity error
Indications:
No service impact
This error is a transient hardware problem
The parity error will be automatically corrected
This error is caused by transient hardware defect. Conditional Branch offset memory is parity protected and will be repaired by the software. There is a possible service impact only if such parity errors are repetitive from different address locations reported.
Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
Collect the show command output.
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log messages show log chassisd start shell network pfe <fpc#> show nvram show syslog messages exit
Analyze the show command output.
In the 'show log messages', review the events that occurred at or just before the appearance of the "CBO[.] parity error" message. Frequently these events help identify the cause.
No RMA is required for a couple of incidents
Contact your technical support representative if this error is reported many times to RMA the FPC.
This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; tag EACHIPTSG XLCHIPTSG