This article provides the steps to troubleshoot disconnections and reconnections of the SRX to MIST.

During the issue, WAN Edge Insights will display SRX disconnection logs as shown below:

WAN Edge Disconnected: 7:16:56 AM, Dec 14, 2024

WAN Edge Connected: 7:17:44 AM, Dec 14, 2024

WAN Edge Disconnected: 7:19:19 AM, Dec 14, 2024

WAN Edge Connected: 7:20:44 AM, Dec 14, 2024

To troubleshoot the issue, follow the steps below: 

1) Check for CPU Spikes:

• Review the WAN Edge Insights to see if there was a CPU spike during the time of the issue. If a spike is detected, contact Juniper TAC for assistance in troubleshooting the CPU spike.

2) Verify Outbound SSH Logs:

• If no CPU spike is found, check the outbound-SSH logs to see if the PID has been updated. Run the following command: show log outbound-ssh.log.
• If the PID has been updated, investigate potential network or ISP latency that might have caused packet loss, resulting in the outbound SSH connection being dropped. Also, verify the WAN SLE to check for any latency or jitter on the WAN link.

3) Check for MIST Cloud Outages:

• Finally, verify if there were any MIST cloud outages by visiting MIST Status.