When an interface is disabled on the remote device or an optical module is removed from the local device, causing the local interface to enter the “operational down” state and remains operationally down when the next 60-second DPDK Tx-stuck monitoring cycle runs, that interface is likely to generate false alarms, as shown below:

Aug 16 18:06:32 SRX : %PFE-3: SRX dpdk_periodic: DPDK port 0 is stuck with hardware issue!!!

Aug 16 18:07:02 SRX : %PFE-3: SRX DPDK port stuck hardware issue is resolved!!!

This issue is currently being tracked in PR1963533:

https://prsearch.juniper.net/problemreport/PR1963533