By default the CPU reservation for the ASAv is 1000 MHz.To change from 1GB to 1.5GB, power down your VM, modify the memory, and power the VM back on. In these cases, you can enable the ASAv5 to be deployed in a VM with 1.5 GB of memory. Console messages related to spontaneous reboots or critical syslogs related to memory usage are symptoms of memory exhaustion. This can occur during certain resource heavy applications, such as enabling An圜onnect or downloading files. In some situations, the ASAv5 may experience memory exhaustion. Do not use the VMware-recommended memory configuration minimum, default, and maximum values.
Note: If you need to change the memory or vCPU hardware settings, use only the values documented in Smart Software Licensing for the ASAv. Under-provisioning can affect performance, and over-provisioning causes the ASAv to warn you that it will reload after a waiting period (24 hours for 100-125% over-provisioning 1 hour for 125% and up), the ASAv will reload.
Do not change the memory setting or any vCPU hardware settings in the Edit Settings dialog box unless you are requesting a license for a different Throughput Level. The memory allocated to the ASAv is sized specifically for the Throughput Level.Memory and vCPU Allocation for Throughput and Licensing For failover deployments, make sure that the standby unit has the same model license for example, both units should be ASAv30s.You must set your keyboard to United States English before installing the ASAv and for using the VM console.Be sure that the VMware 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).asav-esxi-For deployment on ESXi (no vCenter).The selection of the asav-vi.ovf or asav-esxi.ovf file is based on the deployment target: Table 2 Port Group Security Policy Exceptions See the vSphere documentation for more information. You may need to modify these settings for the following ASAv configurations. Security Policy for a vSphere Standard Switchįor a vSphere switch, you can edit Layer 2 security policies and apply security policy exceptions for port groups used by the ASAv interfaces. See Cisco ASA Compatibility for system requirements.
You can deploy the ASAv using the VMware vSphere Web Client, vSphere standalone client, or the OVF tool. Used for dynamic resource scheduling and distributed power management. Table 1 VMware Feature Support for the ASAv VMware Feature Support for the ASAv lists the VMware feature support for the ASAv.