Description

The "WAN parcel timeout error" message reports a hardware or 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 "WAN parcel timeout error" event occurs, a message similar to the following is reported:

Feb 13 14:25:00 router0 fpc5 XMCHIP(2): DRD0: WAN parcel timeout error - Valid 1, Reorder ID 687 XMCHIP(2): PT table entries from PT entry to RID table: 0192 2042 2304 2728

Indications:

In most cases, WAN side healthiness is also checked with host loopback probes. Upon permanent impact of packet forwarding condition, an additional alarm of host-loopback wedge will get reported " Host Loopback:HOST LOOPBACK WEDGE DETECTED IN PATH ID <x> "   and persistent service impact is seen. 

 

Solution

This might be caused by hardware or software.
A high rate of HSL2 (High Speed Link) CRC errors could be a hardware error. Further analysis will be needed to determine if this is the case.

The following KB entries might be relevant:
KB31602 - Syslog message: XMCHIP.*DRD.*Command sequence error [juniper.net]
KB32168 - Syslog message: HOST LOOPBACK WEDGE DETECTED [juniper.net]  

{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 "WAN parcel timeout error" message. Frequently these events help identify the cause.

    1. No RMA required.
    2. JunOS Enhancements within 15.1F6-S8, 16.1R7, 17.1R3, 17.2R2, 17.3R1 and 17.4 and higher do perform automatic recovery.
    3. With the fix for PR/1186421 , major alarms will default to take the disable-pfe action. Without the PR fix, the generic pfe-disable event script will detect the wedge condition that happens as a result of this event and invoke the pfe-disable action; see KB31867 - Generic pfe-disable Event Script [juniper.net] . A FPC reboot at a later time is needed to bring the PFE back into service.
    4. Restart the FPC to recover.
    5. Contact your technical support representative if the issue is seen after a FPC restart. 
 

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: added JunOS Enhancements which performs automatic recovery upon DRD timeout.