This Article describes the scenario where we see FPC failure with a hardware error message.
Both the FPC are offline due to a hardware error and Unresponsive.
root@xx> show chassis fpc no-forwarding
Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer
0 Online 48 27 2 26 26 26 8192 25 47
1 Offline ---Unresponsive---
2 Online 48 25 2 25 25 25 8192 25 47
3 Offline ---Hardware error---
4 Online 48 25 2 23 23 23 8192 25 47
Slot 1 information:
State Offline
Reason Unresponsive
Total CPU DRAM 0 MB
Slot 3 information:
Reason Hardware error
Logs for error:
Jan 20 22:06:30.928 chassisd[20368]: CHASSISD_POWER_CHECK: FPC 1 not powering up
Jan 20 22:06:30.939 craftd[20377]: Receive FX craftd set alarm message: color: 1 class: 100 object: 104 slot: 1 silent: 0 short_reason=FPC 1 Hard errors long_reason=FPC 1 Hard errors id=16777576 reason=16777216
Jan 20 22:06:30.948 craftd[20377]: Major alarm set, FPC 1 Hard errors
Jan 20 22:06:54.001 chassisd[20368]: CHASSISD_POWER_CHECK: FPC 3 not powering up
Jan 20 22:06:54.012 alarmd[20975]: Alarm set: FPC id=16778088, color=RED, class=CHASSIS, reason=FPC 3 Hard errors
Jan 20 22:06:54.015 craftd[20377]: Receive FX craftd set alarm message: color: 1 class: 100 object: 104 slot: 3 silent: 0 short_reason=FPC 3 Hard errors long_reason=FPC 3 Hard errors id=16778088 reason=16777216
Jan 20 22:06:54.015 craftd[20377]: Major alarm set, FPC 3 Hard errors
Kindly try the below steps to resolve the issue:
1)Soft Restart the FPC
request chassis fpc slot slot-number (offline | online | restart)
2)Re-seat the affected FPC
Ensure the FPC module is clean before re-inserting it.
3)If all the above steps fail to resolve the issue, you will need to open a JTAC case to request an RMA for FPC.