Description

This article explains the meaning of the 'XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADEOP (0x8025b)' syslog message along with the corresponding minor alarm and clarifies whether any actions need to be taken.

Symptoms

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

user@device> show chassis alarms no-forwarding
1 alarms currently active
Alarm time Class Description
2023-11-29 05:43:26 UTC Minor FPC 7 Minor Errors

The following log messages can be seen:

Nov 29 05:43:25 device fpc7 xqchip_read_u32:33 XQ-chip(0): pio_handle(0x196a0ff0); pio_read_u32() failed: 1(generic failure)! addr=0000000001
Nov 29 05:43:25 device fpc7 xqchip_cpq_queue_flush:282 XQ-chip[0]: Q Index: 24028 cpq.cpq_ocm read failed 
Nov 29 05:43:25 device fpc7 COS_HALP_JAM(cos_halp_jam_free_l4_node:4415): sched_free_l4_node for ifd xe-7/0/5 type IFL 1073749654 failed 
Nov 29 05:43:26 device fpc7 COS_HALP(cos_halp_free_sched_nodes:1438): L4 Scheduler free failed IFL:1073749654[IFD:479] 
Nov 29 05:43:26 device alarmd[8387]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 7 Minor Errors
Nov 29 05:43:26 device craftd[7822]: Minor alarm set, FPC 7 Minor Errors
Nov 29 05:43:26 device fpc7 COS_HALP(cos_halp_unbind_tc_profile_on_ifl:751): Scheduler node free failed IFL:1073749654[IFD:479] 
Nov 29 05:43:26 device fpc7 COS(cos_ifl_walk_ifd:6921): walker failed IFD:479:xe-7/0/5 
Nov 29 05:43:27 device fpc7 Error: /fpc/7/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADEOP (0x8025b), scope: pfe, category: functional, severity: minor, module: XQCHIP(46), type: XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADEOP 
Nov 29 05:43:27 device fpc7 Performing action log for error /fpc/7/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADEOP (0x8025b) in module: XQCHIP(46) with scope: pfe category: functional level: minor 
Nov 29 05:43:27 device fpc7 Performing action cmalarm for error /fpc/7/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_HEADEOP (0x8025b) in module: XQCHIP(46) with scope: pfe category: functional level: minor 
Nov 29 05:43:28 device fpc7 Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM headeop error detected  
Nov 29 05:43:29 device fpc7 trinity_pio: 1 PIO errors occurred 
Nov 29 05:43:29 device fpc7 trinity_pio: Last error: 3   XQ Trinity PCI    0x00000070 Read PCIe  0

 

Solution

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. This is typically a transient hardware issue with the XQ-chip internal memory. No RMA is required in this case.

Please use the following action plan to recover FPC if you hit this problem:

    1. Clear alarm from CLI using command 'clear chassis fpc errors fpc-slot <X> error-id <Y>. Alternatively, all FPC related errors could be cleared using CLI command ''clear chassis fpc errors fpc-slot <X>' all
    2. Monitor FPC for re-occurrence this alarm
    3. If alarm re-occurs, restart FPC
    4. If the issue is seen repeatedly even after restarting the FPC, contact JTAC for further investigation and assistance

    Modification History

    2023-12-05 : Article Created
    2024-01-19 : Changed solution from "restarting the affected FPC" to clearing the error with CLI command.
    2025-03-13 : Major formatting changes, adjusting KB category