CHASSISD_FASIC_PIO_READ_ERROR

The CHASSISD_FASIC_PIO_READ_ERROR message is reported into the system message file whenever a read error is detected by the chassisd process on a fabric link.

The problem related to this syslog message is described in the following sections:

The CHASSISD_FASIC_PIO_READ_ERROR message is logged whenever a read error is detected by the chassisd process on a fabric link.

Below are examples of the error messages. The messages will vary slightly based on the routing platform. These messages are often accompanied by GBUS errors. Fabric planes may be taken offline due to these errors.

These errors may be due to hardware failure, transient issues on the fabric plane, or chassis restart operations performed while Graceful Routing Engine Switchover (GRES) is enabled and a Control Board (CB) is offline.

Forcibly removing an active CB can also cause these errors.

They may also be caused by rebooting both Routing Engines (REs) in a dual RE system while GRES is enabled.

Determine if GRES is enabled on the system. If it is, review the output of show log messages and show log chassisd to determine if any chassis restart operations were performed while one of the CBs was offline.

Determine if an active CB was removed.

Review the output of show log messages and show log chassisd to determine how often the errors are occurring and if they stopped after fabric planes were taken offline.

Review the output of show chassis fabric xxx commands to determine the status of the fabric planes and links.

If only a few errors were logged and have since stopped, they are likely due to transient issues on the fabric.

If all of the links for a Packet Forwarding Engine (PFE) or plane are in an error state, the errors are likely due to a hardware failure.

If GRES is enabled and chassis restart operations were performed or if both REs were rebooted together, these messages are expected.

If an active CB was forcibly removed, the messages are also expected.

If the errors were due to a transient issue on the fabric, monitor the router for a recurrence of the errors.

If the errors stopped when fabric planes were taken offline, reseat the Control Board associated with the plane and if needed, bring the plane back online.

If the errors return after the plane is brought back online, or if there is indications of a hardware failure, open a case with your technical support representative.

About the author

Prasanna

Leave a Comment