Installing Enterprise Agent on VirtualBox

This article describes how to set up the ThousandEyes Enterprise Agent using the Virtual Appliance OVA with VirtualBox. To download, VirtualBox visit https://www.virtualbox.org.

See the installation guides for VirtualBox:

For your convenience, ThousandEyes provides an image of a virtual machine with the Enterprise Agent installed in OVA (Open Virtual Appliance) format, which is updated bi-weekly. Hence, we strongly recommend that you download a recent image for new Enterprise Agent installations. If your prefer more granular control of the your Enterprise Agent and the underlying operating system, we recommend you deploy the Enterprise Agent using the Linux Package method.

Step-by-Step Guide

To install the ThousandEyes Virtual Appliance, do the following:

  1. To download the most recent Enterprise Agent image, begin by navigating to Agents > Enterprise Agents (thousandeyes-va-<version>.ova).

  2. Click Add New Enterprise Agent.

  3. The Add New Enterprise Agent button reveals the installation options available for the Enterprise Agent. These instructions cover deployment using the OVA package. Select Download - OVA to get the latest version.

  4. Once the image is downloaded, open the VirtualBox application and click File > Import Appliance. The screenshot below is of VirtualBox version 5.2.20 r125813 (Qt5.6.3) on macOS Mojave. Depending on your operating system and version, what you see might have minor differences.

  5. Click Browse and select the downloaded virtual appliance image.

  6. Once the image is selected, click Continue.

  7. The Appliance settings menu displays. Many options are preconfigured. However, the following options can be re-configured:

    • Name of the VM

    • CPU count

    • RAM

    • Hard disk space

    • Network interface

    The agent is designed to operate with the specifications listed in Enterprise Agent Hardware Requirements. If you choose settings higher than the recommended specifications, there are no additional benefits to the performance of the Enterprise Agent. However, performance will be degraded if you choose settings below the recommendations. Once you've finished making changes, click Import.

  8. Wait for the appliance to be imported and visible in the VirtualBox Manager window. Once the import is complete (8), double-click the new machine to start.

  9. Once the machine boots up, a welcome screen displays the default values for the virtual appliance's IP address, username, and password. The virtual appliance's IP address is obtained via DHCP by default. If you are not using DHCP, you can configure a static IP by pressing N and following the interactive setup wizard. The available network configuration options are the following:

    • Hostname

    • IPv4/IPv6

    • DNS

    To reset the virtual appliance password to the default value, press R. You can access the Web UI at https://<Virtual Appliance IP address>. Access can be upgraded to HTTPS by following the steps mentioned here.

  10. To open the web UI, open a web browser and enter the URL displayed on the welcome screen. Once you are at the URL, enter the default username and password. Then click Login. You will be prompted to change the default password. Enter the current and new passwords, then click Change Password.

  1. Obtain the account group token as guided here. Navigate to the Agent tab in the web UI. Enter the account group token in the Account Group Token field; then click Save Changes.

  1. The browser is now redirected to the Review page. Click Complete to finish setup.

  1. If the Review page shows all checks green as in the screenshot above, your Enterprise Agent is now ready to run tests. The newly added Enterprise Agent will appear in the Settings > Enterprise Agents window, as seen below:

Basic Troubleshooting

  • If your VM displays just a black screen, virtualization might be disabled or not available. On windows, you can confirm this using these instructions

  • If the path visualization appears broken or incomplete, this might be due to NAT. For a detailed explanation of this case, see this article

Last updated