This article describes the meaning and steps to perform to resolve error logs XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR (0x2300d5)

Below chassis alarm would be raised.

root@host> show chassis alarms no-forwarding
1 alarms currently active
Alarm time Class Description
2024-03-05 00:29:38 UTC Major FPC 9 Major Errors
 

Below logs would be observed:

Mar 5 00:29:12 re0 fpc9 cassxr_err_addr(8516): EA[2:0].cass_xr[2] ext_mdata 0x0 != err_mdata 0x7f (cae 1, ext_addr 0x0)
Mar 5 00:29:12 re0 fpc9 Error: /fpc/9/pfe/0/cm/0/XQSS(2)/2/XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR (0x2300d5), scope: pfe, category: functional, severity: major, module: XQSS(2), type: XQSS CPQW LP RD error
Mar 5 00:29:12 re0 fpc9 Performing action get-state for error /fpc/9/pfe/0/cm/0/XQSS(2)/2/XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR (0x2300d5) in module: XQSS(2) with scope: pfe category: functional level: major
Mar 5 00:29:33 re0 fpc9 cassxr_err_addr(8516): EA[2:0].cass_xr[2] ext_mdata 0x0 != err_mdata 0x7f (cae 1, ext_addr 0x0)
Mar 5 00:29:34 re0 fpc9 cassxr_err_addr(8516): EA[2:0].cass_xr[2] ext_mdata 0x0 != err_mdata 0x7f (cae 1, ext_addr 0x0)
Mar 5 00:29:38 re0 fpc9 Performing action cmalarm for error /fpc/9/pfe/0/cm/0/XQSS(2)/2/XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR (0x2300d5) in module: XQSS(2) with scope: pfe category: functional level: major
Mar 5 00:29:38 re0 fpc9 Performing action disable-pfe for error /fpc/9/pfe/0/cm/0/XQSS(2)/2/XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR (0x2300d5) in module: XQSS(2) with scope: pfe category: functional level: major
Mar 5 00:29:38 re0 fpc9 PFE 2: 'PFE Disable' action performed. Bringing down ifd et-9/1/0 1322
Mar 5 00:29:38 re0 fpc9 PFE 2: 'PFE Disable' action performed. Bringing down ifd et-9/1/1 1323
Mar 5 00:29:38 re0 fpc9 PFE 2: 'PFE Disable' action performed. Bringing down ifd et-9/1/2 1324
Mar 5 00:29:38 re0 fpc9 PFE 2: 'PFE Disable' action performed. Bringing down ifd et-9/1/3 1325
Mar 5 00:29:38 re0 fpc9 PFE 2: 'PFE Disable' action performed. Bringing down ifd et-9/1/0 1322
Mar 5 00:29:38 re0 host01 fpc9 Cmerror Op Set: XQSS(2): XQ-SS[2]: CPQW LP XR Read is returned with Error (URI: /fpc/9/pfe/0/cm/0/XQSS(2)/2/XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR)
Mar 5 00:29:38 re0 alarmd[29664]: Alarm set: FPC id=150997352, color=RED, class=CHASSIS, reason=FPC 9 Major Errors
Mar 5 00:29:38 re0 craftd[27777]: Major alarm set, FPC 9 Major Errors

root@host> show chassis fpc errors 9
Mar 05 01:33:15
FPC Scope Category Level Occurred Cleared Threshold Action-Taken Action
9 board functional Minor 0 0 1 0 LOG|CM ALARM|
pfe functional Minor 0 0 1 0 LOG|CM ALARM|
Major 1 0 1 3 GET STATE|CM ALARM|DISABLE PFE
Pfe-State: pfe-0 -ENABLED | pfe-1 -ENABLED | pfe-2 -DISABLED | pfe-3 -ENABLED |

The log message "XQSS_CMERROR_CPQW_ERR_INT_FSET_LP_RD_ERR (0x2300d5)" indicates an error related to the XQSS (Queuing Subsystem) in the PFE ASIC, specifically related to a read operation in the LP (Logical Port) of the FSET (Forwarding Set) within the CPQW (Central Packet Queuing and Scheduling) module.

This indicates that it could be a transient hardware issue within the PFE ASIC.

As it is a major error. The PFE that has these errors would be marked as disabled(which is a default action), due to which all ports relating to that PFE will be down. If FPC isn't rebooted go ahead and restart the FPC in MW for recovering the ports which were disabled because of the major error’s default action.

If you observe this issue post reboot, It could indicate a potential hardware issue. Kindly replace the FPC with the new one.