You must set your keyboard to United States English before installing the ASAv and for using the VM console. VCenter and the LDAP servers in your environment are installed in an ASCII-compatible mode. The ASAv OVF deployment does not support localization (installing the components in non-English mode).
The selection of the asav-vi.ovf or asav-esxi.ovf file is based on the deployment target:Īsav-esxi-For deployment on ESXi (no vCenter) VPN Optimization-See VPN Optimization for additional considerations for optimizing VPN performance with the ASAv. See Multiple RX Queues for Receive Side Scaling (RSS) for more information. Receive Side Scaling-The ASAv supports Receive Side Scaling (RSS), which is a technology utilized by network adapters to distribute network receive See NUMA Guidelines for more information. NUMA-You can improve performance of the ASAv by isolating the CPU resources of the guest VM to a single non-uniform memory access See Performance Tuning for the ASAv on VMware for more information. To achieve the best performance out of the ASAv, you can make adjustments to the both the VM and the host. This is theĭisable Large Receive Offload (LRO) to avoid poor
Vmxnet3-This is a para-virtualized network driver that supports 10Gbps operation but also requires CPU cycles. SR-IOV is generally preferred because it has more deployment flexibility. I40evf/ixgbe-vf-Effectively the same as above (DMAs packets between the NIC and the VM) but allows the NIC to be shared across No CPU cycles are required for moving packets. I40e in PCI passthrough-Dedicates the server's physical NIC to the VM and transfers packet data between the NIC and the VM The following vNICs are recommended in order of optimum performance. M4 server with the Intel® Xeon® CPU E5-2690v4 processors running at 2.6GHz.ĪSAv supports ESXi version 6.0, 6.5, and 6.7. The host CPU must be a server class x86-based Intel or AMD CPU with virtualization extension.įor example, ASAv performance test labs use as minimum the following: Cisco Unified Computing System™ (Cisco UCS®) C series Make sure to conform to the specifications below to ensure optimal performance. Review the following guidelines and limitations before you deploy the ASAv. It is not possible to change the resource allocation of the disk space.
The ASAv deploys with a disk storage size of 8GB. Each virtual appliance you create requiresĪ minimum resource allocation-memory, number of CPUs, and disk space-on the host machine. The specific hardware used for ASAv deploymentsĬan vary, depending on the number of instances deployed and usage requirements. You can create and deploy multiple instances of the ASAv on an ESXi server. You can also redeploy a new ASAv VM withĪSAv on VMware Guidelines and Limitations To 9.13(1)+ from an earlier version without increasing the memory of your ASAv VM.
If your current ASAv runs with less than 2GB of memory, you cannot upgrade The minimum memory requirement for the ASAv is 2GB. You can deploy the ASAv on any server class x86 CPU device that is capable of running VMware ESXi.
Configure a Network Serial Console Port.Deploy the ASAv Using the OVF Tool and Day 0 Configuration.Deploy the ASAv Using the VMware vSphere Standalone Client and Day 0 Configuration.
Access the vSphere Web Client and Install the Client Integration Plug-In.Deploy the ASAv Using the VMware vSphere Web Client.Unpack the ASAv Software and Create a Day 0 Configuration File.ASAv on VMware Guidelines and Limitations.