FortiManager enforces a device/VDOM model constraint that prevents deleting a VDOM while its management VDOM resides in a different ADOM. This article explains the constraint and provides two practical workarounds.
FortiManager's ADOM (Administrative Domain) architecture determines how VDOMs are assigned and managed. In Normal Device Mode, all VDOMs from a single FortiGate must be placed in the same ADOM. In Advanced Device Mode, individual VDOMs from the same FortiGate can be assigned to separate ADOMs, enabling multi-tenant management.
The deletion restriction occurs because FortiManager's device database tracks the management VDOM's ADOM assignment. When the management VDOM is in a different ADOM than the target VDOM, FortiManager cannot process the deletion through its normal device database operations. This is consistent with expected behavior where FortiManager displays errors when the management VDOM is not in the current ADOM for example, the error 'The management VDOM for device xxxxxx is not in the current advanced ADOM'.
Workaround 1: Move the VDOM to the Same ADOM. Temporarily move the non-management VDOM so that both the management VDOM and the target VDOM reside in the same ADOM, then delete the VDOM.
Workaround 2: Delete Directly on the FortiGate and Resync.
Delete the VDOM directly on the FortiGate (bypassing FortiManager's ADOM restriction), then resynchronize the FortiGate on FortiManager.
Verify the VDOM is removed from FortiManager's device database. Note: If the VDOM was created in FortiManager's device database but not properly saved, you may encounter an "Internal error" (code -20001) when attempting deletion. In such cases, run the following command on FortiManager to fix the database:
diagnose cdb upgrade check resync-dev-vdoms
This resyncs and removes any missing VDOMs from the device database.
Related documents:
|