Below steps would cause the FPC0 to go offline and generate an srxpfe corecump.
1. Disable 4 out of 5 interfaces
2. Commit and-quit
3. Rollback 1
4. Commit and-quit
5. show security flow session destination-prefix <prefix>
##############. More details of steps - ##################
root@testbed> edit
Entering configuration mode
[edit]
root@testbed# rollback 1
load complete
root@testbed# show | compare
[edit interfaces ge-0/0/1]
- disable;
[edit interfaces ge-0/0/2]
[edit interfaces ge-0/0/3]
[edit interfaces ge-0/0/4]
root@testbed# commit and-quit
commit complete
Exiting configuration mode
root@testbed> show security flow session destination-prefix <prefix> | refresh 2
---(refreshed at 2025-06-18 21:51:31 UTC)---
Total sessions: 0
---(refreshed at 2025-06-18 21:51:33 UTC)---
error: usp_ipc_client_recv_:ipc_pipe_read() failed read timed out after 5 second(s)
---(refreshed at 2025-06-18 21:51:41 UTC)---
---(refreshed at 2025-06-18 21:51:49 UTC)---
---(refreshed at 2025-06-18 21:51:57 UTC)---
^C[abort]
root@testbed> show chassis fpc
Temp CPU Utilization (%) CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt 1min 5min 15min DRAM (MB) Heap Buffer
0 Online -------------------- CPU less FPC --------------------
---(refreshed at 2025-06-18 21:52:19 UTC)---
error: usp_ipc_client_recv_ 1250: ipc_pipe_read fails! error:Connection reset by peer(54), tries:1
---(refreshed at 2025-06-18 21:52:21 UTC)---
root@testbed> show chassis fpc pic-status
Slot 0 Offline FPC
Slot 0 Online FPC
PIC 0 Ready
root@testbed> show system core-dumps
/var/crash\/*core*: No such file or directory
-rw------- 1 root wheel 161646347 Jun 17 21:37 /var/tmp/srxpfe.core.0.gz
-rw------- 1 root wheel 134938618 Jun 18 21:52 /var/tmp/srxpfe.core.1.gz
/var/tmp/pics\/*core*: No such file or directory
/var/crash/kernel.*: No such file or directory
/var/jails/rest-api/tmp\/*core*: No such file or directory
/tftpboot/corefiles\/*core*: No such file or directory
total files: 2
Core/crash
After the interfaces are enabled, wait for the interfaces to come up before running the "show security flow session destination-prefix <prefix>" command.
This issue has been fixed in PR :1874848 in the following releases.
junos:24.2R2-S1 junos:24.4R2 junos:25.2R1 junos:25.3R1