Step 2: Configure virtual hardware settings

After deploying the FortiADC-VM image and before powering on the virtual appliance, log into the Hyper-V Manager and configure the virtual appliance hardware settings to suit the size of your deployment.

Virtual hardware settings summarizes the defaults that are set in the default image and provides rough guidelines to help you understand whether you need to upgrade the hardware before you power on the virtual appliance. For more precise guidance on sizing, contact your sales representative or Fortinet Technical Support.

Virtual hardware settings

Component	Default	Guidelines
Hard drive	30 GB	30 GB is insufficient for most deployments. You must upgrade the hard drive before you power on the appliance. After you power on the appliance, you must reformat the FortiADC OS log disk with the following command: execute formatlogdisk You need to upload a license file before using this command.
CPU	1 CPU	1 CPU is appropriate for a VM01 license. Upgrade to 2, 4, 8, 16, or 32 CPU for VM02, VM04, VM08, VM16, and VM32 licenses, respectively.
RAM	4 GB	4 GB is the minimum. See the section on vRAM for guidelines based on expected concurrent connections.
Network interfaces	8 bridging vNICs are mapped to a port group on one virtual switch (vSwitch).	Change the mapping as required for your VM environment and network.

Resizing the virtual disk

The virtual disk size of the imported FortiADC-VM virtual machine is 30 GB (the default size for a Hyper-V virtual machine).

To increase the size of the virtual hard disk:

Shut down the FortiADC-VM virtual machine (Actions > Shut Down).
Select the FortiADC-VM virtual machine in the list of machines, and then, under Actions, click Settings.
Under Hardware, expand the IDE Controller item that contains the machine’s hard drives, and then select the hard drive data.vhd.

In the hard drive settings, under Media, ensure that Virtual hard disk is selected, click Edit, and then use the Edit Virtual Hard Disk wizard to expand the size of the virtual disk.
Start the virtual machine (Actions > Start).
If you have resized logdisk (not bootdisk), after rebooting FortiADC and uploading a license file, you should execute the following command: execute formatlogdisk. Executing this command will clear all statistics and logs etc.

Configuring the number of virtual CPUs (vCPUs) and RAM

By default, the virtual appliance is configured to use 1 vCPU. Depending on the FortiADC-VM license that you purchased, you can allocate from 1 to 32 vCPUs.

To change the number of vCPUs and RAM:

Shut down the virtual machine (Actions > Shut Down).
Select the FortiADC-VM virtual machine in the list of machines, and then, under Actions, click Settings.
Under Hardware, select the Processor item, and then use the Processor settings to increase or decrease the number of vCPUs.

Under Hardware, select the Memory item, and then use the Memory settings to increase or decrease the Startup RAM. Make sure Dynamic Memory is not enabled.

Click OK and then start the machine.

MAC address spoofing

To operate correctly, FortiADC-VM virtual switches require MAC address spoofing. The option is enabled by default when you create a virtual switch. It is located in the settings for the virtual machine under Hardware. To view the option, simply expand the virtual switch component and then select Advanced Features.

Important: In order for the HA feature to work correctly, the Hyper-V HA setup also requires that the virtual switch connecting the heartbeat port also have MAC address spoofing configured.

Mapping the virtual NICs (vNICs) to physical NICs

When you import the FortiADC-VM package, the import process creates 8 bridging vNICs and automatically maps them to a port group on 1 virtual switch (vSwitch) within the hypervisor (the default name of this vSwitch is vmnet). Each of the interfaces in FortiADC-VM uses one of these vNICs. vSwitches are themselves mapped to physical ports on the server.

In most cases, you do not need to change the default mappings of the FortiADC-VM network adapter ports to the host computer’s physical ports. The default bridging vNIC mappings are appropriate for configurations where each of the host’s guest virtual machines have their own IP addresses on your network.

You can change the mapping, map other vNICs, or create additional vSwitches, if your VM environment requires it.

To configure the mappings, in the Hyper-V Manager, go to Actions > Virtual Switch. Manager.

If you are unsure of your network mappings, try bridging before you attempt non-default vNIC modes such as NAT or host-only networks.

Trunking with Hyper-V networking

In the Hyper-V Manager GUI you will not find a way to define a trunk on a vNIC attached to a vSwitch. But this can be done via PowerShell. Your domain account must be given the proper rights, which can be done by adding it to the Hyper-V Administrators local group, on the Hyper-V server. You must also launch your PowerShell console in an elevated form, as Admin.

To trunk with Hyper-V networking

1. Delete the default network adapter if the interface uses the same name.

2. Add the ethernet ports

Add-VMNetworkadapter -VMName FortiADC -Name "adapter1"

3. Trunk adapter1 and add the required VLANIDs

Set-VMNetworkAdaptervlan -VMName FortiADC –VMNetworkAdapterName " adapter1" -Trunk -AllowedVlanIdList "10, 20, 30" -NativeVlanId 0