Description
This article describes how to manually reset workflow database for FortiManager ADOM in workflow mode when there is unexpected error or abnormality seen in the ADOM during a workflow session.
Scope
FortiManager.
Solution
- Starting from FortiManager version 7.0.7 / 7.2.2 GA, a new CLI command has been included.
The 'diagnose dvm workflow workflow-db-reset <adom_name>' command allows the user to manually reset the workflow database for FortiManager ADOM in workflow mode.
This CLI command is useful when a user experiences unexpected errors or abnormalities during a workflow session such as policies in a policy package going missing when creating a new workflow session.
- The user can enter the following CLI command in the FortiManager to reset the workflow database for a specific ADOM, which will subsequently trigger a reboot of FortiManager.
Below is a snippet of the CLI command which is running against ADOM 'test_adom'.
diagnose dvm workflow workflow-db-reset test
ADOM [test] workflow DB will be re-generated from rundb. It is recommended to perform a backup first. System will reboot afterwards.
Do you want to continue? (y/n)
- Once the FortiManager boots up, verify if the workflow session issues or errors are rectified.
Related article:
Technical Tip: How to configure workflow approval matrix on FortiManager using the remote RADIUS adm...
