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.*Parity error detected for bank.*of CP table



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

The "Parity error detected for bank .. of CP table" message reports a hardware parity error detected in the EACHIP Fabric input block.

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 "Parity error detected for bank .. of CP table" event occurs, messages similar to the following is reported:

Jul 31 07:26:23 router-0 : %PFE-3: fpc10 MQSS(0):MQSS(0): FI: Protect 2: Parity error detected for bank 28 of CP table - data32_log_err 0x10000000, data32_log_address 0x13a


  • Single occurrence of syslog and not seen with other events indicate a one time transient hardware error with no operational impact

  • Multiple continuous occurrences indicate persistent underlying issues and possibly service impact

  • Alarm will be raised



This is due to a transient hardware SRAM error within EACHIP Fabric input block.


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 "Parity error detected for bank .. of CP table" 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 issue is seen repeatedly after FPC restart.

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