Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Syslog message: MQSS.*DRD.*Protect.*Parity error corrected for alloc state memory .* data32_log_err .* data32_log_address

0

0

Article ID: KB31719 KB Last Updated: 12 Oct 2021Version: 2.0
Summary:

The "MQSS alloc state memory" message reports a parity error correction done in the EACHIP state memory.

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 - Index of Articles for Troubleshooting PFE ASIC Syslog Events.

.

Symptoms:

When a "MQSS alloc state memory" event occurs, a message similar to the following is reported:

Jul 25 16:48:31.809 router0 : %PFE-3: fpc8 Cmerror Op Set: MQSS(0): MQSS(0): DRD: Protect 1: Parity error corrected for alloc state memory 0_A - data32_log_err 0x0, data32_log_address 0x992

Indications:

  • Single occurrence of the error, not seen with other events, will be automatically corrected by ECC. Multiple continuous occurrences indicate persistent underlying issues.

  • No traffic/functional impact.

  • Alarm will be raised​

 

Cause:

This is due to a software micro-code error or transient hardware error

Solution:



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 "MQSS alloc state memory" message. Frequently, these events help identify the cause.

    • No RMA is required.

    • With a single occurrence, the alarm can be cleared using the following command:

      clear chassis fpc errors fpc-slot <x> all

      Note: This command is available in Junos OS 16.1R4-S2, 16.1R5, 16.2R2, 17.1R2, 17.2R1 and higher.
    • For multiple continuous occurrences of errors, perform FPC restart during a maintenance window.

    • Collect debug information with the script in KB31922 - shell script collecting data if packet forwarding at Packet Forwarding Engine is compromised 

    • Contact your technical support representative if this issue still exist after FPC restart

This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; tag EACHIPTSG

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.

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search