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

[MX] Multiple Alarms: MQ Chip Error code: 0x3000

0

0

Article ID: KB35989 KB Last Updated: 10 Nov 2021Version: 2.0
Summary:

This article explains the meaning of the following multiple alarms seen on the device and indicates if any actions need to be taken:

user@router> show chassis alarms no-forwarding
2 alarms currently active
Alarm time               Class  Description
2020-06-18 01:50:52 UTC  Major  FPC 2 Major Errors - MQ Chip Error code: 0x3000b
2020-06-18 01:50:51 UTC  Minor  FPC 2 Minor Errors - MQ Chip Error code: 0x3000a
Symptoms:

The following syslog messages are seen on the device for the FPC:

fpc2 MQCHIP(1) DDRIF Chksum Cnts  Current 12, Total 12
chassisd[13820]: <FPC 2> ASIC Error detected errorno 0x0003000a
alarmd[15197]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 2 Minor Errors - MQ Chip Error code: 0x3000a
craftd[13833]:  Minor alarm set, FPC 2 Minor Errors - MQ Chip Error code: 0x3000a
fpc2 MQCHIP(1) FO half 0 packet error
fpc2 Cmerror: Draining ASIC error message queue
fpc2 cmerror_process_queue: module = MQ Chip(1)
Cause:

This error indicates that there is a checksum error in the DDRIF packet memory. The MPC2EQ in FPC0 hit with DDRIF Checksum Errors. The cause may be due to a transient software or hardware issue.

Solution:

To resolve the above error, perform the following steps:

  1. Collect the following 'show' command outputs to investigate further.

    show log messages
    show log chassisd
    start shell network pfe <fpc#>
    show nvram
    show syslog messages
    
  2. Analyze the 'show' command outputs at the time the alarm was triggered.

    1. A single occurrence of this checksum error in the log indicates a transient hardware issue. If it is a single occurrence, it can be cleared manually by using the following command in operational mode. This command is available starting in Junos OS 16.1R4-S2, 16.1R5, 16.2R2, 17.1R2, and 17.2R1 as a hidden command. It is unhidden in Junos OS 18.2R1 and higher.

      user@mx> clear chassis fpc errors fpc-slot fpc-slot (all | error-id error-id)

      Note: It is suggested to use all instead of a particular error-id to avoid the complicated error-id format, which is represented as a Uniform Resource Identifier (URI). The default disable-PFE actions upon Major Alarm are invoked to protect further operational impact.

    2. If the error occurs multiple times or even after the above command, take the FPC offline and bring it online again or restart the FPC during a maintenance window.

      user@mx> request chassis fpc slot <slot number> offline

      Wait for a few minutes.

      user@mx> request chassis fpc slot <slot number> online

      OR

      user@mx> request chassis fpc slot <slot number> restart

If the alarm does not clear after performing the above steps, contact JTAC Support for further investigation.
Note: This article is indexed in KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events tag MQCHIPTSG

Modification History:
2021-11-10 Move the KB to public access
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