This article describes LUCHIP Memory read error syslog.

The "luchip_index_read_dmem_block: luchip_instance_read_dmem_block error for RC 1" message reports a transient hardware issue.

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 the background scrubbing process of memory reading fails, the below syslog messages can be seen.

:Feb 23 13:11:17 Juniper : %PFE-3: fpc1 luchip_index_read_dmem_block: luchip_instance_read_dmem_block error for RC 1, lu_idx 0. 

:Feb 23 13:11:17 Juniper : %PFE-3: fpc1 jnh_read_cmem_internal(1318): Failed jnh_pread_cmem inst 1, lkup_idx 0 addr 0xc000d132. 

:Feb 23 13:11:17 Juniper : %PFE-3: fpc1 stats_lu_counter_read_internal(1215): pfe 1:[exception-counter] jnh_counter_read error - generic failure 

:Feb 23 13:11:20 Juniper : %PFE-3: fpc1 trinity_pio: 1 PIO errors occurred 

:Feb 23 13:11:20 Juniper : %PFE-3: fpc1 trinity_pio: Last error: 7   LU-1.0 Trinity PCI  0x00000090 Read PCIe  0  

:Feb 23 13:11:17 Juniper : %PFE-3: fpc1 luchip_index_read_dmem_block: luchip_instance_read_dmem_block error for RC 1, lu_idx 0. 

:Feb 23 13:11:17 Juniper : %PFE-3: fpc1 jnh_read_cmem_internal(1318): Failed jnh_pread_cmem inst 1, lkup_idx 0 addr 0xc000d132. 

:Feb 23 13:11:17 Juniper : %PFE-3: fpc1 stats_lu_counter_read_internal(1215): pfe 1:[exception-counter] jnh_counter_read error - generic failure 

:Feb 23 13:11:20 Juniper : %PFE-3: fpc1 trinity_pio: 1 PIO errors occurred 

:Feb 23 13:11:20 Juniper : %PFE-3: fpc1 trinity_pio: Last error: 7   LU-1.0 Trinity PCI  0x00000090 Read PCIe  0  

Indications:

• These memory parity errors will be automatically corrected
• PIO read errors for LUCHIP are due to the background scrubbing process reading the memory fails.
• Single occurrence of this syslog, an event not seen with other events indicates a one-time transient hardware error. Multiple continuous occurrences indicate persistent underlying issues.
• If we see multiple events on the same card then FPC is likely to be faulty.

The PIO read errors for LUCHIP are due to the background scrubbing process reading the memory.

It is a transient hardware error and clears on its own.

A single occurrence of this message indicates a one-time condition.

Perform these steps to determine the cause and resolve the problem:

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

show chassis alarms

show log messages

show log chassisd

show chassis fpc

show chassis fpc detail

start shell pfe network <fpc#>

show nvram 

show syslog messages 

exit

•  Analyze the show command output. In the 'show log messages', review the events that occurred at or just before the appearance of the "PIO errors occurred" message. Frequently these events help identify the cause.
•  FPC restart during a maintenance window should clear this error and alarm.
• If this syslog message appears a second time then this could be a hardware error and card replacement can be done.
•  Contact your technical support representative if the issue is seen after a FPC restart