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 addr error

0

0

Article ID: KB32163 KB Last Updated: 11 Oct 2021Version: 3.0
Summary:

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

.

Symptoms:

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.



 
Cause:

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

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

 

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