Skip to main content
Arif69
Staff
Staff
March 13, 2026

Troubleshooting Tip: Unable to push network settings from FortiManager to AWS FortiGate cluster

  • March 13, 2026
  • 0 replies
  • 108 views
Description This article describes how to troubleshoot when a user is unable to push network settings from FortiManager to the AWS FortiGate cluster.
Scope FortiManager, FortiGate.
Solution
  1. Configure a static route in the FortiGate device database:

 

chrome_KTtiVldX5P.png

 

  1. After configuring the static route, the Config Status shows 'Modified':

     

    chrome_5n6MXNJ5Ig.png

     

     

  2. However, when proceeding with Install Device Settings, the install preview shows 'No preview result':

     

    chrome_9TyW4EgUug.png

     

     

  3. For clarification, the FortiGate is not assigned any Provisioning Templates that usually might be the cause of this issue.

     

     

  4. Further checking, the FortiGate has a 'vdom-exception' configured for the static route:

     

    chrome_OEJdJ7vy1P.png

     

     

  5. FortiManager will not install the static route because the command 'handle-nonhasync-config' is preventing it. This command is disabled by default:

     

    chrome_ELvW4RvvB8.png

     

     

  6. To ensure FortiManager installs network settings that are configured as 'vdom-exception', the 'handle-nonhasync-config' needs to be enabled through CLI:

 

config system dm

(dm)# set handle-nonhasync-config enable

(dm)# end

 

  1. After enabling the command, the static route shows up in the Install Preview:

     

 

chrome_cYCs3KosTg.png