The "lmem addr error" message is caused by a transient hardware or software defect.

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 "lmem addr error" event occurs, messages similar to the following are reported:

XLCHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 XL[0:0]_PPE 0 Errors lmem addr error

EACHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 EA[0:0]_PPE 25 Errors lmem addr error

LUCHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 LUCHIP(0) PPE 25 Errors lmem addr error​

Indications:

• Single occurrence of a syslog, not seen with other events, indicates a one time hardware error.

• Multiple continuous occurrences indicate persistent underlying issues.

• For each error entry, some data traffic packet drop could be seen, but the losses are not persistent and traffic should resume at 100% as before.

This error is caused by a transient hardware or software defect. Examine other events reported to conclude further guidance.

{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 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 "lmem addr error" message. Frequently these events help identify the cause.

• No RMA is required

• Collect trap debug file in /var/tmp directory. Refer to KB31922 - shell script collecting data if packet forwarding at Packet Forwarding Engine is compromised  [juniper.net]

• Contact your technical support representative fur further guidance.

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