The "lmem data error" message is caused by a transient hardware error which is automatically repaired.

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 data 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 data error 0x00000082
Sep 7 17:11:38.269 router : %PFE-3: fpc8 ppe_lmem_recover(2469) XL[0:0]_PPE  0 Excessive LMEM Data errors require Zone 1 disable.
or
Sep 7 17:11:38.269 router : %PFE-3: fpc8 ppe_lmem_recover(2469) XL[0:0]_PPE  0 too many shared LMEM errors, disabling.

EACHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 EA[0:0]_PPE  0 Errors lmem data error 0x00000082
Sep 7 17:11:38.269 router : %PFE-3: fpc8 ppe_lmem_recover(2469) EA[0:0]_PPE  0 Excessive LMEM Data errors require Zone 1 disable.
or
Sep 7 17:11:38.269 router : %PFE-3: fpc8 ppe_lmem_recover(2469) EA[0:0]_PPE  0 too many shared LMEM errors, disabling.

LUCHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 LUCHIP(0) PPE  0 Errors  lmem data error  0x00000082
Sep 7 17:11:38.269 router : %PFE-3: fpc8 LUCHIP(0) LMEM errors require LUCHIP(0) PPE 0 Zone 0 disable
or
Sep 7 17:11:38.269 router : %PFE-3: fpc8 LUCHIP(0) SHARED LMEM errors require LUCHIP(0) PPE 0 Zone 0 disable​

Indications:

• No service impact

• This error is a transient hardware problem and gets automatically corrected.

• The alarm is raised once specific zones have many repairs, then the specific zone is disabled.

• If the specific zone is a shared zone, then the corresponding PPE will get disabled.

This error is caused by a transient hardware error. LMEM data errors are parity errors and the software will repair those errors automatically.

• If the number of errors exceeds the threshold of 7, then a particular zone will be disabled for further usage.
• If this threshold is reached for shared zones, the entire PPE (Packet Processing Engine) will become disabled.

Recommend Action

• EXCEPTION: If you are running Junos software without the fix for PR1652416, you may need to restart the FPC when encountering this error - See Also KB35702 [juniper.net]
• NO ACTION IS NEEDED
• If multiple PPEs are disabled, you may schedule a maintenance window to restart the FPC to clear the error

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

• No RMA is required for couple incidents

• 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 to RMA the FPC if zones are disabled. 

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

Note: KB Team - All changes to this article must be approved by the AI-Scripts Review team ( [email protected] ) before re-publishing.

• Syslog message: LUCHIP.*PPE.*Errors lmem data error