Description

The "gumem[.].par_protect" message is caused by a transient hardware issue which is automatically repaired.

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 "gumem[.].par_protect" event occurs messages similar of the following are reported:

XLCHIP:

Sep 7 16:40:54.248 router : %PFE-3: fpc10 XL[0:0].gumem[0].par_protect CACHE SRAM BANK 3 LO err_addr NA (mult 0xf0f).
Sep 7 16:40:54.360 router : %PFE-6: fpc10 XL[0:0].gumem[0].par_protect CACHE SRAM BANK 3 LO Error @ 0x7c is being repaired

EACHIP:

Sep 7 16:37:31.546 router : %PFE-3: fpc8 EA[0:0].gumem[3].par_protect CACHE SRAM BANK 7 HI err_addr NA (mult 0x3).
Sep 7 16:37:31.548 router : %PFE-6: fpc8 EA[0:0].gumem[3].par_protect CACHE SRAM BANK 7 HI Error @ 0xa is being repaired


Indications:

  • No service impact

  • This error is a transient hardware problem

  • The parity error will be automatically corrected

 

Solution

Global microcode space is parity protected. This is caused by a transient hardware issue and is repaired by the software automatically.

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
    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 "gumem[.].par_protect" message. Frequently these events help identify the cause.

  • No RMA is required for a couple of incidents

  • Contact your technical support representative if this error is reported many times

This article is indexed in  KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; tag EACHIPTSG XLCHIPTSG

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.