Playbook Connectors on Content Hub
Recover FortiGates that drop off FortiManager
Finds FortiGates missing from FortiManager, re-adds deleted ones, authorizes pending ones and reinstalls their policy package.
@ftnt-dspilleMaintainer v1.0.0 Platform 7.4.0+ Published Oct 6, 2026
Download JSON · 99 KB
fortimanager-down-detector-1.0.0.json
sha256:aa6ca420d50152d89f559a7315ffbe89dd9996ab4e1b30eced86296a927b93e9
Sanitized by the pipeline and shipped inactive. Follow the before turning it on.
A NOC check for FortiGates that have dropped off FortiManager. For each FortiManager record, it compares the FortiManager device list against the FortiGates that should be managed. Devices that were deleted are added back as model devices, and devices waiting for authorization are authorized. Configuration is retrieved and the policy package is installed on the recovered devices.
- 00 - Start: entry point. Synchronises the FortiManager records, then runs the per-FortiManager handling.
- 01 - Per FortiManager Handling: the comparison and recovery.
- FortiGate side: log in and out, read central management and status, and point the FortiGate at FortiManager when its settings are wrong.
Requirements:
- The FortiManager ZTP solution pack from the Content Hub. It provides the Managers module and the FortiManager sub-playbooks this calls (sync, get devices, delete device, retrieve config, install policy, variable scope).
- Global variables
FGT_UsernameandFGT_Passwordfor the FortiGate logins. - "00 - Start" looks up a manager record named
SecOps_FMG. Change that name to match yours.
Something wrong with this item? Sign in to report