Installing LogLogic EVA on VMware

LogLogic EVA is distributed on the TIBCO eDelivery website in the form of an .ova, compatible with VMware ESXi and VMware Workstation.

See the characteristics and limitations of LogLogic EVA on VMware.

Memory and Storage Considerations
While LogLogic EVA is running on hypervisors with slower I/O speed, the system might run into a virtual disk timeout issue, and a message might be displayed: 
mptscsih: ioc0: attempting task abort! (sc=ffff8801995d3e80)
mptscsih: ioc0: task abort: SUCCESS (sc=ffff8801995d3e80)
The solution is to create a new udev rule file /etc/udev/rules.d/98-vmware-scsi-udev.rules with the content: 
ACTION=="add", BUS=="scsi", SYSFS{model}=="*[Vv]irtual [Dd]isk*", RUN+="/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'"
Doing so increases the disk timeout period to survive the slower I/O environment. Reboot the machine after creating the file.

Prerequisites

  1. Ensure that you are using the supported version of any one of the following fully functional VMware products:
    • VMware ESXi
    • VMware Workstation

    For a complete list of supported platforms and versions, see the LogLogic EVA Readme file.

  2. Ensure that the minimum hardware requirements are met. See Minimum Hardware Requirements.
  3. Download the LogLogic EVA archive TIB_logeva_<version>_ova.zip and extract its contents. The archive includes the following files:
    • TIB_logeva_<version>.asc
    • TIB_logeva_<version>.ova
    • TIB_logeva_<version>.ova.sig
  4. The .ova ​ files in the package are unsigned and do not contain a certificate issued by TIBCO. These files can be validated using GNU Privacy Guard (GPG) 'detached signature', which is included in the package, by running the following commands:
    1. Locate the file TIB_logeva_<version>.asc.
    2. Import the public key by running the following command: 
      gpg --import TIB_logeva_<version>.asc
    3. Validate the .ova file by running the following command: 
      gpg --verify TIB_logeva_<version>.ova.sig TIB_logeva_<version>.ova

      Example output: 

      gpg: Signature made Mon 14 May 2018 05:10:23 PM EDT using RSA key ID 0AD43131
gpg: Good signature from "TIBCO LogLogic Support <support@tibco.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: DA6A 5640 4480 F326 0C9F 24FC DC39 7F08 0AD4 3131
      The actual output might vary depending on the signature of the .ova file.

Procedure

Follow the instructions provided with your VMware software to import the .ova file. Browse to select the file you downloaded.

Deploying multiple LogLogic EVA instances
When you deploy multiple LogLogic EVA instances using the same .ova file, a unique SNMP community string is configured for each instance that you deployed. This string is displayed in the Administration > System Settings > General > Inbound Polling Community String field. Before starting the upgrade to version 6.2.1 or later, you must change the default value (public) of the Inbound Polling Community String field to any other string.
Deploying on VMware ESXi version 6.5 or 6.7
In a VMware ESXi version 6.5 or 6.7 setup, if you are deploying LogLogic EVA using the GUI, an error message might be displayed mentioning that a disk (the .vmdk file) could not be found. In this scenario, you can perform one of the following steps:

Result

After performing these steps, a running virtual machine containing LogLogic EVA is installed on your system.

What to do next