The XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR error (error-id 0x230063) has been identified as a Major error on the FPC. This error type is generally isolated and does not typically lead to significant traffic disruptions or permanent PFE forwarding impacts.
[Jul 13 22:47:55.792 LOG: Debug] cmerror_platformd_set_error: Platformd cmerror setting error with mod_id:17 pfe_id:0 err_id:2293859 and reason:XQ-SS[0]: SCHED DQU QSUM underrun interrupt[Jul 13 22:47:55.792 LOG: Debug] Cmerror: Draining ASIC error message queue[Jul 13 22:47:55.792 LOG: Debug] cmerror_process_queue: module = XQSS(0)[Jul 13 22:47:55.792 LOG: Debug] Cmerror: processing the task op_type 1 for scope 1 and category 0 level 1 level_count 0 occur_count 0 clear_count 0 level_threshold 1 level_action 0x7item errid 2293859 item_threshold 1 item_count 0 item_sub_err_state 0 sub_item errid 0 sub_item_state 0 item_times[Jul 13 22:47:55.792 LOG: Debug] Cmerror: Level 1 count increment 1 occur_count 1 clear_count 0[Jul 13 22:47:55.792 LOG: Debug] Cmerror: Level 1 count increment 1 occur_count 1 clear_count 0[Jul 13 22:47:55.792 LOG: Notice] CMError: /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR (0x230063), scope: pfe, category: functional, severity: major, module: XQSS(0), type: XQSS sched QL4 DQU QSUM underrun, oc_category: unknown oc_category[Jul 13 22:47:55.792 LOG: Debug] Cmerror: Level 1 count 1 (occur_count 1 clear_count 0)crossed threshold 1 action 0x7[Jul 13 22:47:55.792 LOG: Debug] is_managed_external 1, category 0[Jul 13 22:47:55.792 LOG: Debug] cmerror_get_current_alarm_count: count for level 1 = 0[Jul 13 22:47:55.792 LOG: Debug] alarm count for level 1 is incremented and set to 1[Jul 13 22:47:55.792 LOG: Debug] is_managed_external 1, category 0[Jul 13 22:47:55.792 LOG: Debug] cmerror_set_current_alarm_count: count for level 1 = 1[Jul 13 22:47:55.792 LOG: Debug] Cmerror category is NOT internal[Jul 13 22:47:55.792 LOG: Notice] Performing action log for error /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR (0x230063) in module: XQSS(0) with scope: pfe category: functional level: major, oc_category: unknown oc_category[Jul 13 22:47:55.792 LOG: Debug] cmerror_take_action_helper: performing action 1 for scope 1 category 0 level 1 err_id /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR(0x230063) module id 17[Jul 13 22:47:55.792 LOG: Notice] Performing action get-state for error /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR (0x230063) in module: XQSS(0) with scope: pfe category: functional level: major, oc_category: unknown oc_category[Jul 13 22:47:55.792 LOG: Debug] cmerror_take_action_helper: performing action 2 for scope 1 category 0 level 1 err_id /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR(0x230063) module id 17[Jul 13 22:47:55.920 LOG: Info] HBM: hbm_avago_aapl_fw_build_id: ZT[0:0] HBM 0 SBUS FW BUILD ID 0x2002[Jul 13 22:47:55.920 LOG: Info] HBM: hbm_avago_aapl_fw_build_id: ZT[0:0] HBM 1 SBUS FW BUILD ID 0x2002[Jul 13 22:47:55.925 LOG: Debug] platform_zt_module_get_state_cb: module id:17 action 2 error-code 230063[Jul 13 22:47:55.925 LOG: Debug] platform_zt_module_get_state_cb: module id:19 action 2 error-code 230063[Jul 13 22:47:55.925 LOG: Debug] cmerror_platformd_action_ack: Platformd cmerror action ack mod_id:19 pfe_id:0 err_id:0x230063 action:2[Jul 13 22:47:55.925 LOG: Debug] cmerror_platformd_action_ack: Platformd cmerror action ack mod_id:17 pfe_id:0 err_id:0x230063 action:2[Jul 13 22:48:16.059 LOG: Debug] platform_zt_module_get_state_cb: module id:27 action 2 error-code 230063[Jul 13 22:48:16.059 LOG: Debug] platform_zt_module_get_state_ack_cb: module id:17 action 2 error-code 230063 ack 1[Jul 13 22:48:16.059 LOG: Debug] platform_zt_module_get_state_ack_cb: module id:19 action 2 error-code 230063 ack 1[Jul 13 22:48:24.060 LOG: Err] platform_zt_module_get_state_ack_cb: module id:27 action 2 error-code 230063 ack 0 timed out[Jul 13 22:48:24.060 LOG: Info] TFTP (block) write - saw ack 263, expected 264[Jul 13 22:48:24.060 LOG: Notice] Performing action cmalarm for error /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR (0x230063) in module: XQSS(0) with scope: pfe category: functional level: major, oc_category: unknown oc_category[Jul 13 22:48:24.060 LOG: Debug] cmerror_take_action_helper: performing action 4 for scope 1 category 0 level 1 err_id /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR(0x230063) module id 17[Jul 13 22:48:24.060 LOG: Err] Cmerror Op Set: XQSS(0): XQ-SS[0]: SCHED DQU QSUM underrun interrupt(URI: /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR)[Jul 13 22:48:36.041 LOG: Debug] cmerror_platformd_action_ack: Platformd cmerror action ack mod_id:27 pfe_id:0 err_id:0x230063 action:2FMPC9( vty)# show cmerror module 17 error 0x230063Error-id : 0x230063Error Name : XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDRIdentifier : /fpc/9/pfe/0/cm/0/XQSS(0)/0/XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDRDescription : XQSS sched QL4 DQU QSUM underrunState : enabledScope : pfeCategory : functionalPFE : 0Configured Level : MajorDefault Level : MajorCount : 1Threshold : 1Error Limit : 0Occur Count : 1Clear Count : 0OverItemThres Occur Count : 1OverItemThres Clear Count : 0Last-occurred(ms ago) : 4528570Logs:----------------------------------------------------------Index Time Sub-Err State Description----------------------------------------------------------0x230063 0 Major 1 1 1 0 4513069 XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDRFMPC9( vty)# show cmerror module 17Module (17) (XQSS(0))PFE support 1Get state cb 0x0 platform action cb 0x8e3b540 control cb 0x0
Note: Currently this alarm is still under investigation, So far from field "XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR" error id alone is not service affecting, You can clear the error using the following command: "clear chassis fpc errors all fpc-slot x"
Example
Node-18> show chassis alarms1 alarms currently activeAlarm time Class Description2024-07-13 16:48:27 -06 Major FPC 9 Major ErrorsNode-18> clear chassis fpc errors fpc-slot 9 all Clearing error(s) on fpc 9, option all{master}Node-18> show chassis alarms No alarms currently active{master}Node-18>
This error is being tracked via internal PR1793375. Updates regarding this issue will be provided through the PR tracking system as they become available.
For further assistance or if the issue persists after applying the workaround, please contact technical support for additional guidance and troubleshooting steps.