If you have servers, you can choose between two agent versions: Software or Virtual Appliance. The Software version is ideal if you are familiar with Linux and want to run the agent on your favorite distribution. In that case, you are in charge of updating the OS and we are in charge of updating the agent software.
If you don't want to manage your Linux VM and you have access to a virtualized environment, the Virtual Appliance is perfect for you. In that case, we are both in charge of the OS updates and the agent software updates.
Latest release: 2.46.0-rev1
- Hyper-V: https://download.obkio.com/disks/obkio-agent-2.46.0-rev1.img.vhd.zip
- KVM: https://download.obkio.com/disks/obkio-agent-2.46.0-rev1.img.qcow2.zip
- VirtualBox: https://download.obkio.com/disks/obkio-agent-2.46.0-rev1.img.vdi.zip
- VMware: https://download.obkio.com/disks/obkio-agent-2.46.0-rev1.img.vmdk.zip
- XEN: https://download.obkio.com/disks/obkio-agent-2.46.0-rev1.img.qcow2.zip
Important: The image is not an installation CD (.iso) but a fully bootable disk image that must be configured as an IDE (preferred) or SATA but not SCSI. After the initial boot, the image must ONLY be used on that VM.
Once installed, there is no need to upgrade the Virtual Appliance Agent. Our systems will take care of updating both the underlying OS and the agent software itself.
- CPU: 2 vCPU
- Memory: 2 GB
- Disk: 8 GB
- Network Config: DHCP (see below for static IP configuration)
- Download the VM Disk corresponding to your virtualization environment and unzip it (see the download links above).
- Create a new VM. For Hyper-V, select Generation 1 and for the OS type, select Linux Kernel 4.x (64-bits). For VMware, the Guest OS Family must be Linux and the OS Version Other 3.x or later Linux (64-bits).
- When you setup the disks, do not create a new disk but use the downloaded disk image. Once you boot on the disk, you can not reuse it with another VM. If you want to install multiple agents, make a copy before you boot on it.
- Make sure the disk is configured as IDE (preferred) or SATA but not SCSI.
- For VMware, make sure the Network Adapter Type is e1000e (preferred) or e1000.
- Boot the VM.
- You should see a line at the bottom starting with Obkio Agent with a Serial Number and a UUID. Send that information to email@example.com (or use the Chat Box at the bottom right of this page) and our team will associate the Virtual Appliance with the agent you want in the App. This step will be integrated in the App in the next releases.
We can manually create an image with the static IP configuration. We need to have the following info:
- IP Address
- Default Gateway
- DNS Servers
- Image Type (VMware? Hyper-V?)
Send that information to firstname.lastname@example.org (or use the Chat Box at the bottom right of this page) and our team will create the image for you usually within 24h.
If you want to reinstall the agent on another infrastructure, you can simply delete the old VM and install a new one. Then, you can Dissociate the Virtual Appliance from the agent in the App and Associate it with the new VM.
If at boot time you have errors unrecognized disk label or No such file or directory while trying to open /dev/disks/by-label... make sure the disk is configured as IDE (preferred) or SATA and not SCSI.
If the boot process stops at Started Update UTMP about System Runlevel Changes (like the screenshot below), this means that the VM is not able to connect to the cloud. Make sure you have DHCP enabled on the network, that you are using e1000 or e1000e network card on VMware and that your firewall is not blocking outbound access to our cloud systems.