Description

The "LI Received a parcel with more than 512B" 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 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] .

.

Symptoms

When a "LI Received a parcel with more than 512B" event occurs, a message similar to the following is reported:

Feb 19 09:28:02 router0 fpc1 XMCHIP(0): XMCHIP(0): LI1: Received a parcel with more than 512B accompanying data

Indications:

 

Solution

In most cases this is caused by a LUCHIP/XLCHIP ucode software defect. The size of the parcels from LUCHIP/XLCHIP to XM is incorrect. Such a software error could also be triggered when a corrupted fabric parcel is processed. The HSL2 retransmission (RT) is enabled for the links between LUCHIP/XLCHIP and XMCHIP. There was a software bug for MPC6E linecard with this functionality, and it is addressed in PR1161194 .  
 

 

{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 "LI Received a parcel with more than 512B" message. Frequently these events help identify the cause.

    • An RMA is required only if a high rate of HSL2 CRC errors are reported. Check the CRC errors with the command 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.
    • If there are no HSL2 errors for LU/XL and XM links, then it is possible that this is a LU/XL ucode software bug. Check for LU/XL errors (PPE timeouts).
 

This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; 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.