Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: lmem data error

2

0

Article ID: KB32162 KB Last Updated: 12 Oct 2021Version: 3.0
Summary:

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 - Index of Articles for Troubleshooting PFE ASIC Syslog Events.

.

Symptoms:

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.

  • Alarm is raised once specific zones have many repairs, then specific zone is disabled.

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

Cause:

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 exceed 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. PR1152026 addresses proper parity error handling. PR1082932 Data Error in shared LMEM of LU/XL chip causes a MQ/XM chip wedge. PR1157173 auto-ttrace and Nexthop-tracing upon LMEM data errors may cause XMCHIP DRD Commands Sequence error.

 

Solution:

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.

    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.

This article is indexed in KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; tag EACHIPTSG XLCHIPTSG 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:

Note: KB Team - All changes to this article must be approved by the AI-Scripts Review team (pvs-scripts-review@juniper.net) before re-publishing.


AI-Scripts history:       (Updated by AI-Scripts team only)
 
Date KB Article Version AI-Scripts PR (optional) Notes
10/19/2017 1.2 1315327 Updated Syslog KB
       

 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search