CHASSISD_FASIC_HSL_LINK_ERROR

On MX routers, this article addresses how to detect CRC errors on High Speed Link (HSL) interconnection between Dense Port Concentrator (DPC)’s Packet Forwarding Engine (PFE) or Flexible Port Concentrator (FPC), midplane connector, and a Switch Control Board (SCB – MX series) or Switch Interface Boards (SIB – T Series) or Forwarding Engine Board (FEB – M120).

The

means the chassis process (chassisd) detected an error for the indicated high speed link (HSL) for the indicated F chip on the indicated Control Board (CB).

SYMPTOMS:

When a

event occurs, a message similar to the following is reported:

Depending on the severity and frequency of errors, a forwarding plane may be brought in check state or even be off-lined.

CHASSISD_FASIC_HSL_LINK_ERROR messages are reported when there is a link failure due to packet corruption. This is usually caused by a hardware error, and may or may not indicate faulty hardware. To determine which component is causing the link failure, check outputs from the forwarding plane, fabric chips, controls boards and FPCs.

To determine what part is causing the issue, first look at the

Note: For T-series routers, change “fpcs” to “sibs”; and for a M120, substitute “feb” for “fpcs”) output.

In the following show chassis fabric fpcs output, all PFE planes show a link error. This is likely a DPC issue.

In the following show chassis fabric fpcs output, there is an error on one plane for multiple PFEs. This is likely SCB issue.

Then review the output of show chassis fabric plane. In the following example output, one DPC showing link errors on multiple planes. This is likely an issue with the DPC.

In the following show chassis fabric plane, there are Link errors showing up on one plane for all DPCs. This likely an issue with the SCB.

In the following show chassis fabric plane, there are Link errors on one DPC and one plane. Further troubleshooting is needed to determine the part causing the errors.

For further troubleshooting, examine the following output to help determine the cause of this message:

Look for any related events that occurred at or just before the CHASSISD_FASIC_HSL_LINK_ERROR message in the log messages and log chassisd outputs.

Perform the following steps:

1. Follow the instructions under “Confirm Causes”.

2. During a maintenance window, as it will impact transit traffic, try the following:

  • In cases where DPC or FPC is determined to be the culprit, reseat the DPC or FPC.
  • In cases where SCB, SIB, or FEB is determined to be the culprit, reseat the SCB, SIB, or FEB.
  • if re-seating the component does not resolve the issue, or if the errors continually return shortly after re-seating, open a case with your technical support representative to investigate the issue further.

3. In cases where the part cannot be determined (for example, there is only one link error, or the errors exist across multiple dpcs/fpcs AND multiple planes), open a case with your technical support representative to investigate the issue further. Be warned that troubleshooting for such issues will likely include several hardware swaps, which will impact traffic on production routers.

About the author

Prasanna

Leave a Comment