This KB explains why we see PCIe error along with FPC hard errors and how to recover the same.

• We can see FPC 0 has hardware errors reported on it:

user@router> show chassis alarms no-forwarding
1 alarms currently active
Alarm time        Class Description
2025-07-11 15:23:46 BST Major FPC 0 Hard errors

• Logs suggests there FPC0 reported PCIe bus error before it lost IPC connection with RE0.

Message Logs:

Aug 16 13:47:13 2026  router-re0-fpc0 kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
Aug 16 13:47:14 2026  router-re0-fpc0 kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
Aug 16 13:47:23 2026  router-re0 chassisd[12861]: CHASSISD_IPC_CONNECTION_DROPPED: Dropped IPC connection for FPC 0
Aug 16 14:12:42 2026  router-re0 chassisd[12861]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Restarting unresponsive board
Aug 16 14:23:05 2026  router-re0 chassisd[12861]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Restarting unresponsive board
Aug 16 14:33:22 2026  router-re0 chassisd[12861]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Restarting unresponsive board

Chassisd Logs

Aug 16 13:47:13  pic_get_port_infop: port count value from hwdb 16 for fpc 0 pic 1
Aug 16 13:47:13  pic_optics_inform_ifd_optics_transportd: Transportd Msg Handled for et-0/1/5 optics 178
Aug 16 13:47:23  rcv: ch_ipc_dispatch() ETIMEDOUT TCP/IP pipe ipc read for args 0xae51fc0 pipe 0xa0a6580, fru FPC 0 errno 60
Aug 16 13:47:23  rcv: ch_ipc_dispatch() ipc pipe read error for args 0xae51fc0 pipe 0xa0a6580, fru FPC 0 subfru 0 errno 0
Aug 16 13:47:23  ch_ipc_dispatch: fru FPC offline_reason = Reconnect
Aug 16 13:47:23  ch_connection_shutdown: Destroying the IPC pipe
Aug 16 13:47:23  fpc_disconnect_generic: fpc 0 slc 0 state Online cargs 0xae51fc0 clean_shutdown 0, offline_reason=Reconnect
Aug 16 13:47:23  -- FPC 0, last request 0, state Online
Aug 16 13:47:23  CHASSISD_IPC_CONNECTION_DROPPED: Dropped IPC connection for FPC 0
Aug 16 13:47:23  FPC0 fpc_tvp_chassis_disconnect_cleanup.
Aug 16 13:47:23  CHASSISD_IFDEV_DETACH_FPC: ifdev_detach_fpc(0)
Aug 16 14:12:42  CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Restarting unresponsive board
Aug 16 14:12:43  FPC#0 - power off reason: Restarting unresponsive board
Aug 16 14:12:43  FPC#0 - power off reason: Restarting unresponsive board

• Above logs indicating access issue with LMIC in slot 1, which requires a power cycle.
• It is recommended to recover by power cycling the affected device. This can be done by physically removing power, or by using the CLI command below.

user@router> request vmhost power-cycle-cb