FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
WinterSnowYap
Article Id 388181
Description This article describes how to troubleshoot FortiManager's failure to add the model device in a backup ADOM.
Scope FortiManager.
Solution

Below is the scenario:

 

  1. At FortiManager run CLI commands:

 

diagnose debug disable
diagnose debug reset
diagnose debug app fgfmsd 255 <Device Name>

 

In this example, it will be:


diagnose debug app fgfmsd 255 FGT
diagnose debug application depmanager 255
diagnose dvm debug enable dvmcmd
diagnose debug application dmapi 255
diagnose debug application dmworker 255
diagnose debug service cdb 255
diagnose debug service cmdb 255
diagnose debug service main 255
diagnose debug service sys 255
diagnose debug enable

 

  1. At FortiManager inside the ADOM (Backup Mode), Add a Model Device.

 

202504_FMG_AddModelIssue_001.png

 

202504_FMG_AddModelIssue_002.png

 

  1. At FortiManager the FortiGate device is unable to bring up after added using Add Model Device method. Inside the debug result will show similar result.

 

202504_FMG_AddModelIssue_003.png

 

  1. At FortiManager, edit the FortiGate device settings, and perform the changes:

  • Fill up the correct login credentials.
  • Enable the 'Enforce Device Configuration' setting.

 

202504_FMG_AddModelIssue_004.png

 

After that, the FortiGate device will be able to be added to FortiManager.