Support Support Downloads Knowledge Base Case Manager My Juniper 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

[MX] FPC Major Alarm XQ-chip: CPQ-OCM headoffset error detected

0

0

Article ID: KB37089 KB Last Updated: 11 Jun 2021Version: 1.0
Summary:

This article explains the meaning of the 'Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM headoffset error detected' syslog message along with the corresponding major alarm and clarifies whether any actions need to be taken.

Symptoms:

Output of 'show system alarm' indicates 'Major Errors' alarm:

user@device> show system alarms
1 alarms currently active
Alarm time               Class  Description
2021-05-27 05:44:12 BST  Major  FPC 1 Major Errors

The following log messages can be seen:

May 27 05:44:07  device : %PFE-3: fpc1 xqchip_read_u32:33 XQ-chip(0): pio_handle(0x170b8700); pio_read_u32() failed: 1(generic failure)! addr=000000000140dff0
May 27 05:44:07  device : %PFE-3: fpc1 xqchip_cpq_queue_flush:282 XQ-chip[0]: Q Index: 14332 cpq.cpq_ocm read failed
May 27 05:44:07  device : %PFE-3: fpc1 COS_HALP_JAM(cos_halp_jam_free_l4_node:4412): sched_free_l4_node for ifd lt-1/1/0 type IFL 1073786098 failed
May 27 05:44:07  device : %PFE-3: fpc1 COS_HALP(cos_halp_free_sched_nodes:1436): L4 Scheduler free failed IFL:1073786098[IFD:489]
May 27 05:44:08  device : %PFE-3: fpc1 COS_HALP(cos_halp_unbind_tc_profile_on_ifl:751): Scheduler node free failed IFL:1073786098[IFD:489]
May 27 05:44:08  device : %PFE-3: fpc1 COS(cos_unbind_final_scheduler_on_ifl:2231): Unbind tc profile failed IFL:1073786098
May 27 05:44:08  device : %PFE-3: fpc1 cos_ifl_tcprofile_delete_action_wrapper:1792: TCP delet failed for ifl = 1073786098 ret 1, msg COS_IFL_TCP
May 27 05:44:08  device : %PFE-3: fpc1 vbf_cos_ifl_sched_node_op:907: vbf_cos_ifl_tcp_delete failed
May 27 05:44:08  device : %PFE-3: fpc1 trinity_pio: 2 PIO errors occurred
May 27 05:44:08  device : %PFE-3: fpc1 trinity_pio: Last error: 3     XQ Trinity PCI       0x000000f0 Read  PCIe   0
May 27 05:44:10  device : %PFE-5: fpc1 Performing action cmalarm for error /fpc/1/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADOFFSET (0x8025a) in module: XQCHIP(46) with scope: board category: functional level: major
May 27 05:44:10  device : %PFE-3: fpc1 Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM headoffset error detected
May 27 05:44:11  device : %PFE-5: fpc1 Error: /fpc/1/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADOFFSET (0x8025a), scope: board, category: functional, severity: major, module: XQCHIP(46), type: XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADOFFSET
May 27 05:44:11  device : %PFE-5: fpc1 Performing action get-state for error /fpc/1/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADOFFSET (0x8025a) in module: XQCHIP(46) with scope: board category: functional level: major
May 27 05:44:12  device : %PFE-5: fpc1 Performing action cmalarm for error /fpc/1/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADOFFSET (0x8025a) in module: XQCHIP(46) with scope: board category: functional level: major
May 27 05:44:12  device alarmd[16644]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 1 Major Errors
May 27 05:44:12  device craftd[15866]: %DAEMON-4:  Major alarm set, FPC 1 Major Errors
May 27 05:44:12  device : %PFE-3: fpc1 Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM headoffset error detected
Cause:

This issue is caused by a memory read parity error condition. Here, the FPC has reported a XQ-chip memory parity error. A parity error is an error that results from irregular changes to data, as it is recorded when it is entered in memory.

There are two types of parity errors: soft parity errors and hard parity errors.

  1. Soft parity errors are often caused by electromagnetic field conditions, such as background radiation, electromagnetic interference, or static discharge events.
  2. Hard errors may be caused by power surges, overheating, manufacturing defects, or other causes.
Different types of parity errors can require re-transmission of data or cause serious system errors, such as system crashes.
Solution:

This is typically a transient hardware issue with the XQ-chip internal memory, no RMA is required.

Collect the following output which may provide additional information regarding this issue:
  1.  Collect the 'show' command output.

    show log messages
    start shell pfe network <fpcX>
    show cmerror module brief
    show cmerror module <module_number> error <error_id_number>
    show syslog messages
  2. Analyze the show command output.

    In the show log messages file, review the events that occurred at or just before the appearance of the 'Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM headoffset error detected'
FPC restart during a maintenance window should clear this error.

If the issue is seen repeatedly even after restarting the FPC, contact JTAC for further investigation and assistance.

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