This article describes the error and how to resolve this alarm.

Below alarm would be raised:

root@host> show chassis alarms 

9 alarms currently active

Alarm time        Class Description

2024-02-29 10:22:30 UTC Major FPC 0 Major Errors

Below logs would be observed:

Feb 29 10:46:19.293 <hostname> fpc0 Error: /fpc/0/pfe/0/cm/0/Eth_Port_Error/0/ETH_CMERROR_MAJOR_2 (0x2d0003), scope: board, category: switch, severity: major, module: Eth Port Error, type: eth_host major error

Feb 29 10:46:19.293 <hostname> fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/Eth_Port_Error/0/ETH_CMERROR_MAJOR_2 (0x2d0003) in module: Eth Port Error with scope: board category: switch level: major

Feb 29 10:46:19.485 <hostname> fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/Eth_Port_Error/0/ETH_CMERROR_MAJOR_2 (0x2d0003) in module: Eth Port Error with scope: board category: switch level: major

This error/alarm can be due to eth2 (LCPU path between PE and CPU) having errors, therefore FPC was unable to connect to the routing engine.  These errors are transient in nature and should be healed/clear automatically.

In case alarm/error does not get clear, please restart FPC.

> request chassis fpc slot X offline     >>>> Check fpc status. It should be offline "show chassis fpc"
> request chassis fpc slot X online