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

[MX] Syslog message - "464 TPCI PIO Read errors seen in last second"

0

0

Article ID: KB37331 KB Last Updated: 16 Aug 2021Version: 1.0
Summary:

This article explains the meaning of the syslog message "464 TPCI PIO Read errors seen in last second" that is seen on MX routers and what users must do when they encounter this error.

Symptoms:

The Routing Engine continuously logs the following messages:

​Jul 17 17:15:03.657 2021  Test : %PFE-3: fpc2 cc_mic_periodic_raw: CC_MIC(2/2) 464 TPCI PIO Read errors seen in last second
Jul 17 17:15:03.861 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 PIO Active, Timestamp 127585408743 msec.
Jul 17 17:15:03.958 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 (0x0006)                         Status : 0x00004010
Jul 17 17:15:04.075 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 (0x004a)                  Device status : 0x0000000c
Jul 17 17:15:04.176 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 (0x0052)                    Link status : 0x00001811
Jul 17 17:15:04.286 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 (0x0104)     Uncorrectable error status : 0x00100000
Jul 17 17:15:04.395 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 (0x0118)       Advanced error cap & ctl : 0x000001f4
Jul 17 17:15:04.504 2021  Test : %PFE-3: fpc2 PCI ERROR: 2:2:11:0 (0x011c)                   Header log 0 : 0x40008001
Solution:

The error indicates a permanent or temporary PCI block error. A PIO error message is reported in the system message file whenever a memory integrity check is performed by the LU driver and encounters an error.

If this log appears only once, it is most likely that this is a transient issue. In this case, reboot the affected MIC and monitor. Ideally, in the case of a transient issue, a reboot will re-initiate all functions and processes.

If the log continues to appear after a reboot, it is suggested to re-seat/replace the MIC. If the log persists even after replacement, contact Support for additional assistance.

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