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: XMCHIP.*LI.*Received a parcel from the HSL2 interface with EOPE



Article ID: KB31733 KB Last Updated: 06 Oct 2021Version: 3.0

The "LI Received a parcel from the HSL2 interface" message reports a transient hardware or LU/XL software issue.

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.



When a "LI Received a parcel from the HSL2 interface" event occurs, a message similar to the following is reported:

Jan 23 09:21:55 router0 : %PFE-3: fpc11 XMCHIP(1): LI0: Received a parcel from the HSL2 interface with EOPE




It is a transient hardware or LUCHIP/XLCHIP ucode software defect. The parcels (i.e. packet going through route lookup) from LUCHIP/XLCHIP to XMCHIP is marked with the Error Flag.

EOPE means End of Packet with Error. The HSL2 retransmission (Reliability Transmission) is enabled for the links between LUCHIP/XLCHIP and XMCHIP.  This is due to a transient HW error at the lookup chip. We would have a corresponding event in LUCHIP or XLCHIP section. Check for HSL2 CRC, LMEM data errors or parity errors in XLCHIP unload block.



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

  2. Analyze the show command output.

    In the 'show log messages', review the events that occurred at or just before the appearance of the "LI Received a parcel from the HSL2 interface" message. Frequently, these events help identify the cause.

  • RMA is required only if high rate of HSL2 CRC errors are seen between XMCHIP and XLCHIP/LUCHIP. Check CRC errors using 'show pfe statistics error' or check for CRC errors in the pfe.debug file in /var/tmp/

  • Contact your technical support representative for more analysis.

  • Check if HSL2 errors are seen between the LU/XL and XM HSL2 links

    • If Yes, this is an indication that it is either a HW transient error or bad HW

    • In this case, restart the MPC and monitor if the error is repeatedly seen

    • If Yes, then the FPC should be RMA’ed

  • If there is no HSL2 errors for LU/XL and XM links, then it is possible due to many LMEM data errors or XLCHIP unload block parity errors

This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; tag XMCHIPTSG

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:
2019-10-14: Article reviewed for accuracy; no changes required.

Related Links

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