Troubleshooting Tip: FortiExtender missing in FortiManager GUI 'Extender Manager' and in the CLI due to corrupted DB

[mvlasak]

Description	This article describes how to resolve an issue where a FortiExtender is authorized on a FortiGate device but does not appear in the FortiManager Extender Manager GUI or in CLI output.
Scope	FortiManager v7.2.x and above.
Solution	If the FortiExtender is missing in the GUI 'Extender Manager', verify it using the following CLI command: FMG # execute fmpolicy print-device-object <ADOM_ID> <DEVICE_ID> <VDOM_ID> Note: Object ID 3228 refers to “extension-controller extender”. Example – Missing FortiExtender FMG # execute fmpolicy print-device-object 165 2191 3 3228 Available objects for category [extension-controller extender] in device [FGT-LAB-BROKEN] vdom[root] are --------------- (no output) Example – correct output (FortiExtender displayed): FMG # execute fmpolicy print-device-object 178 2624 3 3228 Available objects for category [extension-controller extender] in device [FG01-LAB] vdom[root] are --------------- FX003TQ99009989 Option 1: Manual Fix: Run the following command to add scope for the FortiExtender on the FortiGate device: FMG # diagnose cdb check policy-packages <NAME_ASSIGNED_POLICY_PACKAGE_TO_FGT> Synchronize extender data using the following: FMG # diagnose dvm extender sync-extender-data <DEVICE_ID> savedb syncadom no If the FortiExtender is still missing in the GUI and CLI, run the following: FMG # diagnose dvm extender reset-adom After, re-import the FortiExtender template from FortiGate into the Extender Manager and assign it to the FortiExtender. Option 2: Re-add the Device. Remove the FortiGate device from FortiManager and add it again. This will remove invalid extender data associated with that device. Note: After re-adding the device, it is necessary to import the configuration again and restore template mapping.