Deploy the ExtraHop Explore Appliance on Linux KVM
In this guide, you will learn how to deploy an ExtraHop Explore virtual appliance on a Linux kernel-based virtual machine (KVM) and to join multiple Explore appliances to create an Explore cluster. You should be familiar with basic KVM administration before proceeding.
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. |
System requirements
Your environment must meet the following requirements to deploy a virtual Explore appliance:
Important: | ExtraHop tests virtual Explore clusters on local storage for optimal performance. ExtraHop strongly recommends deploying virtual Explore clusters on continuously available, low latency storage, such as a local disk, direct-attached storage (DAS), network-attached storage (NAS), or storage area network (SAN). |
- A KVM hypervisor environment capable of hosting the Explore virtual appliance. The
Explore virtual appliance is available in the following configurations:
EXA Manager Node EXA-XS EXA-S EXA-M EXA-L 4 CPUs 4 CPUs 8 CPUs 16 CPUs 32 CPUs 8 GB RAM 8 GB RAM 16 GB RAM 32 GB RAM 64 GB RAM 4 GB boot disk 4 GB boot disk 4 GB boot disk 4 GB boot disk 4 GB boot disk 12 GB 250 GB or smaller datastore disk 500 GB or smaller datastore disk 1 TB or smaller datastore disk 2 TB or smaller datastore disk The hypervisor CPU should provide Supplemental Streaming SIMD Extensions 3 (SSSE3) support.
Note: The Explore manager node is preconfigured with a 12 GB datastore disk. You must manually configure a second virtual disk to the other EXA configurations to store record data. Consult with your ExtraHop sales representative or Technical Support to determine the datastore disk size that is best for your needs.
Note: For KVM deployments, virtio-scsi interface is recommended for the boot and datastore disks. - An Explore virtual appliance license key.
- The following TCP ports must be open:
- TCP port 443: Enables browser access to Administration settings. Requests sent to port 80 are automatically redirected to HTTPS port 443.
- TCP port 9443: Enables Explore nodes to communicate with other Explore nodes in the same cluster.
Package contents
The installation package for KVM systems is a tar.gz file that contains the following items:
- EXA-5100v-<x>.xml
- The domain XML configuration file
- EXA-5100v-<x>.xml.md5
- The domain XML checksum file
- extrahop-boot.qcow2
- The boot disk
- extrahop-boot.qcow2.md5
- The boot disk checksum file
Deploy the Explore virtual appliance
To deploy the Explore virtual appliance, complete the following procedures:
Determine the best bridge configuration
Identify the bridge through which you will access the management interface of your Explore appliance.
- Make sure the management bridge is accessible to the Explore virtual appliance and to all users who must access the management interface.
- If you need to access the management interface from an external computer, configure a physical interface on the management bridge.
Edit the domain XML configuration file
After you identify the management bridge, edit the configuration file, and create the Explore virtual appliance.
Create the datastore disk
Create the datastore disk so that the allotted space is large enough to store the type of records you want to store for the amount of lookback desired.
(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.
Configure the Explore appliance
After you obtain the IP address for the Explore appliance, log in to the appliance through https://<explore_ip_address>/admin and complete the following recommended procedures.
Note: | The default login username is setup and the password is default. |
- Register your ExtraHop system
- Connect the Discover and Command appliances to Explore appliances
- Send record data to the Explore appliance
- Review the Explore Post-deployment Checklist and configure additional Explore appliance settings.
Create an Explore cluster
For the best performance, data redundancy, and stability, you must configure at least three Explore appliances in an Explore cluster.
Important: | If you are creating an Explore cluster with six or more nodes, you must configure the cluster with manager nodes. For manager node instructions, see Deploying manager nodes. |
In the following example, the Explore appliances have the following IP addresses:
- Node 1: 10.20.227.177
- Node 2: 10.20.227.178
- Node 3: 10.20.227.179
You will join nodes 2 and 3 to node 1 to create the Explore cluster. All three nodes are data nodes. You cannot join a data node to a manager node or join a manager node to a data node to create a cluster.
Important: | Each node that you join must have the same configuration (physical or virtual) and the same ExtraHop firmware version. EXA 5100 and EXA 5200 physical appliances can be in the same cluster. |
Before you begin
You must have already installed or provisioned the Explore appliances in your environment before proceeding.Connect the Explore appliance to Discover and Command appliances
After you deploy the Explore appliance, you must establish a connection from all ExtraHop Discover and Command appliances to the Explore appliance before you can query records.
Important: | Connect the Discover appliance to each Explore node so that the Discover appliance can distribute the workload across the entire Explore cluster. |
Note: | If you manage all of your Discover appliances from a Command appliance, you only need to perform this procedure from the Command appliance. |
Send record data to the Explore appliance
After your Explore appliance is connected to all of your Discover and Command appliances, you must configure the type of records you want to store.
Thank you for your feedback. Can we contact you to ask follow up questions?