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 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] .

.

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

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.

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

• No RMA is required

• Look for other events

• Collect trap ttrace information 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 for further guidance

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.