This article will go over how to install CVX on a vCenter 6 appliance. Starting from vCenter 6, there was a change in the OVFTool built into vCenter that changes the SHA hashing algorithm from 1 to 256. There is also an issue with 6.5 where it is required to go into the BIOS of the CVX vm and change the boot order from HDD to CD.
The vEOS image (whethere as a vEOS-lab, vEOS for vRouter functionality in Amazon Web Services or Microsoft Azure, or vEOS-lab for labbing) contains two files. First, the *.iso file is the Aboot file required as the first bootable device using IDE. Second, the *.vmdk file is used as the actual HDD for the vm, and should be set as secondary IDE.
These steps will outline a few issues we have found in the field when deploying vEOS and the resolutions.
CVX Deployment Instructions
To install CVX, obtain a copy of the vmdk file as well as the Aboot iso from Arista.com > Software Downloads.
You will need to change OS type to Linux and the OS to “Other Linux (64-bit)” as well as the VM compatibility to vCenter/ESXi 5.5. You must also change the RAM size to at least 2 GB and CPU to 4. You can delete the SCSI disk as we will upload the vmdk as an IDE. You must also change the CD drive to an IDE over SCSI. Optionally you may add multiple NICs to the CVX vm.
Received an “OVF package is invalid and cannot be deployed” when using an OVF method of installation
You may also receive from your SE the CVX in an OVF format instead of vmdk/iso files. When uploading an OVF, you may get this error below stating “The OVF package is invalid and cannot be deployed. The following manifest file entry is invalid”
This is due to the change of OVFTool from 1 to 256. To workaround this error, you can follow the solution found on VirtuallyGhetto blog and edit the manifest file.
After changing this, you will now be able to import the OVF.
VM keeps rebooting, showing “This is not a bootable disk. Please insert a bootable floppy and press any key to try again..
To workaround this issue, go into the VM Options for the CVX vm and under Boot Options, check off Force BIOS setup to boot straight into the vm’s BIOS instead of the disk.
Browse to the Boot menu and move the CD-ROM Drive as the first bootable disk and press F10 to save.
The vm will now boot properly.
We hope that these steps here will be helpful for users deploying not only CVX, but also vEOS-lab images as well. Should you have any other issues, please get in touch with your local SE, or leave a comment in the section below.
This post is a post that I originally wrote for Arista EOS Central – find the original link here.