This KB addresses the chassis alarms where FPC's are having major errors along with log message - CHASSISD_FRU_UNRESPONSIVE_RETRY.
 

Below are the outputs which shows the problem state.

root> show chassis fpc 

           Temp CPU Utilization (%)  CPU Utilization (%) Memory  Utilization (%)

Slot State      (C) Total Interrupt   1min  5min  15min DRAM (MB) Heap   Buffer

 0 Online      39   28     2    26   26   26  2048    34     21

 1 Online      40   27     2    28   28   27  2048    36     21

 2 Offline     ---Chassis connection dropped---

root> show chassis fpc 

           Temp CPU Utilization (%)  CPU Utilization (%) Memory  Utilization (%)

Slot State      (C) Total Interrupt   1min  5min  15min DRAM (MB) Heap   Buffer

 0 Online      40   25     3    28   27   27  2048    34     21

 1 Online      40   32     3    30   28   27  2048    36     21

 2 Present      29

Aug 2 14:57:57.696 2024 root fpc2 XL[0:0]:xl asic num 0 Bist XRIF 2 failed, FRU:U90018 (XLCHIP0_XR2_1)

Aug 2 15:00:10.678 2024 root fpc2 XL[0:0]:xl asic num 0 Bist XRIF 2 failed, FRU:U90018 (XLCHIP0_XR2_1)

Aug 2 15:01:55.398 2024 root chassisd[11194]: CHASSISD_FRU_UNRESPONSIVE_RETRY: Attempt 1 to power on FPC 2 timed out; restarted it

Aug 2 14:50:41.490 2024 root chassisd[11194]: CHASSISD_FRU_UNRESPONSIVE: Error for FPC 2: unresponsive to attempts to start it; left it offline

Aug 2 14:50:41.591 2024 root chassisd[11194]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 2 offline: Error

Aug 2 15:04:34 atlas_i2cs_power_ok: FPC-2 Power Up State 0x00000008

Aug 2 15:04:34 atlas_i2cs_power_ok: FPC-2 Power Disable Cause 0x00000000

Aug 2 15:04:34 atlas_i2cs_power_ok: FPC-2 Power VFail 1 Cause 0x00000000

Aug 2 15:04:34 atlas_i2cs_power_ok: FPC-2 Power VFail 2 Cause 0x00000000

root> show chassis alarms 

3 alarms currently active

Alarm time        Class Description

2024-08-02 14:50:41 +05 Major FPC 2 Hard errors

2024-08-02 12:59:33 +05 Major FPC 2 Major Errors

Before proceeding with RMA for the FPC (linecard), please follow the procedures below:

1. Check Related Events
   Review any related events that occurred at or just before the log message to gather hints on the possible cause of the problem.

2. Reboot / Reseat the FPC (Linecard)

   • Soft Restart: Use the following command to perform a soft restart:
     request chassis fpc slot <slot-number> (offline | online | restart)
   • Hard Reseat: Physically remove and reinsert the FPC during a maintenance window. Ensure the FPC module is clean when reinserted.

3. Stabilization
   Wait for the FPC to stabilize before concluding it to be a hardware issue, especially if the FPC or router was recently rebooted.