Jump to content


1

Cisco Virtual ASA Help

Security CCNA Security

5 replies to this topic

#1 RemzRR

RemzRR

    Member

  • Members
  • PipPip
  • 36 posts
  • 40 thanks

Posted 06 May 2015 - 08:30 AM

Need help/assistance in setting up Cisco Virtual ASA in a ESXi Environment. I have downloaded the Virtual ASA 9.41 in ovf format from Cisco's website but unable to import into ESXi.
I get a unrecognized element property at line 164. I opened the ovf in Notepad++ and what I see is listed below. Does someone have a converted image for ESXi or how can I edit the ovf file itself ????


164 <Category>Management Interface DHCP mode</Category>
165     <Property ovf:key="DHCP" ovf:type="boolean" ovf:userConfigurable="true">
166        <Description>Choose DHCP for Management interface configuration</Description>
167 <Value ovf:value="FALSE" ovf:configuration="Standalone"/>
168 <Value ovf:value="FALSE" ovf:configuration="Secondary"/>
169 <Value ovf:value="FALSE" ovf:configuration="Primary"/>

#2 willempie

willempie

    Junior Member

  • Members
  • PipPip
  • 1 posts
  • 230 thanks

Posted 06 May 2015 - 08:56 AM

Have you tried using the the vmware vsphere client, I had something similar when I used the vmware vsphere web client.

#3 RemzRR

RemzRR

    Member

  • Members
  • PipPip
  • 36 posts
  • 40 thanks

Posted 08 May 2015 - 12:17 PM

No I have never used the vsphere webclient. Sorry for the late post
Is there a difference in deploying with the webclient ?

#4 Resolute7

Resolute7

    Junior Member

  • Members
  • PipPip
  • 5 posts
  • 21 thanks

Posted 27 May 2015 - 06:45 AM

Did you try to deploy .ova file esxi?
Maybe it works.

#5 RemzRR

RemzRR

    Member

  • Members
  • PipPip
  • 36 posts
  • 40 thanks

Posted 31 May 2015 - 12:48 PM

this is the first method I have tried and it doesnt work unfortunately.

#6 slimy_cat

slimy_cat

    Member

  • Members
  • PipPip
  • 35 posts
  • 4487 thanks

Posted 20 August 2015 - 06:45 PM

You need to have vCenter to deploy the new ASAv instance.
Without vCenter it is impossible. Even if you're able to put the vmdk drives into the virtual machine, it will show you "ERROR" and will reboot constantly.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Organization

Community

Downloads

Test Providers

Site Info


Go to top