After disabling the CB (control board) and re-enabling it again, several FPC's went offline due to self-ping failure. The CB offline/online was performed to recover the routing engine (RE) inserted into this CB.

The CB1 was offlined/onlined was done in an attempt to recover the RE1 which was offline by that time. After the CB1 was offlined/onlined:

request chassis cb slot 1 offline
request chassis cb slot 1 online

Several FPC's went offline due to self-ping failure:
 

Feb 25 23:11:43.529 2024 router-re0 : %PFE-3: fpc2 CMTFPC: Reporting self ping blackhole for FPC 2 PFE 0 tx 858589689 rx 858588918 last-rx 858588918

Feb 25 23:11:43.533 2024 router-re0 : %PFE-3: fpc2 CMTFPC: Reporting self ping blackhole for FPC 2 PFE 1 tx 858589670 rx 858588900 last-rx 858588900

Feb 25 23:11:44.226 2024 router-re0 : %PFE-5: fpc2 Error: /fpc/2/pfe/0/cm/0/CM[0]/0/CM_CMERROR_FABRIC_SELFPING (0x2e0006), scope: board, category: functional, severity: major, module: CM[0], type: MPC fabric selfping blackhole

Feb 25 23:11:46.283 2024 router-re0 : %PFE-3: fpc3 CMTFPC: Reporting self ping blackhole for FPC 3 PFE 0 tx 858590744 rx 858589918 last-rx 858589918

Feb 25 23:11:46.293 2024 router-re0 : %PFE-3: fpc3 CMTFPC: Reporting self ping blackhole for FPC 3 PFE 1 tx 858590712 rx 858589887 last-rx 858589887

Feb 25 23:11:46.990 2024 router-re0 : %PFE-5: fpc3 Error: /fpc/3/pfe/0/cm/0/CM[0]/0/CM_CMERROR_FABRIC_SELFPING (0x2e0006), scope: board, category: functional, severity: major, module: CM[0], type: MPC fabric selfping blackhole



The root cause has not been found as the issue is not reproducible. To recover the FPC's the following commands were used:

request chassis fpc slot 2 restart
request chassis fpc slot 3 restart