In some cases, Juniper Networks EX4300 Series switches might experience a core-dump for PFEX, and then reboot to recover. This explains the root cause for this and how to resolve it.

Your device experienced a reboot, and just before that, a core-dump was generated with the following logs seen prior to that:

May 8 12:18:24.484 2023 switch pfex: 

May 8 12:18:24.486 2023 switch pfex: PANIC PANIC PANIC PANIC PANIC PANIC

May 8 12:18:24.488 2023 switch pfex: Heap corruption at 0x0x0

May 8 12:18:24.488 2023 switch pfex: Traceback:

May 8 12:18:24.489 2023 switch pfex:   Frame 00: sp = 0x065d8f90, pc = 0x0184eaf0

May 8 12:18:24.490 2023 switch pfex:   Frame 01: sp = 0x065d8fa8, pc = 0x01853dc0

May 8 12:18:24.490 2023 switch pfex:   Frame 02: sp = 0x065d8ff0, pc = 0x01805834

May 8 12:18:24.491 2023 switch pfex:   Frame 03: sp = 0x065d9018, pc = 0x018060fc

On EX4300 platforms, PFEX might crash if soft error recovery feature is enabled on the PFE. It might cause traffic impact and generate a core file. This is addressed on https://prsearch.juniper.net/problemreport/PR1567515. To resolve this, please upgrade to one of the following resolved-in versions:

19.1R3-S5, 19.4R3-S3, 20.1R3, 20.3R3, 20.4R2, 21.1R1, 21.1R2, 21.2R1 or 20.2R3.S1.

2023-05-12: KB created.

PR1567515