Minimum system requirements

Before deploying the FortiSandbox virtual appliance, install and configure the latest stable release of VMware vSphere ESXi Hypervisor software. Supported versions are ESXi version 5.1 to 7.0.1.

Access VMware vSphere using a web browser or install the VMware vSphere client.

In VMware, you can expose full CPU virtualization to the guest operating system so that applications that require hardware virtualization can run on virtual machines without binary translation or paravirtualization. For more information, see https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-2A98801C-68E8-47AF-99ED-00C63E4857F6.html.

When configuring your FortiSandbox hardware settings, use the following table as a guide with consideration for future expansion.

Technical Specification	Details
	On-Premise (Private) Cloud	Public Cloud - BYOL	Public Cloud - PAYG
Hypervisor Support	VMware ESXi Microsoft Hyper-V Windows server 2016 and 2019	AWS Azure
HA Support	FortiSandbox 3.2 or later
Virtual CPUs (min / max)	4/Unlimited Fortinet recommends four virtual CPUs plus the number of VM clones.	4/16 Fortinet recommends following virtual CPUs based on the number of VM Clones: 0-4 clones - 4 cores, 5-32 clones - 8 cores, 33-100 clones - 16 cores, 101+ clones - 16 cores or higher. Pick up the appropriate Instance Type.
Virtual Memory (min / max)	16 GB / 32 GB Fortinet recommends following virtual memory based on the number of VM Clones: 0-4 clones - 24 GB 5-8 clones - 32 GB	8 GB / 64 GB Recommended: Following virtual memory based on the number of VM Clones: 0-4 clones - 8 GB, 5-32 clones - 16 GB, 33-100 clones - 32 GB, 101+ clones - 64 GB. Pick the appropriate Instance Type.
Virtual Storage (min / max)	200 GB / 16 TB Fortinet recommends at least 500 GB for a production environment.
Virtual Network Interfaces	Recommended: 4 and above	Recommended: 2 and above
VM Clones Support (Min/Max)	01/ 8 (Local VMs) and 200 (Cloud VMs)	01 / 2162	01 / 1283

1 For HA-Cluster deployment setup configured as Primary node acting as a dispatcher.

2 Can enable any of the Custom VM or Cloud VM types up to the total seat count which is based on a combination of Windows licenses (max of 8), BYOL (8) and Cloud VMs (max of 200).

3 Total seat count is based on the number of cores multiplied by 4. Maximum VMs is 128 since the highest available vCPU on PAYG is 32. CloudVMs can also be added on top and registered, however, this is not advised due to product serial number changes after shutdown.