[MX] LUCHIP(*): Bist RLDRAM 1 failed

When a "BIST: Memory Error" event occurs, a message similar to the following is reported:

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Memory Error

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Test Name:Unique Address (Bottom-Up) 

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Error Count: 1

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Error Address: Raw: 0x0000000000000448 Cell: 0x0000000000000011, Burst: 0, Bank: 1 

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Actual Data:  0x00000000000000002240001000000000

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Expected Data: 0x00000000000000002240089000000000 

fpc0 RamBIST:LU-CHIP[3] RLDRAM 1 BIST: Vector Data:  0x00000000000000000000000000000088 

fpc0 LUCHIP(3): Bist RLDRAM 1 failed, FRU:U4755 (LUCHIP3_RLDRAM1) 

fpc0 CMT: LU3 init failed, generic failure 

fpc0 CMT: Failed to init LU chip 3.0 

FPC may go unresponsive when BIST memory is seen.

chassisd[1547]: CHASSISD_FRU_UNRESPONSIVE: Error for FPC 0: unresponsive to attempts to start it; left it offline

CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Error

craftd[1549]: Major alarm set, FPC 0 Hard errors

The cause is due to a memory error detected at POST (Power on Self Test) one FPC does initialize all components. The LUCHIP initialization fails while booting up the FPC due to BIST errors.

Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

show log messages

show log chassisd

start shell network pfe <fpc#>

show nvram

show syslog messages

exit

>Most of the time FPC will not come online and RMA is required. 

>In some cases FPC may come up online even though "Contact your technical support representative" immediately to RMA the card regardless of error rate.