Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: CBO[.] parity error

0

0

Article ID: KB32158 KB Last Updated: 12 Oct 2021Version: 2.0
Summary:

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 - Index of Articles for Troubleshooting PFE ASIC Syslog Events.

.

Symptoms:

When a "CBO[.] parity error" event occurs, messages similar of the following are reported:

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

Cause:

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.

Solution:

Perform these steps to determine the cause and resolve the problem (if any).  Continue through each step until the problem is resolved.

  1. 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

  2. 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; tag EACHIPTSG XLCHIPTSG


Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search