This article explains how to troubleshoot FPC Major Alarm With Error Code 0x210523
1 alarms currently active
Alarm time Class Description
2025-03-31 17:43:49 PDT Major FPC 2 Major Errors
Mar 31 17:43:49.471 router-re0 fpc2 pechip_cmerror_set_error:3196: Level: Major, cmerror_code: 0x210523 (id=1315), recover_err: 0 chip_id: 1, current count: 0, threshold: 16, (counter: 0), fh_msg: 0x0
Mar 31 17:43:49.494 router-re0 fpc2 INTR: throttle 30sec PECHIP[1]:pe.fabrord[0].protect.par_protect.interrupts.status:detected_l1_fbm(0): (Count:1)
Mar 31 17:43:49.515 router-re0 fpc2 CMError: /fpc/2/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_FABRORD0_PAR_PROTECT_FSET_REG_DETECTED_L1_FBM (0x210523), scope: pfe, category: processing, severity: major, module: PE Chip, type: Description for PECHIP_CMERROR_FABRORD0_PAR_PROTECT_FSET_REG_DETECTED_L1_FBM, oc_category: default
Mar 31 17:43:49.516 router-re0 fpc2 Performing action get-state for error /fpc/2/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_FABRORD0_PAR_PROTECT_FSET_REG_DETECTED_L1_FBM (0x210523) in module: PE Chip with scope: pfe category: processing level: major, oc_category: default
Mar 31 17:43:49.783 router-re0 fpc2 Performing action cmalarm for error /fpc/2/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_FABRORD0_PAR_PROTECT_FSET_REG_DETECTED_L1_FBM (0x210523) in module: PE Chip with scope: pfe category: processing level: major, oc_category: default
Mar 31 17:43:49.784 router-re0 fpc2 Cmerror Op Set: PE Chip: PE1[1]: FABRORD[0-Data]:ecc: 0x00080000: Free bits memory for L1 table (URI: /fpc/2/pfe/0/cm/0/PE_Chip/1/PECHIP_CMERROR_FABRORD0_PAR_PROTECT_FSET_REG_DETECTED_L1_FBM)
Mar 31 17:43:49.864 router-re0 alarmd[33065]: Alarm set: FPC id=150995560, color=RED, class=CHASSIS, reason=FPC 2 Major Errors
Mar 31 17:43:49.865 router-re0 craftd[32230]: Receive FX craftd set alarm message: color: 1 class: 100 object: 104 slot: 2 silent: 0 short_reason=FPC 2 Major Errors long_reason=FPC 2 Major Errors id=150995560 reason=150994944
Mar 31 17:43:49.865 router-re0 craftd[32230]: Major alarm set, FPC 2 Major Errors
These errors are due to the Timeout in the Timestamp database which might occur during Fabric Re-ordering.
If the PFE is active, the corrupted memory location will be overwritten with the correct timestamp on the new incoming fabric cell.
If we saw these error had just one occurrence, then it could be a transient issue.
We need to reboot the affected FPC and monitor the alarm/error. If the error/alarm reappears post FPC reboot, need to replace the FPC.