The "Fast request is asserted for empty Queue" message reports a software issue in the EACHIP when the internal queue is empty, but still requests processing. 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 - Master Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] . .
When a "Fast request is asserted for empty Queue" event occurs, a message similar to the following is reported:
Jul 25 15:48:49.287 router0: %PFE-0: fpc8 Cmerror Op Set: XQSS(0)::FATAL ERROR!! from XQ-SS[0]: CPQW Fast request is asserted for empty Queue
Indications:
This is due to a transient software issue in the EACHIP. The EACHIP software state is usually reset internally to correct this condition.
{DIDYOUKNOWSERVICENOWTOKEN.EN_US} Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
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
Analyze the show command output.
In the 'show log messages', review the events that occurred at or just before the appearance of the "Fast request is asserted for empty Queue" message. Frequently, these events help identify the cause.
No RMA is required
Collect debugging information using KB31922 - shell script collecting data if packet forwarding at Packet Forwarding Engine is compromised [juniper.net]
FPC restart during a maintenance window should clear this error
Contact your technical support representative if this issue is seen repeatedly.
This article is indexed in KB31893 - primary Index of Articles for Troubleshooting PFE ASIC Syslog Events [juniper.net] ; tag EACHIPTSG
2019-10-01: Article reviewed for accuracy; no changes required