Deploy an ExtraHop recordstore with Hyper-V
The following procedures explain how to deploy the ExtraHop virtual recordstore on the Microsoft Hyper-V platform. You must have experience administering your hypervisor product to complete these procedures.
Virtual machine requirements
You must have an existing installation of Hyper-V on Windows Server 2012 or later capable of hosting the virtual recordstore. In addition, you need Hyper-V Manager to manage the virtual machine.
Important: | ExtraHop tests virtual clusters on local storage for optimal performance. ExtraHop strongly recommends deploying virtual 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). |
The following table provides the server hardware requirements for the recordstore.
vCPUs | Memory | Datastore disk |
---|---|---|
4 | 8 GB RAM | 150 GB to 250 GB |
8 | 16 GB RAM | 150 GB to 500 GB |
16 | 32 GB RAM | 150 GB to 1 TB |
32 | 64 GB RAM | 150 GB to 2 TB |
The hypervisor CPU should provide Streaming SIMD Extensions 4.2 (SSE4.2) and POPCNT instruction support.
Note: | When you deploy a recordstore, you must create a second virtual disk, which is required to store record data. The minimum datastore disk size for all configurations is 150 GB. Consult with your ExtraHop sales representative or ExtraHop Support to determine the datastore disk size that is best for your needs. |
Import the ExtraHop virtual machine
Before you begin
If you have not already done so, download the ExtraHop firmware file for Hyper-V from the ExtraHop Customer Portal and extract the contents from the .zip file to your Windows Server.Create a datastore disk
Create a virtual hard disk (VHDX) for each recordstore that you plan to deploy.
Configure memory and processor settings
Configure the amount of memory and virtual processors allocated to the recordstore based on the virtual machine requirements table above.
- In the Virtual Machines list, right-click the recordstore, and then click Settings.
- In the Hardware section, click Memory.
- In the Startup RAM field, type the amount of memory you want to assign to the recordstore.
- Click Apply.
- In the Hardware section, click Processor.
- In the Number of virtual processors field, specify the number of vCPUs you want to assign to the recordstore.
- Click Apply.
- Click OK.
- Repeat steps 1-8 for each additional recordstore you are deploying.
Start the virtual machines
- In the Virtual Machines list, right-click the virtual machine, and then select Start.
- Right-click the virtual machine again and select Connect.
- At the login prompt, type shell, and then press ENTER.
- At the password prompt, type default, and then press ENTER.
- Type show ipaddr and then press ENTER to display the IP address and netmask of the recordstore. If you need to configure a static IP address, see Configure a static IP address through the CLI.
- Repeat steps 1-5 for each additional recordstore you are deploying.
Configure a static IP address through the CLI
The ExtraHop system is configured by default with DHCP enabled. If your network does not support DHCP, no IP address is acquired, and you must configure a static address manually.
Important: | We strongly recommend configuring a unique hostname. If the system IP address changes, the ExtraHop console can re-establish connection easily to the system by hostname. |
- Access the CLI through an SSH connection, by connecting a USB keyboard and SVGA monitor to the physical ExtraHop appliance, or through an RS-232 serial (null modem) cable and a terminal emulator program. Set the terminal emulator to 115200 baud with 8 data bits, no parity, 1 stop bit (8N1), and hardware flow control disabled.
- At the login prompt, type shell and then press ENTER.
- At the password prompt, type default, and then press ENTER.
-
To configure the static IP address, run the following commands:
Configure the recordstore
Next steps
After the system is licensed, complete these recommended procedures:- Register your ExtraHop system
- Review the Recordstore Post-deployment Checklist and configure additional recordstore settings.
- Create a recordstore cluster
- Connect the recordstore to a console and all sensors
- Send record data to the recordstore
Thank you for your feedback. Can we contact you to ask follow up questions?