This article explains possible causes and solutions for SRX devices that frequently hang or goes down and requires a reboot to recover.

Below logs are observed during the timestamp:

Chassis logs observed:

fpc_srxsme_is_mpim_present: slot 1, FPC not present
fpc_srxsme_owire_read_eeprom: slot 1, FPC not detected
fpc_srxsme_is_mpim_present: slot 1, FPC not present
fpc_srxsme_init: slot 1, FPC not detected

Message logs observed:

eventd[1815]: %SYSLOG-5-SYSTEM_ABNORMAL_SHUTDOWN: System abnormally shut down
eventd[1815]: %SYSLOG-5-SYSTEM_OPERATIONAL: System is operational

To address high RE CPU utilization leading to device hangs or crashes:

1. Verify if traceoptions or PCAP captures are enabled, as these can significantly increase RE CPU usage. Disable if not required.

2. Check the logging mode configured on the device (event or stream).

3. If event mode is used, logs are stored locally on the device, consuming RE resources and potentially causing high CPU. Consider switching to stream mode.

4. In case of Stream mode, verify the source address configured and the route to reach the monitoring server.

5. If the source address belongs to the loopback interface or FXP0, both the interfaces are bound to RE, thus it will again cause RE CPU. The same goes if they use an external interface as FXP0. 

** It is always suggested to use the revenue interface as the external interface and their IPs as the source address.