The "Errors sync xtxn error" message is likely to be caused due to Hardware related error condition since synchronous transaction to external device is not possible

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 sync xtxn error" event occurs messages similar of 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 sync xtxn error

XLCHIP:

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

LUCHIP:

Aug 6 20:56:00 router-re0 fpc16 LUCHIP(0) PPE 0 Errors sync xtxn error​

Indications:

• Typically seen in combination with other error events

• The affected packet will be dropped

• Operational impact depends on frequency of such events

This is likely to be caused by hardware related error once synchronous transaction to external device is not possible. This will invoke the trap handler and affected packet getting dropped along with a ttrace is getting reported. Other events need to be examined to understand the root cause trigger.

{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 sync 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

2017-10-11:  No technical changes. Updated article to link to AI-Script.