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: XMCHIP.*CPQ1.*Queue underrun indication



Article ID: KB32005 KB Last Updated: 06 Oct 2021Version: 5.0

The "Queue underrun indication" reports an overflow of fabric tokens.

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.


When a "CPQ1 Queue underrun indication" event occurs, a message similar to the following is reported:

Mar 17 10:50:22  router fpc11 XMCHIP(0): CPQ1: Queue unrderrun indication - Queue 14


  • The message will be logged continuously

  • Permanent impact for all traffic into the fabric on the reporting PFE

  • Packet drops are counted as fabric drop reported with command show pfe statistics traffic


This is a transient hardware or software defect.



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

  2. Analyze the show command output.

    In the 'show log messages', review the events that occurred at or just before the appearance of the "CPQ1 Queue underrun indiction" message. Frequently these events help identify the cause.

  • No RMA required.  

  • Junos OS has been enhanced within PR1265385 to report such condition and raise a Major CMERROR Alarm.

  • The generic pfe-disable event script will detect a permanent impact on packet forwarding condition that happens as a result of this event and invoke the pfe-disable action”.  KB31867 - [Junos] Generic pfe-disable event script

  • Contact your technical support representative if the issue is seen after FPC restart  

This article is indexed in KB31893 - Primary Index of Articles for Troubleshooting PFE ASIC Syslog Events; 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.

Note: KB Team - All changes to this article must be approved by the AI-Scripts Review team ( before re-publishing.

AI-Scripts history:       (Updated by AI-Scripts team only)
Date KB Article Version AI-Scripts PR (optional) Notes
9/15/2017 1.0 1299045 New Syslog KB

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