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.* FI: Cell underflow at the state stage (Cell behind reorder window) - Stream .* Count .*



Article ID: KB31720 KB Last Updated: 12 Oct 2021Version: 3.0

The "Cell underflow at the state stage" message reports a cell arriving late at the egress PFE

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 "Cell underflow at the state stage" event occurs, a message similar to the following is reported:

Jul 25 16:14:50.881 router0: %PFE-3: fpc8 MQSS(0): FI: Cell underflow at the state stage (Cell behind reorder window) - Stream 0, Count 0


  • Service impact depends on number of cells dropped

  • counter value presents the number of 64B cell drops

  • With the fix for PR1184761, a minor alarm will be raised if the rate is higher than 100/second



The is due to the fabric cells arriving late on the egress PFE behind the reorder window.



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 "Cell underflow at the state stage" message. Frequently, these events help identify the cause.

  • No RMA is required

  • It could be triggered  due to fabric congestion because of some specific traffic flow characteristics on the affected PFE

  • ‚ÄčIf there are excessive and sustained out of order events due to fabric congestion it could expose a possible fabric stream wedge which is solved in PR1276301

  • Contact your technical support representative if the issue is persistent.

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