FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
Nur
Staff
Staff
Article Id 322274
Description This article describes the case when upgrading ADOM but FortiManager is still showing value being used from the ADOM database.
Scope FortiManager and ADOM.
Solution

When upgrading the ADOM fails, run the debug and will know which object and value cause an error.

Below is an example, web filter object name g-default has the unwanted value for URLFILTER.

 

Screenshot 2024-06-25 101755.png

 

Basically, it is possible to delete the unwanted value from the ADOM database by going to Policy &Object -> Advanced -> CLI configuration.

 

Screenshot 2024-06-26 083030.png

 

 

However, if the GUI shows that the object does not have any value, it is necessary to check from the CLI side.

 

execute fmpolicy print-adom-object <adom_name> <category> {all | list} <output>

 

This article focuses on the search web filter profile name g-default.

 

Screenshot 2024-06-25 103143.png

 

Somehow, the CLI still detected that URLFILTER has the value. Hence, it is necessary to delete it via the script from FortiManager.


Name: Webfilter g-default
run script on : Policy Package or ADOM Database
Script details :
config webfilter profile
    edit "g-default"
        config web
            unset urlfilter-table
end

 

Screenshot 2024-06-25 103533.png

 

After deleting the unwanted value, it will be possible to upgrade the ADOM without having any issues.

Contributors