Support Support Downloads Knowledge Base Case Manager My Juniper 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

[MX] Error message 'FPC Major Errors - XM Chip Error code: 0x70297'

1

0

Article ID: KB35992 KB Last Updated: 28 Oct 2020Version: 2.0
Summary:

This article explains why a parity error with the error message  "FPC Major Errors - XM Chip Error code: 0x70297" is seen on MX Series routers and what should be done to resolve the error.

Note: 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.

Symptoms:

When a CPT parity error is detected on XMCHIP, the following alarm is generated:

root@MX> show chassis alarms no-forwarding

1 alarms currently active
Alarm time               Class  Description
2020-06-18 10:45:31 UTC  Major  FPC 0 Major Errors - XM Chip Error code: 0x70297

The message log displays the following:​

Jun 18 10:39:47 2020  MX : %PFE-3: fpc0 Cmerror Op Set: XMCHIP(1): XMCHIP(1): PT1: CPT parity error detected - Address 0xac0
Jun 18 10:39:48 2020  MX : %PFE-3: fpc0 Cmerror Op Set: XMCHIP(1): XMCHIP(1): PT1: CPT parity error detected - Address 0xac0
Jun 18 10:39:49 2020  MX rpd[14912]: %DAEMON-4-RPD_MPLS_INTF_MAX_LABELS_ERROR: Maximum labels exceeded - failed to stack additional label to nexthop on interface ae0.0 nhid: 1051527 fnh: 0x9d876d1c lspname: MX-to-kcm-pcor-20 label: Push 523134, Push 519586, Push 523133(top)
Jun 18 10:39:49 2020  MX : %PFE-3: fpc0 Cmerror Op Set: XMCHIP(1): XMCHIP(1): PT1: CPT parity error detected - Address 0xb00
Indications:
  • Traffic impact or PFE packet forwarding is permanently compromised if errors are seen repeatedly.

  • A major alarm will also be raised.

Cause:

CPT parity errors will occur because of PCT parity errors or from actual hardware faults. The PFE will be in a bad state potentially sending bad packets out after they occur. PCT parity errors will occur from either microcode accessing uninitialized PCT entries or from actual hardware faults. If PCT happens long after the XM was already in a bad state then its most likely due to accessing uninitialized PCT entries and it can be ignored. This is a transient hardware issue on XMCHIP.

Solution:

Perform the following steps to determine the cause and resolve the problem (if any).

  1. Collect the following 'show' command outputs to investigate further.​​

Capture the output to a file (in case you need to open a Technical Service Request). To do this, configure each SSH client/terminal emulator to log your session.

show log messages
show log chassisd
start shell pfe network <fpc#>
show nvram
show syslog messages
  1. Analyze the 'show' command output.

In the show log messages file, review the events that occurred at or just before the appearance of the 'fpc0 Cmerror Op Set: XMCHIP(1): XMCHIP(1): PT1: CPT parity error detected - Address 0xac0' message.

  1. After confirming the error message in the above file, restart the FPC during a maintenance window to fix the issue. Restarting the FPC is seen to resolve the issue in most cases.

request chassis fpc slot <slot number> restart
  1. If the issue is seen repeatedly even after restarting the FPC, open a Technical Service Request for further investigation and assistance. Traffic or permanent packet forwarding on the Packet Forwarding Engine (PFE) may be impacted if the errors are seen repeatedly and may require replacement of the FPC.

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 follow-on error messages. The subsequent collateral damage error messages can be ignored usually.

Modification History:
2020-10-28: Fixed typo in Solution item 1 (start shell network pfe <fpc#> To: start shell pfe network <fpc#>)
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