Deploy the ExtraHop Command Appliance on Linux KVM
This document provides information on how to install the ExtraHop Command virtual appliance on a Linux kernel-based virtual machine (KVM). This guide assumes that you are familiar with basic KVM administration.
If you have not already done so, download the ExtraHop Command virtual appliance file for KVM from the ExtraHop Customer Portal.
Important: | If you want to deploy more than one ExtraHop virtual appliance, create the new instance with the original deployment package or clone an existing instance that has never been started. |
Requirements
Before you can install the ExtraHop virtual appliance, make sure that your environment meets the following requirements:
- A KVM hypervisor environment capable of hosting a VM that has:
- 4 GB RAM
- Two vCPUs.
- One 4 GB boot disk (virtio-scsi interface recommended)
- One 40 GB datastore disk (virtio-scsi interface recommended)
The hypervisor CPU should provide Supplemental Streaming SIMD Extensions 3 (SSSE3) support.
- An ExtraHop virtual appliance license key
Performance guidelines
The following table provides guidelines that can help you optimize the performance of the Command appliance. These guidelines are minimum requirements that you might need to adjust based on the size and needs of your environment.
Scalability | Connected ExtraHop Appliances | 1-8 | 9-24 | 25-64 |
Provisioning Requirements | CPU Cores | 4 | 8 | 16 |
RAM | 8 GB | 16 GB | 32 GB | |
Boot Disk | 4 GB | 4 GB | 4 GB | |
Datastore and Utility Disk | 40 GB | 48 GB | 64 GB | |
Disk Total | 44 GB | 52 GB | 68 GB |
Package contents
The installation package for KVM systems is a tar.gz file that contains the following items:
- eca.xml
- The domain XML configuration file
- eca.xml.md5
- An MD5 checksum file to verify the integrity of the eca.xml file.
- extrahop-boot.qcow2
- The boot disk
- extrahop-boot.qcow2.md5
- An MD5 checksum file to verify the integrity of the extrahop-boot.qcow2 file.
- extrahop-data.qcow2
- The datastore disk
- extrahop-data.qcow2.md5
- An MD5 checksum file to verify the integrity of the extrahop-data.qcow2 file.
Edit the domain XML configuration file
Edit the configuration file and create the ExtraHop virtual appliance.
(Optional) Configure a static IP address
By default, ExtraHop systems ship with DHCP enabled. If your network does not support DHCP, you must configure a static address manually.
Post-deployment actions
Log in to the ExtraHop system with the setup user account and type default for the password.
- Review the Discover and Command Post-deployment Checklist and configure additional Command settings.
- Connect a Command appliance to Discover appliances
- Connect the Discover and Command appliances to Explore appliances
- Connect the Discover and Command appliances to the Trace appliance
Thank you for your feedback. Can we contact you to ask follow up questions?