We’ve just had quite the head scratcher trying to install the ISE 2.3 OVA on ESXi 6.5 and figured we won’t be the only ones.
Tl;dr – Convert the OVA to VMX then convert that VMX to OVF. Do not go directly from OVA to OVF.
*Edit* 26/11/2018 – Can confirm this works for ISE 2.4 on ESXi 6.7 which I tested in my home lab. Make sure you use separate folders to convert each step below or your VMDK file will get overwritten on the last step and ruin it. Thanks to crystal for pointing that out.
The OVA can’t be deployed as.. an OVA
Yep. The install file provided by Cisco needs to be converted to a different format in order to work with VMware i.e. OVF.
The error message when attempting this:
3.5: ATTRIBUTE_REQUIRED: Attribute “id” is required.
3.5: ATTRIBUTE_REQUIRED: Attribute “href” is required.
15.3: ATTRIBUTE_REQUIRED: Attribute “id” is required.
To be fair this is partly documented by Cisco but it doesn’t clear much up on what to do next.
The ISE 2.3 OVA templates are not compatible with VMware web client for vCenter 6.5. As a workaround, use the VMware OVF tool to import the OVA templates.
Download VMware OVF Tool
For ISE 2.3 on to ESXi 6.5 I used OVF Tool version 4.2
You can convert directly from OVA to OVF but we encountered the error below after doing this and importing to ESXi. A senior colleague saved my bacon by saying they’d had luck going from OVA to VMX then to OVF.
4:5: PARSE_ERROR: Parse error: Unexpected character ‘.’ (code 58) (missing namespace prefix?) at [row,col,system-id]: [4,11,”descriptor.ovf”].
Convert OVA -> VMX
- Install the OVF Tool
- Place your OVA somewhere easily accessible (C:) and open up elevated command prompt.
- Navigate to cd C:\Program Files\Vmware\Vmware OVF Tool
- Initiate the executable in the format ovftool.exe “source file” “destination file” e.g. ovftool.exe “C:\ISE-188.8.131.528-virtual-SNS3415-600.ova” “C:\ISE-184.108.40.2068-virtual-SNS3415-600.vmx”
- The above will convert from the OVA to the VMX in the same directory of C:
Once complete you will see both the original OVA and the two new VMX/VMDK files
Convert VMX -> OVF
Now that VMX can be converted to OVF. Note you can choose not to use the quotations like in this example as long as there’s a space between source and destination. I created an OVF directory so that it didn’t overwrite any files during this process.
ovftool.exe C:\ISE-220.127.116.118-virtual-SNS3415-600.vmx C:\OVF\ISE-18.104.22.1688-virtual-SNS3415-600.ovf
You will end up with three files in your OVF directory and the OVF can be used for the import to ESXi.
Import to ESXi
This time there is no error on the import and the resources are automatically filled out via the OVF template.
Additional Note Feb 2018 from Frank (comments below):
“When deploying in VMware, I needed to select both the converted OVF-file and the VMDK-file. When selecting only OVF-file, VMware said that files where missing.”