Description

This article describes steps to perform to resolve error logs PECHIP_CMERROR_FO_INT_REG_PKTCRC (0x210616).

Symptoms

Below chassis alarm would be raised.

root@host> show chassis alarms no-forwarding

1 alarms currently active

Alarm time              Class Description

2023-09-13 23:33:17 PDT Major FPC 0 Major Errors

 

Below logs would be observed:

Sep 13 23:33:17.237 hostname fpc0 Error: /fpc/0/pfe/0/cm/0/PE_Chip/7/PECHIP_CMERROR_FO_INT_REG_PKTCRC (0x210616), scope: pfe, category: io, severity: major, module: PE Chip, type: Description for PECHIP_CMERROR_FO_INT_REG_PKTCRC

Sep 13 23:33:17.276 hostname fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/PE_Chip/7/PECHIP_CMERROR_FO_INT_REG_PKTCRC (0x210616) in module: PE Chip with scope: pfe category: io level: major

Sep 13 23:33:17.302 hostname inetd[16123]: Number of tftp connections at max limit (1)

Sep 13 23:33:17.404 hostname alarmd[16099]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 0 Major Errors

Sep 13 23:33:17.404 hostname craftd[16110]: Receive FX craftd set alarm message: color: 1 class: 100 object: 104 slot: 0 silent: 0 short_reason=FPC 0 Major Errors long_reason=FPC 0 Major Errors id=150995048 reason=150994944

Sep 13 23:33:17.404 hostname craftd[16110]: Major alarm set, FPC 0 Major Errors

Sep 13 23:33:17.409 hostname fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/PE_Chip/7/PECHIP_CMERROR_FO_INT_REG_PKTCRC (0x210616) in module: PE Chip with scope: pfe category: io level: major

Sep 13 23:33:17.409 hostname fpc0 Cmerror Op Set: PE Chip: PE7[7]: FO payload CRC error threshold reached

Solution

The first time this occurs, the recommendation is to reset the line card in a maintenance window


Kindly restart the affected FPC during the maintenance window to clear the alarm.

> request chassis fpc slot X offline

[In case you choose to offline FPC card. Check fpc status. It should be offline "show chassis fpc"]

> request chassis fpc slot X online

[Use Online command in case you choose offline option to restart the card.]
 

When the line card reboots, the power-on BIST will check the health of the board and automatically attempt to correct any issues.  This will almost always recover the affected ASIC components.



If restart doesn't help in resolving the issue, the affected card needs to be replaced.
 

Please open a case with Juniper Technical support JTAC Support  for further investigation.

Modification History

Version 1