The ExtraHop Command appliance (ECA) is a virtual appliance that provides centralized management and reporting across multiple ExtraHop appliances distributed across datacenters, branch offices, and the public cloud. For most large ExtraHop deployments, a dedicated ECA is the most efficient way to manage and report across the remote nodes.
The following procedures explain how to deploy an ExtraHop Command appliance with the vSphere client running on a Windows machine. You must have experience administering your VMware ESX and ESXi environments to complete these procedures.
You must have an existing installation of VMware ESX/ESXi server version 5.0 or later capable of hosting the Command virtual appliance. In addition, you need a vSphere client to deploy the OVF file and to manage the virtual machine.
The ECA is distributed as an OVA package that includes a preconfigured virtual machine (VM) with a 64-bit, Linux-based OS that is optimized to work with VMware ESX and ESXi version 4.0 and later.
- 2 CPUs
- 4 GB RAM
- One 4 GB disk
- One 40 GB disk
- One bridged network interface
|Note:||You might need to adjust the preconfigured virtual appliance to scale to your environment. For more information, see the Performance guidelines section.|
The following ESX/ESXi server hardware is required:
- One Intel processing core with hyper-threading support, VT-x technology, and a processing speed of 2.5 GHz or higher
- 4 GB or higher
- 44 GB or higher
- One 1 Gbps Ethernet network port
- Place in network
- Near one of the managed ExtraHop appliances, but accessible on port 443 to all managed ExtraHop appliances
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||ExtraHop Nodes||1-4||5-16||17-64||65 or more|
|Provisioning Requirements||CPU Cores||2||4||8||16|
|RAM||4 GB||8 GB||16 GB||24 GB|
|Boot Disk||4 GB|
|Datastore Disk||32 GB + (Size of RAM x 2)
For example, if you provision the appliance with 16 GB of RAM, the disk requirement is 64 GB.
|Disk Total||36 GB + (Size of RAM x 2)|
- If you have not already done so, download the ExtraHop Command appliance firmware file for VMware from the ExtraHop Customer Portal.
- Start the VMware vSphere client and connect to your ESX server.
- Go to the File menu and select Deploy OVF Template.
Follow the Virtual Machine wizard prompts to deploy the virtual machine. For
most deployments, the default settings are sufficient.
- Browse to the location of the downloaded OVA file, select the file, and then click Next.
- Review and verify the OVF template details and click Next.
- Type the VM name and location. Give the VM a unique and specific name for the ESX Inventory and then click Next.
- For Disk Format, select Thick Provision Lazy Zeroed and then click Next.
- Map the OVF-configured network interface labels with the correct ESX-configured interface labels and then click Next.
Verify the configuration, select the Power on after
deployment checkbox, and then click
Finish to begin the deployment.
When the deployment is complete, you can see the unique name you assigned to the ExtraHop VM instance in the inventory tree for the ESX server to which it was deployed.
The ECM contains a preconfigured bridged virtual interface with the network
label, VM Network. If your ESX has a different interface
label, you must reconfigure the network adapter on the ECM virtual appliance
before starting the appliance.
- Select the Summary tab.
- Click Edit Settings, select Network adapter 1, select the correct network label from the Network label drop-down list, and then click OK.
- Click the Command virtual appliance in the ESX Inventory and then select the Console tab.
- Click the console window and then press ENTER to display the login prompt.
- Log in with the shell user account and the password default.
Run the show ipaddr command to display the IP address of
Note: If you need to manually configure an IP address, see the Configure a static IP address section.
- Press CTRL+ALT+DELETE to exit the window.
The ExtraHop virtual appliance is delivered with DHCP enabled. If your network does not support DHCP, no IP address is acquired, and you must configure a static address manually. To configure a static IP address, complete the following steps:
- Log in to the console with the shell user account. At the password prompt, type default, and then press ENTER.
To configure the static IP address, run the following commands:
Enable privileged commands:
- At the password prompt, type default, and then press ENTER.
Enter configuration mode:
Enter the interface configuration mode:
Run the ip command and specify the IP address and
DNS settings in the following format: ip ipaddr <ip_address>
<netmask> <gateway> <dns_server>
ip ipaddr 10.10.2.14 255.255.0.0 10.10.1.253 10.10.1.254
Leave the interface configuration section:
Save the running config file:
- Type y and then press ENTER.
- Enable privileged commands:
Complete the following steps to apply a product key supplied by ExtraHop Support.
If you do not have a product key, contact firstname.lastname@example.org.
- In your browser, type the IP address of the ExtraHop appliance (https://<extrahop_ip_address>/admin).
- Review the license agreement, select I Agree, and then click Submit.
- On the login screen, type setup for the username.
For the password, select from the following options:
- For a physical appliance, type the service tag number found on the
pullout tab on the front of the appliance.
Note: The serial number for the EDA 1100 is located on the bottom of the appliance, and displayed in the Appliance info section of the LCD menu.
- For a virtual appliance, type default.
- For a physical appliance, type the service tag number found on the pullout tab on the front of the appliance.
- Click Log In.
- In the System Settings section, click License.
- Click Manage License.
- Click Register.
- Enter the product key and then click Register.
- Click Done.