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: Errors async xtxn error

0

0

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

The "Errors sync axtxn error" message is likely caused by a software related error condition accessing illegal memory space.

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 "Errors async xtxn error" event occurs, messages similar to the following are reported and are never on its own:

EACHIP:

Jun 2 17:43:23 router-re0 fpc1 EA[1:0]_PPE 48 Errors async xtxn error

XLCHIP:

Nov 6 20:56:00 router-re0 fpc16 XL[0:0]_PPE 0 Errors async xtxn error

LUCHIP:

Nov 4 20:36:00 router-re0 fpc5 LUCHIP(0) PPE 0 Errors async xtxn error​

Indications:

  • Typically seen in combination with other error events

  • Affected packet will be dropped

  • Operational impact depends on frequency of such events

 

Cause:

This can be a software error when accessing illegal memory space. Lookup of these packets are terminated. Trap and trace information is needed to debug further. Most of these events are surrounded with other syslog messages and data points.

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 "Errors async xtxn 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/16/2017 1.2 1311793 Finish Syslog KB
       

 
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