System requirements for a virtual appliance Before installing Web Gateway as a virtual appliance, you must make sure that the system requirements for this appliance type are met. These requirements must also be met when installing a virtual appliance on an Azure platform with Hyper-V. Virtual machine software This VMware type is required: VMware ESXi The following table shows the versions of this VMware type that we recommend for use with particular versions of Web Gateway. VMware versions that are not recommended can still be run with Web Gateway. Recommended VMware versions ESXi 5.0 ESXi 5.5 update 2 ESXi 6.0 ESXi 6.0 update 2 ESXi 6.5 ESXi 6.5 update 2 ESXi 6.7 update 1 MWG 7.6.x.x No Yes Yes No No No No MWG 7.7.x.x No Yes No Yes No No No MWG 7.8.x.x No No No Yes Yes Yes Yes* MWG 8.x.x No No No Yes Yes Yes Yes* No = Not recommended Yes = Recommended Yes* = ESXi 6.7 update 1 is recommended for the MWG 126.96.36.199 main release and later 7.8.x.x releases, as well as for the MWG 8.0.1 controlled release and later 8.x.x releases. Virtual machine host system CPU — 64-bit capable Virtualization extension — VT-x/AMD-V Virtual machine Specifications depend on how you are using a virtual appliance. Specifications for a virtual machine Use RAM (in GB) Hard-disk space (in GB) CPU cores Functional testing (user interface based on Java applet or desktop client) 4 80 4 Functional testing (HTML-based user interface) 8 80 4 Production (minimum) 16 200 4 Production (recommended) 32 500 4 or more Setup procedures differ for each VMware type. The following table provides some more common setup parameters and values. Parameter names can also differ. For parameters that are not listed, use the default values in the procedures. Virtual machine settings Option Definition Configuration type Typical | Advanced (recommended) Installation mode ISO image Operating system CentOS 64-bit, version 7 Memory 32 GB (recommended) Starting with version 4.1, VMware ESXi, which is one of the supported VMware types for a virtual Web Gateway appliance, includes some optimizations known as NUMA optimizations. A host system for virtual machines that runs this VMware is also referred to as a NUMA node. Memory must then be allotted to a virtual machine in relation to the memory that is available on a NUMA node, otherwise you might experience a severe impact on performance. For example, if you set up three virtual machines on one NUMA node and configure the same number of processors (CPU cores) for each virtual machine, do not allot more than one third of the memory that is available on the NUMA node to each virtual machine. Best results are achieved if you run one virtual machine on one NUMA node. Make sure that you also reserve a certain amount of memory for the NUMA node (the host system). Hard-disk space 500 GB (recommended) Number of processors 1 | 2 | 4 (recommended) | <other values> The number of processors (CPU cores) that are provided for selection depends on the equipment of the host system that is used for setting up the virtual appliance. When virtual machines are set up on a host system that runs ESXi VMware, version 4.1 or later, with NUMA optimizations, CPU cores must be configured in relation to what is allowed on a NUMA node (a host system). The number of CPU cores that you configure for a virtual machine must be multiples or divisors of the number of CPU cores that fit in with the size of a NUMA node. For example, if the size of a NUMA node is sufficient for running six CPU cores, configure virtual machines with two, three, or six cores (if you are only using one node), or with 12, 18, 24, and so on (if you are using multiple nodes). Best results are achieved if you run one virtual machine on one NUMA node. Network connection mode Bridged (recommended) | NAT | <other values> CD/DVD drive with assigned ISO image <drive name>/<name of the ISO image> Network interface card type VMXNET 3 SCSI controller (for some ESX versions) BusLogic SCSI (not supported in a 64-bit environment) | LSI Logic Parallel (default) | LSI Logic SAS | VMware PV SCSI (recommended) vSwitch — Allow promiscuous mode Yes vSwitch — Allow forged transmits Yes Supported Hyper-V servers Windows Server 2016 R2 (64-bit) Windows Server 2012 R2 (64-bit) Microsoft Hyper-V Server 2012 R2 (64-bit) Windows Server 2008 R2 (64-bit) Static MAC address for a virtual appliance on Hyper-V A virtual machine on a Hyper-V server platform is by default configured to use dynamic MAC addresses. When Web Gateway runs as a virtual appliance on this platform, using dynamic MAC addresses will result in losing IP address information after a restart. For this reason, the default settings must be changed to let the virtual appliance use a static MAC address.