FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
This article describes how to troubleshoot a FortiGate that randomly reboots in an AWS environment.
Scope
FortiGate
Solution
Check the system event logs for any errors or warnings that may indicate the cause of the reboot.
Verify the CPU and memory usage of the firewall to ensure it is not overloaded. This can be done by running the 'get sys performance status' command.
Check for any UDP flood or other traffic that may be causing a DoS Attack. Check Logs -> Security Events -> Anomaly.
If the firewall is in HA, verify the HA configuration and ensure that it is set up correctly. This can be done by running the 'get sys ha status' command.
Check the console logs for any errors or warnings that may indicate the cause of the reboot.
If the issue persists, enable alerts on the Monitoring tools like SNMP for high CPU and high memory consumption, and ensure that console logging is enabled on AWS.
The firewall can also be rebooted by AWS CloudFront, and there were no crash logs or console logs available to determine the cause of the high CPU usage. It is recommended to check with AWS support to determine the cause of the reboot and to ensure that the AWS CloudFront is configured correctly.
