Support Support Downloads Knowledge Base Case Manager My Juniper 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

[MX] LUCHIP(5) PPE_11 Errors sync xtxn error

0

0

Article ID: KB35690 KB Last Updated: 29 May 2020Version: 1.0
Summary:

This article discusses the 'LUCHIP(5) PPE_11 Errors sync xtxn error' and the recommended action to take.

Symptoms:

The logs below were seen for an FPC, and there was no service impact reported:

fpc9 LUCHIP(5) IDMEM Parity error in Bank 0, Count 1, IDMEM Bank 0 Offset 0x000033ff IDMEM[0x00cfe3] Rd 0xda40300689c00183.
fpc9 LUCHIP(5) PPE_2 Errors sync xtxn error
fpc9 LUCHIP(5) PPE_4 Errors sync xtxn error
fpc9 LUCHIP(5) PPE_6 Errors sync xtxn error
fpc9 LUCHIP(5) PPE_7 Errors sync xtxn error
fpc9 LUCHIP(5) IDMEM Parity error in Bank 0, Count 12, IDMEM Bank 0 Offset 0x000033ff IDMEM[0x00cfe3] Rd 0xda40300689c00183.

FPC 9            REV 33   750-037358   CAFM5862          MPC4E 3D 32XGE
Cause:

When software detects IDMEM parity errors, software has the capability to correct the memory location. The syslog entry confirms that the error was detected and corrected. The xtxn errors are there because of illegal FPC memory addressing and there is no operation impact because of this. The cause is due to a transient memory error detected in the LUCHIP, so this is not hardware failure.

Solution:
  1. Check for any physical interface errors on the FPC:

    show interface <interface_number> extensive
  2. Check for any fabric / fpc drops:

    show pfe statistics error
    show pfe statistics traffic fpc <slot_number>
    show chassis fabric fpcs

  3. Check the FPC status

  4. Check if there is any other "Uncorrectable ECC errors" message seen with the XTXN errors. If yes, a restart of FPC should clear the errors.

  5. If the Parity error messages stop getting logged on the device, it is recommended to monitor the device for a while. If the parity error do not stop, isolate the issue by referring to KB19882 - Debugging MX MPC Erroneous IDMEM Parity errors.

  6. If you still see the issue, proceed with rebooting/reseating the line-card.

    request chassis fpc offline slot <slot-no>
    request chassis fpc online slot <slot-no>
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