Fortinet Document Library

Version:


Table of Contents

About FortiGate for AWS

Deploying FortiGate on AWS

Deploying auto scaling on AWS

Single FortiGate-VM Deployment

Use Case: High Availability for FortiGate on AWS

Security Fabric Connector Integration with AWS

Resources

Upgrade Path Tool
6.0.0
Copy Link

Troubleshooting

CREATE_FAILED error in CloudFormation stack

If you encounter a CREATE_FAILED error when you launch the Quick Start, it is recommended that you relaunch the template with Rollback on failure set to No. (This setting is under Advanced in the AWS CloudFormation console Options page.) With this setting, the stack’s state is retained and the instance is left running, so you can troubleshoot the issue.

Caution

When you set Rollback on failure to No, you continue to incur AWS charges for this stack. Ensure to delete the stack when you finish troubleshooting.

FortiGate-VM master election was not successful

If the FortiGate-VM master election is not successful, reset the master election. If the reset does not solve the problem, please contact support.

How to reset the master election

To reset the master election, navigate to the DynamoDB table <ResourceTagPrefix>-FortiGateMasterElection. Click the Items tab and delete the master record (the only item listed).

A new master FortiGate-VM will be elected and a new record will be created as a result.

For details on locating the DynamoDB table <ResourceTagPrefix>-FortiGateMasterElection, refer to the master election portion of the section Verifying the deployment.

Resources

Troubleshooting

CREATE_FAILED error in CloudFormation stack

If you encounter a CREATE_FAILED error when you launch the Quick Start, it is recommended that you relaunch the template with Rollback on failure set to No. (This setting is under Advanced in the AWS CloudFormation console Options page.) With this setting, the stack’s state is retained and the instance is left running, so you can troubleshoot the issue.

Caution

When you set Rollback on failure to No, you continue to incur AWS charges for this stack. Ensure to delete the stack when you finish troubleshooting.

FortiGate-VM master election was not successful

If the FortiGate-VM master election is not successful, reset the master election. If the reset does not solve the problem, please contact support.

How to reset the master election

To reset the master election, navigate to the DynamoDB table <ResourceTagPrefix>-FortiGateMasterElection. Click the Items tab and delete the master record (the only item listed).

A new master FortiGate-VM will be elected and a new record will be created as a result.

For details on locating the DynamoDB table <ResourceTagPrefix>-FortiGateMasterElection, refer to the master election portion of the section Verifying the deployment.