Description

The "KMB[.] parity error or KMA[.] parity error " message is caused due to 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 "KMB[.] parity error or KMA[.] parity error " event occurs, messages similar of the following are reported:

XLCHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 XL[0:0]_PPE 2 Errors KMA[0] parity error
Sep 7 17:11:38.269 router : %PFE-3: fpc8 XL[0:0]_PPE 2 Errors KMB[1] parity error

EACHIP:

Sep 7 17:11:38.269 router : %PFE-3: fpc8 EA[0:0]_PPE 0 Errors KMA[1] parity error
Sep 7 17:11:38.269 router : %PFE-3: fpc8 EA[0:0]_PPE 0 Errors KMB[0] parity error

Indications:

  • No service impact

  • This error is a transient hardware problem

  • The parity error will be automatically corrected

 

Solution

This error is caused by a transient hardware error. Constant memory errors are parity protected and will be recovered automatically from shadow space.

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 "KMB[.] parity error or KMA[.] parity error" message. Frequently these events help identify the cause.

  • No RMA is required for couple incidents

  • Contact your technical support representative if this error is reported many times to RMA the FPC.

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.