Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: EA.*Bist XRIF.*failed

1

0

Article ID: KB32087 KB Last Updated: 12 Oct 2021Version: 2.0
Summary:

The "Bist XRIF 0 failed" message reports a memory build in self test error.

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 - Index of Articles for Troubleshooting PFE ASIC Syslog Events.

.

Symptoms:

When a "Bist XRIF 0 failed" event occurs, messages similar to the following is reported:

Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Memory Error
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Test Name:Unique Address (Top-Down)
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Error Count: 1
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Error Address: Raw: 0x00000000001dd778 Cell: 0x000000000000775d, Burst: 0, Bank: 7
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Actual Data: 0x000000000000000000c05170000c4517
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Expected Data: 0x000000000000000000c45170000c4517
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Vector Data: 0x00000000000000000000000000004000
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: Error Vector: 0x00000000000000000004000000000000
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: XR2 Core: 0, Cluster: 2, Internal address: 0x313baea
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: XR2 Macro: 3, Bank: 0x9, Column: 0x6, Row: 0xeb
Aug 17 15:47:24 router-0 fpc7 RamBIST:EA-CHIP[57] XRIF 0 BIST 2: XR2 Word: 0x5, Low bit: 50, Databit: 410
Aug 17 15:47:24 router-0 fpc7 EA 57 chip_num 1, XRIF 0 bist id 2 boot diags failed
Aug 17 15:47:24 router-0 fpc7 EA[1:0]: Bist XRIF 0 failed, FRU:U80008 (EACHIP1_XR2_0)
Aug 17 15:47:24 router-0 kernel: router-0 fpc7 EA[1:0]: Bist XRIF 0 failed, FRU:U80008 (EACHIP1_XR2_0)
Aug 17 15:47:25 router-0 fpc7 eachip_init(2609): EA[1:0] failed XR2 boot diag
Aug 17 15:47:34 router-0 fpc7 eachip_init(2633): Register EA-CHIP HOSTIF
Aug 17 15:47:35 router-0 fpc7 cmtfpc_eachip_init: EA1:0 init failed, generic failure
Aug 17 15:47:35 router-0 fpc7 CMT: Failed to init EA chip 1:0

Indications:

  • FPC will not come online and operational failing self diagnostic test

  • Major alarm FPC hard errors are reported


 
Cause:

This is due to a memory error not passing diagnostic self test during boot initialization.

Solution:

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

  1. Collect the show command output.

    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

  2. Analyze the show command output.

    In the 'show log messages', review the events that occurred at or just before the appearance of the "Bist XRIF 0 failed" message. Frequently these events help identify the cause.

  • RMA is required

  • While waiting for hardware replacement, please configure power off with the following configuration change

    'set chassis fpc <slot> power off'
  • Contact your technical support representative.

This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; tag EACHIPTSG


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.

 
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search