After enabling Juniper Resiliency Interface on an MX10k8, both the installed FPC's in slot 0 and slot 8 enter a cyclic reboot. Sample configuration as following.

chassis {

  fpc 0 {

    pfe 0 {

      exception-reporting {

        category firewall {

          inline-monitoring-instance JRI_MON;

        }

        category forwarding-state {

          inline-monitoring-instance JRI_MON;

        }

        category layer2 {

          inline-monitoring-instance JRI_MON;

        }

        category layer3 {

          inline-monitoring-instance JRI_MON;

        }

        category packet-errors {

          inline-monitoring-instance JRI_MON;

        }

      }

    }

}

}

Note that the same problem can be seen with MPC2E-NG, MPC5E. The MPC10E and latest MPC type are stable.

MPC keeps coredump once enabled "exception-reporting category packet-errors".

This problem is with "exception-reporting category packet-errors" configure. Problem will be seen in releases that have PR1684382 fix.

PR1730840 has fixed this issue. Upgrading to below release will stop the coredump and make the FPC online.
The fixed JUNOS/JUNOS-EVO release are: evo:23.4R2-EVO evo:24.1R1-EVO junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2 junos:24.1R1