Technical Tip: Understanding FortiZTP status change when provisioning FortiGate to FortiManager

[tnesh]

Description	This article describes more details on FortiZTP status changes when provisioning FortiGate to FortiManager.
Scope	FortiGate, FortiManager, FortiZTP.
Solution	Unprovisioned: The devices (for example, FortiGate) that are available to be provisioned to the target location (for example, FortiManager). Incomplete - Waiting. After provisioning FortiGate to FortiManager, FortiZTP will wait for FortiGate to come online and connect to it. It will retry every 2 minutes. Incomplete - Provision is too long. After 30 minutes and no connection established between FortiGate & FortiZTP, the CLI script is still not pushed to FortiGate. FortiManager-Cloud: No license or no confirmation received from FortiManager Cloud. It will retry daily. Provisioning. FortiGate becomes online and establishes a connection to FortiZTP. CLI script being pushed to FortiGate to update the central management configuration. Provisioned. After the CLI script is pushed to FortiGate. FortiManager-Cloud: After getting confirmation from FortiManager-Cloud.