The following KB provides insights into a scenario where customers suspect that the restart and reconfiguration of SRX occurred due to error message "WAN Edge Disconnected". It offers detailed information and guidance on this issue.

Audit logs do not contain any indications or clues regarding the underlying issue.

• Use the command >show chassis routing-engine to verify the restart status of SRX. In the provided example, it demonstrates that no restart occurred during the timestamp of the error message.

root@JTAC-SRX> show chassis routing-engine no-forwarding

Routing Engine status:

  Temperature         30 degrees C / 86 degrees F

  CPU temperature       50 degrees C / 122 degrees F

  Total memory       4096 MB Max 2007 MB used ( 49 percent)

   Control plane memory  2320 MB Max  858 MB used ( 37 percent)

   Data plane memory    1776 MB Max 1154 MB used ( 65 percent)

  5 sec CPU utilization:

   User           40 percent

   Background         0 percent

   Kernel          10 percent

   Interrupt         0 percent

   Idle           50 percent

  Model             RE-SRX380-POE-AC

  Serial ID           EW1823AN0086

  Start time           2024-04-04 17:08:39 UTC >>>>>>>>>>>>

  Uptime             11 days, 4 hours, 5 minutes, 14 seconds

  Last reboot reason       0x200:normal shutdown

  Load averages:         1 minute  5 minute 15 minute

                    0.90    0.44    0.27

• Utilize the WAN Edge Insights section to examine the timestamps of error messages, facilitating correlation with device log messages.
• Review the output of command >show interfaces extensive [interface-name] on the WAN interface to detect any interface flapping that may trigger the error message.
• Conduct a comprehensive health check on the device to eliminate other potential issues or uncover additional clues regarding the error message. Refer to [Internal Only] Generic system health check commands for detailed instructions on performing a health check.
• In this scenario, the health check yielded satisfactory results. However, the logs were overwritten, rendering log analysis inconclusive. The disconnection from Mist Cloud lasted only 2 minutes and occurred once. This could be a transient or isolated issue. It is advisable to monitor the device closely and promptly collect log files should the issue recur to accurately ascertain its cause.
• These steps will assist you in gathering more information and identifying potential causes of these errors.