Description

The "LUCHIP TOE Read" 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] .

.

Symptoms

When a "LUCHIP TOE Read" event occurs, a message similar to the following is reported:

Dec 9 15:51:49 router0 fpc8 LUCHIP(12) RD_NACK 2 AP[0x04] TOE Read 0x0404da90
​Dec 9 15:51:49 router0 fpc8 LUCHIP(12)​ IDMEM Parity error in Bank 0, Count 4, IDMEM Bank 0 Offset 0x00003475 IDMEM[0x00d1da] Rd 0x0000000040000000.​

 

Solution

The cause is due to a transient memory error detected in the LUCHIP and usually followed with the report of a parity error. This can be transient in nature, and a one time occurrence can be ignored. The periodic memory check will automatically correct a parity error. However, if multiple memory errors are also reported in the syslog, have your support representative investigate this further.

 

{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.

  1. Collect the show command output.

    {SYSLOGSERVICENOWTOKEN.EN_US}

    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 pfe network <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 "LUCHIP TOE Read" message. Frequently these events help identify the cause.

    • No RMA is required.
    • Contact your technical support representative if this event is reported continuously.
 

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.

 

Modification History

2022-10-21: Mark PR for public - missing from previous review
2019-10-14: Article reviewed for accuracy; no changes required.