Description

The " Parity error for DRD memory" message reports a transient hardware error.


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 " Parity error for DRD memory"  event occurs, a message similar to the following is reported:
Feb 7 14:51:02 router0 fpc4 XMCHIP(0):XMCHIP(0): DRD: Protect 1: Parity error for DRD memory 7

Indications:

  • Single occurrence of syslog, not seen with other events, indicates a one time hardware error. Multiple continuous occurrences indicate persistent underlying issues.
  • No permanent impact of packet forwarding
  • Alarm will be raised.
  • For each error entry, few data traffic packet drops could be seen, but the losses aren’t persistent and traffic should resume at 100% as before.

 

Solution

The cause is due to a parity error detected in internal memory due to a transient hardware error.

 

{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 " Parity error for DRD memory " message. Frequently these events help identify the cause.

    1. No RMA required.      

    2. FPC restart during a maintenance window should clear this error.

    3. With the single occurrence, the alarm can be cleared using command command, clear chassis fpc errors fpc-slot <x> all

    4. The multiple continuous occurrences of errors require FPC restart during maintenance window to clear the alarms.

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