CHASSISD_PIC_HWERROR: PIC 0 in FPC 0 (PIC type 2643, version 0) had hardware error

Description

FPC 0 PIC 0 had hardware failure

Symptoms

Apr 22 19:17:01.463 alarmd[7391]: Alarm set: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure
Apr 22 19:17:01.463 chassisd[6960]: CHASSISD_PIC_HWERROR: PIC 0 in FPC 0 (PIC type 2643, version 0) had hardware error
Apr 22 22:16:51.852 alarmd[7391]: Alarm cleared: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure

Apr 22 22:24:25.608 alarmd[7391]: Alarm set: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure
Apr 22 22:24:25.608 chassisd[6960]: CHASSISD_PIC_HWERROR: PIC 0 in FPC 0 (PIC type 2643, version 0) had hardware error
Apr 22 23:13:08.664 alarmd[7391]: Alarm cleared: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure

Apr 22 23:20:56.187 alarmd[7391]: Alarm set: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure
Apr 22 23:20:56.187 chassisd[6960]: CHASSISD_PIC_HWERROR: PIC 0 in FPC 0 (PIC type 2643, version 0) had hardware error
Apr 23 02:34:32.256 alarmd[7391]: Alarm cleared: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure

Apr 23 02:42:03.182 chassisd[6960]: CHASSISD_PIC_HWERROR: PIC 0 in FPC 0 (PIC type 2643, version 0) had hardware error
Apr 23 02:42:03.183 alarmd[7391]: Alarm set: PIC id=16777335, color=RED, class=CHASSIS, reason=FPC 0 PIC 0 Failure

Solution

>> These are hardware errors that generally end up in RMA.
>> You can still try to recover by performing a reseat of FPC and PIC.
>> If above does not bring the FPC up, then go ahead and create RMA for FPC 0.

Modification History

2024-04-23 : Article Created
2024-09-12 : Added MX480 in Categories.