A major FPC alarm was created along with PFE being disabled and service impact as shown below.
user@root> show chassis alarms
1 alarms currently active
Alarm time Class Description
2025-03-14 16:20:52 UTC Major FPC 10 Major Errors - XM Chip Error code: 0x7012c
{master}
user@root> show chassis fpc 10
Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer
10 Online 47 28 0 27 29 32 3584 29 26
user@root> show chassis fpc 10 detail
Slot 10 information:
State Online
Temperature 47 degrees C / 116 degrees F
Total CPU DRAM 3584 MB
Total XR2 518 MB
Total DDR DRAM 49920 MB
Start time 2020-08-18 22:37:36 UTC
Uptime 1668 days, 17 hours, 50 minutes, 41 seconds
Max MPC base power consumption 834 Watts
Max MIC0 power consumption 96 Watts
Max MIC1 power consumption 96 Watts
Max MPC total power consumption 1026 Watts
user@root> show chassis fpc errors
FPC Level Occurred Cleared Threshold Action-Taken Action
10 Minor 0 0 1 0 LOG|CM ALARM|
Major 1 0 1 3 CM ALARM|DISABLE PFE
Fatal 0 0 1 0 RESET
Pfe-State: pfe-0 -DISABLED | pfe-1 -ENABLED | pfe-2 -ENABLED | pfe-3 -ENABLED |
Mar 14 16:20:52 user@root chassisd[7242]: %DAEMON-3: FPC 10 sent action 0x44 that is not configured 0x2
Mar 14 16:20:52 user@root alarmd[7554]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 10 Major Errors - XM Chip Error code: 0x7012c
Mar 14 16:20:52 user@root craftd[7246]: %DAEMON-4: Major alarm set, FPC 10 Major Errors - XM Chip Error code: 0x7012c
Mar 14 16:20:54 user@root : %PFE-3: fpc10 XMCHIP(0): XMCHIP(0): FI: Protect: Log Error 0x1, Log Address 0x6, Multiple Errors 0x0
Mar 14 16:21:06 user@root : %PFE-5: fpc10 PFE 0: 'PFE Disable' action performed. Bringing down ifd et-10/0/0 357
Mar 14 16:21:06 user@root kernel: %KERN-3: if_msg_ifd_cmd_tlv_decode ifd et-10/0/0 #357 down with ASIC Error
Mar 14 16:21:07 user@root : %PFE-3: fpc10 Cmerror Op Set: XMCHIP(0): XMCHIP(0): FI: Protect: Parity error for alloc chunk buffer
Step 1: Recommend to reboot the FPC through CLI
request chassis fpc offline slot 1
request chassis fpc online slot 1
Step 2: If you are still seeing the alarm and the failed message, try and re-seat the FPC.
Re-seat the FPC
Step 3: if the issue is fixed after above steps, we can monitor this transient hardware error for 48hrs. If the alarms persist, we shall proceed further with an RMA for the FPC involved. Contact JTAC for further assistance.