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.*FO: Request timeout error - Number of timeouts .*, RC select .*, Stream



Article ID: KB31717 KB Last Updated: 12 Oct 2021Version: 2.0

The "FO: Request timeout error" message reports a transient hardware issue in the EACHIP.

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 "FO: Request timeout error" event occurs, a message similar to the following is reported:

Jul 25 16:12:23.535 router0: %PFE-3: fpc8 MQSS(0): FO: Request timeout error - Number of timeouts 0, RC select 3, Stream 160


  • No traffic impact on single occurrences
  • If errors are seen repeatedly there might be traffic impacted



This is due to another PFE / FPC going down or not responding, or packets are dropped from the reporting PFE through the fabric to the destination PFE.  The EACHIP on this FPC is only reporting the issue, and is not the source of the problem.


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 "FO: Request timeout error" message. Frequently, these events help identify the cause.

  • Fabric resiliency will automatically recover from such condition and take corrective actions
  • Contact your technical support representative if this event is reported repeatedly to isolate the fault area

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