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.*DRD.*CMD FSM state error



Article ID: KB32352 KB Last Updated: 11 Oct 2021Version: 3.0

The "CMD FSM state error" message reports that the Forwarding State Machine of the reorder queue received an unexpected value.

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 "CMD FSM state error" event occurs, a message similar to the following is reported:
Note: Either prior or post CMD FSM state error, you will also see a "CMD reorder ID error" error message.

Nov 30 14:15:19.464 atlas-re0 : %PFE-3: fpc8 MQSS(0): DRD: RORD1: CMD reorder ID error - Command 13, Reorder ID 0, QID 30720
Nov 30 14:15:19.464 atlas-re0 : %PFE-7: fpc8 Cmerror: Draining ASIC error message queue
Nov 30 14:15:19.464 atlas-re0 : %PFE-7: fpc8 cmerror_process_queue: module = MQSS(0)
Nov 30 14:15:19.464 atlas-re0 : %PFE-7: fpc8 Cmerror: processing the task op_type 1 for level 1 level_count 0 occur_count 0 clear_count 0 level_threshold 1 level_action 0x4 item errid 2229195 item_threshold 1 item_count 0 item_sub_err_state 0 sub_item errid 0 sub_item_state 0 item_times
Nov 30 14:15:19.464 atlas-re0 : %PFE-7: fpc8 Cmerror: Level 1 count increment 1 occur_count 1 clear_count 0
Nov 30 14:15:19.464 atlas-re0 : %PFE-6: fpc8 Error: /fpc/8/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_INT_REG_CMD_FSM_STATE_ERR (0x2203cb), severity: major, module: MQSS(0), type: Description for MQSS_CMERROR_DRD_RORD_ENG_INT_REG_CMD_FSM_STATE_ERR
Nov 30 14:15:19.464 atlas-re0 : %PFE-7: fpc8 Cmerror: Level 1 count 1 (occur_count 1 clear_count 0)crossed threshold 1 action 0x4
Nov 30 14:15:19.464 atlas-re0 : %PFE-7: fpc8 cmerror_take_action_helper: performing action 4 for level 1 err_id /fpc/8/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_DRD_RORD_ENG_INT_REG_CMD_FSM_STATE_ERR (0x2203cb) module id 24
Nov 30 14:15:19.464 atlas-re0 : %PFE-3: fpc8 Cmerror Op Set: MQSS(0): MQSS(0): DRD: RORD1: CMD FSM state error - Command 13, Reorder ID 0, QID 0, FSM State 5



This indicates the lookup microcode within LUSS is sending an incorrect command parcel to the MQSS Center Chip.


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 "CMD FSM state error" message. Frequently these events help identify the cause.

  • No RMA is required

  • With the single occurrence, the alarm can be cleared using command:

    • ‚Äčclear chassis fpc errors fpc-slot <x> all

    • ‚ÄčNote: This command is available in Junos OS 16.1R4-S2, 16.1R5, 16.2R2, 17.1R2, and 17.2R1 or higher. 

  • Contact your technical support representative if this event is seen repeatedly

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.


Modification History:

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
1/19/2018 1.0 1334932 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