This article explains the meaning of the 'XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_TAILOFFSET_EOP (0x80258)' syslog message along with the corresponding major alarm and clarifies whether any actions need to be taken.
Output of 'show system alarm' indicates 'Major Errors' alarm:
user@device> show chassis alarms no-forwarding
1 alarms currently active
Alarm time Class Description
2024-05-20 04:51:17 UTC Major FPC 5 Major Errors
Log:-
May 20 04:51:13 device fpc5 xqchip_read_u32:33 XQ-chip(0): pio_handle(0x196a01e0); pio_read_u32() failed: 1(generic failure)! addr=000000000161215c
May 20 04:51:13 device fpc5 xqchip_cpq_queue_flush:282 XQ-chip[0]: Q Index: 542807 cpq.cpq_ocm read failed
May 20 04:51:13 device fpc5 COS_HALP_JAM(cos_halp_jam_free_l4_node:4415): sched_free_l4_node for ifd xe-5/1/6 type IFL 1073756848 failed
May 20 04:51:14 device fpc5 COS_HALP(cos_halp_free_sched_nodes:1438): L4 Scheduler free failed IFL:1073756848[IFD:520]
May 20 04:51:14 device fpc5 COS_HALP(cos_halp_unbind_tc_profile_on_ifl:751): Scheduler node free failed IFL:1073756848[IFD:520]
May 20 04:51:14 device fpc5 COS(cos_ifl_walk_ifd:6921): walker failed IFD:520:xe-5/1/6
May 20 04:51:15 device fpc5 Error: /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_TAILOFFSET_EOP (0x80258), scope: pfe, category: functional, severity: major, module: XQCHIP(46), type: XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_TAILOFFSET_EOP
May 20 04:51:15 device fpc5 Performing action log for error /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_TAILOFFSET_EOP (0x80258) in module: XQCHIP(46) with scope: pfe category: functional level: major
May 20 04:51:16 device fpc5 Performing action get-state for error /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_TAILOFFSET_EOP (0x80258) in module: XQCHIP(46) with scope: pfe category: functional level: major
May 20 04:51:16 device fpc5 trinity_pio: 1 PIO errors occurred
May 20 04:51:16 device fpc5 trinity_pio: Last error: 3 XQ Trinity PCI 0x0000005c Read PCIe 0
May 20 04:51:16 device fpc5 CMIC(5/1) link 6 SFP receive power low alarm set
May 20 04:51:16 device fpc5 CMIC(5/1) link 6 SFP receive power low warning set
May 20 04:51:17 device fpc5 Performing action cmalarm for error /fpc/5/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_TAILOFFSET_EOP (0x80258) in module: XQCHIP(46) with scope: pfe category: functional level: major
May 20 04:51:17 device fpc5 Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM tailoffset_eop error detected
May 20 04:56:12 device fpc5 CMIC(5/1) link 6 SFP receive power low alarm cleared
May 20 04:56:12 device fpc5 CMIC(5/1) link 6 SFP receive power low warning cleared
This issue is caused by a memory read parity error condition. Here, the FPC has reported a XQ-chip memory parity error that leads to failure of queue flush and failure to free up a scheduler node.
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.
This is typically a transient hardware issue with the XQ-chip internal memory, no RMA is required.
A FPC reset during a maintenance window will clear this error. If the issue is seen repeatedly even after restarting the FPC, contact Support for further investigation and assistance.