Description

The " luchip_repetitive_err_chk" message reported on FPC which is tranisent 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].

Symptoms

Below logs are noticed "luchip_repetitive_err_chk" on the FPC.

 %PFE-3: fpc3 luchip_repetitive_err_chk(1141): ERRMSG(cnt 1): LUCHIP(4) RD_NACK 2 AP[0x04] TOE Read 0x0003fa60
%PFE-3: fpc3 luchip_repetitive_err_chk(1134): Repetitive Errors from single source detected -- saved messages follow.
%PFE-3: fpc3 luchip_repetitive_err_chk(1141): ERRMSG(cnt 1): LUCHIP(4) IDMEM Parity error in Bank 2, Count 8, IDMEM Bank 2 Offset 0x00001f45 IDMEM[0x007d1e] Rd 0x1000000008b73f38.
 %PFE-3: fpc3 luchip_repetitive_err_chk(1141): ERRMSG(cnt 1): LUCHIP(4) IDMEM Parity error in Bank 2, Count 7, IDMEM Bank 2 Offset 0x00001f54 IDMEM[0x007d58] Rd 0x000401a05a05c000.

 

Solution

"luchip_repetitive_err_chk(1141): ERRMSG(cnt 1): LUCHIP(4) IDMEM Parity error in Bank 2, Count 8, IDMEM Bank 2 Offset Offset 0x00001f45 IDMEM[0x007d1e] Rd 0x1000000008b73f38."

The message indicates the function or process within the FPC's software that detected the error. It suggests that there's a routine responsible for checking repetitive errors. It indicates that a parity error has been detected in Bank 2 of the Identifier Memory. The "Count 8" suggests that this is the eighth instance of this error. Additionally, it provides information about the offset within Bank 2 where the error occurred (0x00001f45) and the read value (0x1000000008b73f38). 
 

Workaround:

If syslog occurs only once, it may indicate a transient hardware problem that can be ignored.

Follow these steps to identify the cause and resolve the issue if the logs are repetitively noticed on the FPC. Proceed through each step until the problem is resolved.
 

  1. Gather the output of the following commands:
    • show log messages
    • show log chassisd
    • start shell network pfe <fpc#>
    • show nvram
    • show syslog messages
    • exit

Ensure that you capture the output to a file in case you need to open a technical support case. Configure each SSH client/terminal emulator to log your session.
 

  1. Analyze the output of the show commands.

In the 'show log messages' output, examine the events occurring at or just before the occurrence of the "luchip_repetitive_err_chk" message. Often, these events provide clues to identify the root cause.
 

  1. If the alarms persist even after the FPC is taken offline and then back online, physical resetting of the FPC may be necessary.
  2. For the single occurrence, no RMA is necessary.

Modification History

2024-03-29 : Article Created