The "BIST: Memory Error" message reports a hardware issue on MQChip.

This is a Troubleshooting Article for a PFE ASIC Syslog Event.

To view other documented syslog events related to XMCHIP, XLCHIP, MQCHIP, LUCHIP, EACHIP, and PECHIP, see KB31893 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events  [juniper.net].

When a "BIST: Memory Error" event occurs, a message similar to the following is reported by MQChip and may not boot up and will cause the FPC to becomes unresponsive.

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Memory Error 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Test Name:Unique Address (Bottom-Up) 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Error Count: 1 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Error Address: Raw: 0x000000000068d440 Cell: 0x000000000001a351, Burst: 0, Bank: 0 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Actual Data: 0x0000000000000000101035351a1a1030 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Expected Data: 0x0000000000000000101035351a1a1010 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Vector Data: 0x00000000000000000000000000000020 

<host> %PFE-{*}: fpc{*} RamBIST:MQ-CHIP[0] DMC 1 DDR 2 BIST: Error Vector: 0x00000000000000000000000000000020 

<host> %PFE-{*}: fpc{*} MQCHIP(0): mqchip_init: DDR3 boot diag failed - status 1 

<host> %PFE-{*}: fpc{*} CMT: MQ chip init failed, chip 0 

<host> %PFE-{*}: fpc{*} CMT: Failed to init MQ chip 0 

<host> %PFE-{*}: fpc{*} mqchip_config_host_stream() MQCHIP(0) not initialized 

Indications:

• This memory error upon BIST failure will prevent the FPC from coming online

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.

{DIDYOUKNOWSERVICENOWTOKEN.EN_US}

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

Collect the show command output.

1. 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.
2. show log messages
3. show log chassisd
4. start shell network pfe <fpc#>
5. show nvram
6. show syslog messages
7. exitAnalyze the show command output.

In the 'show log messages', review the events that occurred at or just before the appearance of the "BIST: Memory Error" message. Frequently these events help identify the cause.

• Offline the FPC in case it still came online.
• Run the CLI command ‘ request chassis fpc slot # offline ’,
  • For more information on the command, see  request chassis fpc .
• ​Contact your technical support representative immediately to RMA the card regardless of error rate.

This article is indexed in  KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events  [juniper.net]tag LUCHIPTSG

Tip: When looking at an event in the logs, it is important to focus on the first error message in a collection of syslog messages. The first error message is usually the cause of all the follow-on error messages. The follow-on collateral damage error messages can be ignored.