In my previous post “Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (1)“, I tested the importing both OVA and VMDK file into Workstation and ESXi, but both ways failed. Those files are found and downloaded from Internet for only testing purpose. I believe those are good files and somebody has tested them. The only reason for my failure is because I am not using a right way to do it. In my old testing posts I have tested other versions such as 9.2.1, 8.42 and 8.02. All were successful loaded in either Vmware Workstation or ESXi.
Here are all related posts in this blog:
- ASA 8.02 in Vmware Workstation
- ASA 8.42 in VMware Workstation
- ASA 9.21 in Vmware Workstation 10
- Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (1)
- Cisco ASAv 9.4.1 and ASDM 7.4.1 in Workstation / ESXi (2)
- Cisco ASAv 9.5.1 200 and ASDM 7.5.1 in Workstation / ESXi
To find out the why this time failed I searched online again. My searching is based on error message I got from ESXi:
“The OVF package requires support for OVF PropertiesLine 264: Unsupported element ‘Property’.“
Following two links explains why , also both gives a solution , which is Vmware vCenter will be able to help load ASAv 9.4.1 into ESXi or ESX. Actually Vmeare vSphere Client has to connect to vCenter first then deploy this asav941.ova into ESX/ESXi host.
2. File -> Delply OVF Template…
3. Choose downloaded asav941.ova file as the template.
When license agreement window popped up, accept it then next.
4. Choose vm’s name
5. NICs configuration.
By default, there are 10 NICs and all of them are in same virtual network. In my case, it automatically set to connect to VM DMZ network.
6. Some other parameters.
7. Review all configuration
8. After 3-5 minutes importing process deponding on your connection speed, you should get a new VM in your ESXi.
And you can power VM on and get booting window from console.
9. VM will reboot itself once then you will get this lovely ciscoasa prompt
10. Basic configuration for SSH
Interface management 0/0 is Network adapter 1. I changed it to VM Internet network to make management interface connect to my client pc network.
There are some basic configuration to get you SSH session enabled on your ASAv.
ip address 192.168.2.12 255.255.255.0
11. Guidelines for the ASAv
- Multiple context mode
- Active/Active failover
- Shared AnyConnect Premium Licenses
12. Defaults for Smart Software Licensing
- The ASAv default configuration includes a Smart Call Home profile called “License” that specifies the URL for the Licensing Authority.
- When you deploy the ASAv, you set the feature tier and throughput level. Only the standard level is available at this time.