After formatting this drive, the FortiGate performs a reboot. The FortiGate continues its provisioning process and detects that there is an additional hard disk and automatically formats that drive for use.
#Fortigate vm license registration license
Upon boot of the FortiGate, it goes through the normal boot process and detects that there is a FortiGate VM license to install. Once all of these items have been configured, the remaining task is to power up the FortiGate and observe Cloud-Init provision the FortiGate: – Screenshot of hardware listing referencing cloud-init in Proxmox Observing the Cloud-Init process Confirm that the cloud-init image has been added under the hardware listing of the FortiGate VM Figure.
#Fortigate vm license registration iso
– Screenshot of select cloud-init ISO image in ProxmoxĤ. Select the cloud-init ISO image | Click “Create” Figure. – Screenshot of adding CD/DVD Drive in Proxmoxģ. Click “Hardware” | “Add” | “CD/DVD Drive” Figure. – Screenshot of the Proxmox navigation barĢ. In Proxmox, click on the FortiGate Figure. Before launching the FortiGate for the first time, you must add a CD-ROM referencing the cloud-init ISO image as detailed in the following process:ġ. In order to apply it to the FortiGate, you need to first create a FortiGate VM in proxmox as detailed in the following article.
![fortigate vm license registration fortigate vm license registration](https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/resources/af649bd0-a4ce-11e8-8784-00505692583a/images/dbce6b038395094dd3fab4b3023e000f_000.FC.license.download.png)
Once you have the cloud-init ISO image created, the next step is to apply it to the FortiGate VM. – Screenshot of ISO image upladed to Proxmox Applying the Cloud-Init Image to the FortiGate VM in Proxmox Once the file has been uploaded, confirm that it is listed in the available ISO images as shown below: Figure. – Screenshot of ISO upload dialog box with file selected in ProxmoxĤ. – Screenshot of the ISO upload dialog box in Proxmoxģ. In the “Upload” dialog box, click “Select File” Figure. – Screenshot of location to upload ISO in ProxmoxĢ. In proxmox, under the node, Click the storage path | Content | Upload Figure. Once you have generated the ISO file, transfer it to the Proxmox server via the GUI as shown in the process below:ġ. Uploading the Cloud-Init Image to Proxmox server Using this application is beyond the scope of this article. In Windows, you can use a utility called CDBurnerXP to create the iso from a directory. – Screenshot of the terminal console running mkisofs. Once you have the file directory structure above built, you can create an iso in Linux using a utility such as mkisofs with the following command: sudo mkisofs -R -r -o fgt-bootstrap.iso cloud-init/ Figure. Set allowaccess http https ssh ping telnet Here is an example of the FortiGate configuration to be applied upon boot to the FortiGate VM: config system interface
![fortigate vm license registration fortigate vm license registration](https://geekstuff.org//wp-content/uploads/2019/11/fg-import.png)
The “user_data” is the FortiOS CLI configuration file. The file “0000” is a copy of the FortiGate VM License. Please note that you must adhere to this directory structure in order for the cloud-init process to work with FortiOS. The files have to be presented in a particular order. In its simplest form, Cloud-Init requires the image to be mounted to the FortiGate VM as an ISO image presented on a virtual CD-ROM drive. To accomplish this task using Proxmox, follow the sections listed below. This can be used to bootstrap a FortiGate for easy access after initial VM deployment to fully setting up a FortiGate VM for production-ready use with a validated configuration. Apply a custom configuration defined by FortiOS CLI.
![fortigate vm license registration fortigate vm license registration](https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/resources/598118ae-ea1f-11e9-8977-00505692583a/images/9d862424a408d1cb74d14d57c730829f_1a-license-widget.png)
Cloud-Init support in FortiOS allows the administrator to accomplish the following: However, the supported feature set goes beyond this. The ability to bootstrap a FortiGate with network information as part of the VM deployment is very valuable. As an MSSP or an administrator that manages their own private/public cloud, this functionality allows simplification of mass deployment of FortiGate VMs.
![fortigate vm license registration fortigate vm license registration](https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/resources/90a354b5-a711-11e8-8784-00505692583a/images/3e749411937164fc95138df268661e7e_awsha40.png)
With the explanation above, one can see the potential capabilities that Cloud-Init would enable for the provisioning of a FortiGate VM. In a nutshell, this functionality can be leveraged to set up a lot of tasks that is commonly associated with a VM. In a nutshell, Cloud-init is defined by the following statement:Ĭloud-init is the defacto multi-distribution package that handles early initialization of a cloud instance. What is Cloud-Initīefore I go into the details about the procedure to follow, it would be worth it to provide a bit of background about this mechanism. Have you ever cared to deploy a FortiGate virtual machine in your favorite hypervisor (Proxmox, of course) but dreaded the need of completing the mundane tasks of installing the licensing, applying the configuration and the whole host of post setup tasks required for a successful VM deployment? Well stay tuned, because in this article, I am going to cover leveraging the built-in support for Cloud-Init to simplify common deployment tasks associated with deploying a FortiGate VM into Proxmox.