Deploy an ExtraHop sensor on Linux KVM
The following procedure guides you through the deployment process of the ExtraHop EDA 1000v or EDA 2000v virtual sensor on a Linux kernel-based virtual machine (KVM). You should be familiar with basic KVM administration before proceeding.
If you have not already done so, download the ExtraHop virtual sensor file for KVM from the ExtraHop Customer Portal.
Important: | If you want to deploy more than one ExtraHop virtual sensor, create the new instance with the original deployment package or clone an existing instance that has never been started. |
Virtual machine requirements
Your KVM hypervisor must be able to support the following specifications for the virtual sensor.
Sensor | vCPU | RAM | Disk |
---|---|---|---|
EDA 1000v | 2 | 4 GB |
|
Reveal(x) EDA 1100v | 2 | 4 GB |
|
EDA 2000v | 6 | 6 GB |
|
The hypervisor CPU should provide Streaming SIMD Extensions 4.2 (SSE4.2) and POPCNT instruction support.
Note: | If you want to enable packet captures, configure an additional storage disk during deployment. Refer to your vendor documentation to add a disk. |
Package contents
The installation package for KVM systems is a tar.gz file that contains the following files:
Description | EDA 1000v | Reveal(x) 1100v | EDA 2000v |
---|---|---|---|
Domain XML configuration file | eda-1000v.xml | eda-1100v.xml | eda-2000v.xml |
Domain XML checksum file | eda-1000v.xml.md5 | eda-1100v.xml.md5 | eda-2000v.xml.md5 |
Boot disk | extrahop-boot.qcow2 | extrahop-boot.qcow2 | extrahop-boot.qcow2 |
Boot disk checksum file | extrahop-boot.qcow2.md5 | extrahop-boot.qcow2.md5 | extrahop-boot.qcow2.md5 |
Datastore disk | extrahop-data.qcow2 | extrahop-data.qcow2 | extrahop-data.qcow2 |
Datastore disk checksum file | extrahop-data.qcow2.md5 | extrahop-data.qcow2.md5 | extrahop-data.qcow2.md5 |
Determine the best bridge configuration
Gather information about your network to determine the best virtual bridge configuration.
Create the virtual capture bridge
Before you enable packet capture by an ExtraHop virtual sensor, you must create a virtual bridge that is set to promiscuous mode. If you want to capture traffic from an external network, you must add a physical interface to the bridge, and that interface must be also be set to promiscuous mode.
The following procedure describes how to create a virtual bridge with Open vSwitch. For information on how to create a virtual bridge with the built-in Linux bridge, refer to the documentation for your KVM system.
Edit the domain XML configuration file
After you create your virtual bridge, edit the configuration file, and create the ExtraHop virtual sensor.
Configure a mirror session on the capture bridge
This procedure explains how to configure a mirror session on an Open vSwitch virtual bridge.
Before you begin
Important: | To ensure the best performance for initial device synchronization, connect all sensors to the console and then configure network traffic forwarding to the sensors. |
Start the VM
After you have created your ExtraHop virtual sensor, you can log in to the management interface through a web browser to apply your license key, see network traffic, and customize your sensor configurations.
(Optional) Configure a static IP address
By default, the ExtraHop system is configured with DHCP enabled. If your network does not support DHCP, you must configure a static address manually.
Configure the sensor
After you configure an IP address for the sensor, open a web browser and navigate to the ExtraHop system through the configured IP address. Accept the license agreement and then log in. The default login name is setup and the password is default. Follow the prompts to enter the product key, change the default setup and shell user account passwords, connect to ExtraHop Cloud Services, and connect to an ExtraHop console.
After the system is licensed, and you have verified that traffic is detected, complete the recommended procedures in the post-deployment checklist.
Thank you for your feedback. Can we contact you to ask follow up questions?