Export FortiManager by hand
A manual upload reads the appliance alone; its managed estate needs the Collector.
On this page
Upload the appliance configuration
Upload the FortiManager's CLI configuration text. Its first line must be the #config-version=FMG-... header: without it the file is not read as a FortiManager.
This guide names no command for it: use the Collector, which reads the appliance and every managed FortiGate.
What the upload is read for
- The appliance: system settings, administrators and roles, interfaces, log forwarding, SNMP and HA.
- The model and release from the header.
The serial number, the ADOMs, the managed FortiGates and the policy packages do not come with this upload.
Through the Collector
The Collector reads FortiManager over its JSON-RPC API: each ADOM, each managed FortiGate (serial, model, version, sync and connection state, HA, VDOMs, installed package), each policy package, and each FortiGate's configuration. Each FortiGate you choose is its own analysis.
Upload
Open New analysis
Choose File upload and select the file, or choose Paste, paste the output and select Upload and parse.
It is sent at once
One file per upload. ConfigProof reads the vendor and export type from the content, not the file name, then asks the client, project and name. If your role is limited to certain clients, choose the client first.
Answer the picker if asked
A file that holds several VDOMs, contexts, virtual systems or gateways opens a picker. Each one you choose is its own analysis.