Fortinet white logo
Fortinet white logo

Deploy the OVF file

Deploy the OVF file

You must first use VMware vSphere Client to deploy the FortiProxy‑VM OVF package.

To deploy the virtual appliance:
  1. Use the VMware vSphere client to connect to VMware vSphere server:

    1. On your management computer, start the VMware vSphere Client.

    2. In IP address / Name field type the IP address or FQDN of the VMware vSphere server.

    3. Enter the user name and password then click Login.

    After you successfully log in, the vSphere Client window appears.

  2. Go to File > Deploy OVF Template.

    A deployment wizard window appears.

  3. In the Deploy OVF Template window, click Browse and navigate to the FortiProxy‑VM OVF file.

  4. Click Next twice.

    Click Accept to agree to the End User License Agreement, then click Next.

  5. On the Name and Location page, type a unique descriptive name for this instance of FortiProxy‑VM, then click Next.

    The name appears in the vSphere Client inventory, such as FortiProxy-VM-Doc. If you plan to deploy multiple instances of this file, consider a naming scheme that makes each VM’s purpose or IP address easy to remember.

    This name is not used as the host name, and it does not appear in the FortiProxy‑VM GUI.

  6. On the Disk Format page, select one of the following options and then click Next:

    • Thick Provision Lazy Zeroed: Allocates the disk space statically (no other volumes can take the space), but does not write zeros to the blocks until the first write takes place to that block during runtime (which includes a full disk format).

    • Thick Provision Eager Zeroed: Allocates the disk space statically (no other volumes can take the space), and writes zeros to all the blocks.

    • Thin Provision: Allocates the disk space only when a write occurs to a block, but the Virtual Machine File System (VMFS) reports the total volume size to the OS. Other volumes can take the remaining space. This allows you to float space between your servers, and expand your storage when your size monitoring indicates there is a problem. Once a Thin Provisioned block is allocated, it remains in the volume regardless of whether you have deleted data.

    Note

    Regardless of your choice here, you should later either allocate or make available at least 40 GB of disk space. 30 GB is only the default minimum value, and is not recommended.

  7. On the Network Mapping page, if the hypervisor has more than one possible network mapping, select the row for the network mapping that FortiProxy‑VM should use, then click Next.

  8. On the OVF Template Ready to Complete page, review the template configuration. Ensure that Power on after deployment is not enabled. You need to configure the FortiProxy hardware settings before powering on the VM.

  9. Click Finish to deploy the OVF template. A Deployment Completed Successfully dialog displays once the FortiProxy OVF template wizard has finished.

Note

Do not power on the virtual appliance until you have completed the following in the VM environment:

  • Resize the virtual disk (VMDK).

  • Set the number of vCPUs.

  • Set the vRAM on the virtual appliance.

  • Map the virtual network adapter(s).

Deploy the OVF file

Deploy the OVF file

You must first use VMware vSphere Client to deploy the FortiProxy‑VM OVF package.

To deploy the virtual appliance:
  1. Use the VMware vSphere client to connect to VMware vSphere server:

    1. On your management computer, start the VMware vSphere Client.

    2. In IP address / Name field type the IP address or FQDN of the VMware vSphere server.

    3. Enter the user name and password then click Login.

    After you successfully log in, the vSphere Client window appears.

  2. Go to File > Deploy OVF Template.

    A deployment wizard window appears.

  3. In the Deploy OVF Template window, click Browse and navigate to the FortiProxy‑VM OVF file.

  4. Click Next twice.

    Click Accept to agree to the End User License Agreement, then click Next.

  5. On the Name and Location page, type a unique descriptive name for this instance of FortiProxy‑VM, then click Next.

    The name appears in the vSphere Client inventory, such as FortiProxy-VM-Doc. If you plan to deploy multiple instances of this file, consider a naming scheme that makes each VM’s purpose or IP address easy to remember.

    This name is not used as the host name, and it does not appear in the FortiProxy‑VM GUI.

  6. On the Disk Format page, select one of the following options and then click Next:

    • Thick Provision Lazy Zeroed: Allocates the disk space statically (no other volumes can take the space), but does not write zeros to the blocks until the first write takes place to that block during runtime (which includes a full disk format).

    • Thick Provision Eager Zeroed: Allocates the disk space statically (no other volumes can take the space), and writes zeros to all the blocks.

    • Thin Provision: Allocates the disk space only when a write occurs to a block, but the Virtual Machine File System (VMFS) reports the total volume size to the OS. Other volumes can take the remaining space. This allows you to float space between your servers, and expand your storage when your size monitoring indicates there is a problem. Once a Thin Provisioned block is allocated, it remains in the volume regardless of whether you have deleted data.

    Note

    Regardless of your choice here, you should later either allocate or make available at least 40 GB of disk space. 30 GB is only the default minimum value, and is not recommended.

  7. On the Network Mapping page, if the hypervisor has more than one possible network mapping, select the row for the network mapping that FortiProxy‑VM should use, then click Next.

  8. On the OVF Template Ready to Complete page, review the template configuration. Ensure that Power on after deployment is not enabled. You need to configure the FortiProxy hardware settings before powering on the VM.

  9. Click Finish to deploy the OVF template. A Deployment Completed Successfully dialog displays once the FortiProxy OVF template wizard has finished.

Note

Do not power on the virtual appliance until you have completed the following in the VM environment:

  • Resize the virtual disk (VMDK).

  • Set the number of vCPUs.

  • Set the vRAM on the virtual appliance.

  • Map the virtual network adapter(s).