This article explains the meaning of the "FPC Major Errors - XM Chip Error code: 0x7006a"

The following log messages are seen on the Flexible PIC Concentrator (FPC):

Sep 8 08:01:40 XXXXXXX : %PFE-3: fpc1 XMCHIP(0): XMCHIP(0): DDRIF: LLISTQ Protect: Multiple Errors 0x0 

Sep 8 08:01:51 XXXXXXX : %PFE-3: fpc1 Cmerror Op Set: XMCHIP(0): XMCHIP(0): DDRIF: LLISTQ Protect: Parity error for free pointer SRAM (0x20)  

Sep 8 08:01:52 XXXXXXX alarmd[20697]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 1 Major Errors - XM Chip Error code: 0x7006a

Sep 8 08:01:52 XXXXXXX craftd[18257]: %DAEMON-4: Major alarm set, FPC 1 Major Errors - XM Chip Error code: 0x7006a

Sep 8 08:02:00 XXXXXXX : %PFE-3: fpc1 XMCHIP(0): CAJD4585: XMCHIP(0): DDRIF: Checksum error for WO1 - Channel 5, Address 0xa0024, Checksum Errors 7, Checksum Poison Count 0 

Sep 8 08:02:00 XXXXXXX : %PFE-3: fpc1 XMCHIP(0): XMCHIP(0): DDRIF: 2x32 Instance 1, Part 2 - Write rate: 178280, Read rate: 178279, Total rate: 356559 

Sep 8 08:02:00 XXXXXXX : %PFE-3: fpc1 XMCHIP(0): XMCHIP(0): DDRIF: Packet memory - Write rate: 3209251, Read rate: 3209255, Total rate: 6418506 

Sep 8 08:02:00 XXXXXXX : %PFE-3: fpc1 XMCHIP(0): XMCHIP(0): DDRIF: Linkram memory - Write rate: 49, Read rate: 0, Total rate: 49 

Sep 8 08:02:01 XXXXXXX : %PFE-3: fpc1 XMCHIP(0): XMCHIP(0): WO1: Packet error - Error Packets 6, Stream 32 

The cause is a hardware memory error. "ECC" stands for Error Checking and Correcting, which permits error detection as well as correction of certain errors.

Typically, ECC can detect single and dual bit errors and can correct single-bit errors on its own. The corrected errors are transparent to the system. If the message occurs just once or very sporadically, it can be ignored.

In case the FPC is offline due to the error, there is a possibility that this error is fatal in nature. In order to recover from the error, ideally, the FPC resets on its own. In case the FPC is offline with the active alarm, users can manually restart the FPC.

Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.

Need to reboot the FPC to recover from error state.

Take the FPC offline and bring it online again or restart the FPC during a maintenance window, to clear a possible improper state on the chip

user@mx> request chassis fpc slot <slot number> offline

Wait for a few minutes.

user@mx> request chassis fpc slot <slot number> online

OR

user@mx> request chassis fpc slot <slot number> restart

If the issue is still unresolved, please reach out to Juniper support.