This article discusses a scenario when FPC Major Error "XQCHIP(): XQ-chip(): CPQ-OCM qcount error detected" is reported on MX router and clarifies whether any actions need to be taken.
user@device> show system alarms 1 alarms currently active Alarm time Class Description <date> <time> Major FPC 9 Major Errors
user@device> show chassis errors active detail fpc-slot 9 Slot 9 -------------------------------------------------- Location : FPC 9 Identifier : /fpc/9/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT Error : XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT Scope : pfe Category : functional Severity : Major Details : XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT Count : 1 Support : No help info provided
Feb 29 14:13:42 fpc9 xqchip_read_u32:33 XQ-chip(0): pio_handle(0x18cb1788); pio_read_u32() failed: 1(generic failure)! addr=000000000162a344 Feb 29 14:13:42 fpc9 xqchip_cpq_queue_flush:282 XQ-chip[0]: Q Index: 567505 cpq.cpq_ocm read failed Feb 29 14:13:42 fpc9 COS_HALP_JAM(cos_halp_jam_free_l4_node:4418): sched_free_l4_node for ifd lt-9/3/0 type IFL 1073986164 failed Feb 29 14:13:42 fpc9 PFE_ERROR_FAIL_OPERATION: L4 Scheduler free failed IFL:1073986164[IFD:1580] Feb 29 14:13:42 fpc9 PFE_ERROR_FAIL_OPERATION: Scheduler node free failed IFL:1073986164[IFD:1580] Feb 29 14:13:42 fpc9 COS(cos_ifl_walk_ifd:7258): walker failed IFD:1580:lt-9/3/0 Feb 29 14:13:43 fpc9 CMError: /fpc/9/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT (0x80259), scope: pfe, category: functional, severity: major, module: XQCHIP(46), type: XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT Feb 29 14:13:44 fpc9 Performing action get-state for error /fpc/9/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT (0x80259) in module: XQCHIP(46) with scope: pfe category: functional level: major Feb 29 14:13:51 fpc9 trinity_pio: 1 PIO errors occurred Feb 29 14:13:51 fpc9 trinity_pio: Last error: 3 XQ Trinity PCI 0x00000044 Read PCIe 0 Feb 29 14:13:51 fpc9 trinity_pio: Last error: Register Addr 0x0162a344 Feb 29 14:13:51 fpc9 Performing action cmalarm for error /fpc/9/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT (0x80259) in module: XQCHIP(46) with scope: pfe category: functional level: major Feb 29 14:13:52 fpc9 Cmerror Op Set: XQCHIP(46): XQ-chip[0]: CPQ-OCM qcount error detected (URI: /fpc/9/pfe/0/cm/0/XQCHIP(46)/0/XQ_CMERROR_OCM_PROTECT_SET_1_REG_DETECTED_QCOUNT)
In the output of "show log messages" review the events that occurred at or just before the appearance of the "XQCHIP(): XQ-chip(): CPQ-OCM qcount error detected" alarm. Frequently these events help identify the cause.This issue is caused by a memory read error condition. Here, the FPC has reported a XQ-chip memory read 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.
This is typically a transient hardware issue with the XQ-chip internal memory, no RMA is required.Recommended actions:
If the issue is seen repeatedly even after restarting the FPC, contact Support for further investigation and assistance.