Deploy The Extrahop Discover Appliance With Vmware: Virtual Machine Requirements
Deploy The Extrahop Discover Appliance With Vmware: Virtual Machine Requirements
with VMware
Published: 2018-03-15
The ExtraHop virtual appliance can help you to monitor the performance of your applications across
internal networks, the public internet, or a virtual desktop interface (VDI), including database and storage
tiers. ExtraHop can monitor application performance across geographically distributed environments such
as branch offices or virtualized environments through intra-VM traffic.
This guide explains how to deploy the following ExtraHop Discover virtual appliances on the VMware ESXi/
ESX platform:
• EDA 1000v (Monitors up to 250 devices)
• EDA 2000v (Monitors up to 1000 devices)
• EDA 6100v (Monitors up to 3000 devices)
Table 1:
©
2018 ExtraHop Networks, Inc. All rights reserved.
• Always choose thick provisioning. The ExtraHop datastore requires low-level access to the complete
drive and is not able to grow dynamically with thin provisioning. Thin provisioning can cause metric
loss, VM lockups, and capture issues.
• Do not change the default disk size on initial installation. The default disk size ensures correct
lookback for ExtraHop metrics and proper system functionality. If your configuration requires a
different disk size, contact your ExtraHop representative before you make any changes.
• Do not migrate the VM. Although it is possible to migrate when the datastore is on a remote SAN,
ExtraHop does not recommend this configuration.
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.
Network requirements
You can monitor intra-VM or external traffic with the Discover virtual appliance.
EDA 2000v One 1-Gbps Ethernet network Two to four 1-Gbps Ethernet
port is required (for management). network ports are required for
The management interface must the physical port mirror and
be accessible on port 443. management. The physical
port mirror interface must be
connected to the port mirror of the
switch. The VMware ESX server
must support network interface
drivers.
While it is possible to configure
a 10-Gbps Ethernet network port
for the port mirror interface, it is
not recommended as the virtual
appliance cannot process more
than 3 Gbps of traffic.
Note: For registration purposes, the virtual Discover appliance requires outbound DNS
connectivity on UDP port 53 unless managed by the ExtraHop Command appliance.
Deploy the OVA file through the VMware vSphere web client
ExtraHop distributes the Discover virtual appliance package in the open virtual appliance (OVA) format.
Before you begin
If you have not already done so, download the ExtraHop Discover virtual appliance OVA file for VMware
from the ExtraHop Customer Portal .
1. Start the VMware vSphere web client and connect to your ESX server.
2. Select the data center where you want to deploy the Discover virtual appliance.
3. Select Deploy OVF Template… from the Actions menu.
4. Follow the wizard prompts to deploy the virtual machine. For most deployments, the default settings
are sufficient.
a) Select Local file and then click Browse….
b) Select the OVA file on your local machine and then click Open.
c) Click Next.
d) Review the virtual appliance details and then click Next.
e) Specify a name and location for the appliance and then click Next.
f) For Disk Format, select Thick Provision Lazy Zeroed and then click Next.
g) Map the OVF-configured network interface labels with the correct ESX-configured interface labels
and then click Next.
h) 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.
5. The Discover appliance 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
Discover virtual appliance before starting the appliance.
a) Select the Summary tab.
b) Click Edit Settings, select Network adapter 1, select the correct network label from the Network
label drop-down list, and then click OK.
6. Select the Discover virtual appliance in the ESX Inventory and then select Open Console from the
Actions menu.
7. Click the console window and then press ENTER to display the IP.
Note: DHCP is enabled by default on the ExtraHop virtual appliance. To configure a static IP
address, see the Configure a Static IP Address section.
8. In VMware ESXi, configure the virtual switch to receive traffic and restart to see the changes.
enable
b) At the password prompt, type default, and then press ENTER.
c) Enter configuration mode:
configure
d) Enter the interface configuration mode:
interface
e) Run the ip command and specify the IP address and DNS settings in the following format: ip
ipaddr <ip_address> <netmask> <gateway> <dns_server>
For example:
exit
g) Save the running config file:
running_config save
h) Type y and then press ENTER.
Non-authoritative answer:
d.extrahop.com nameserver = ns0.use.d.extrahop.com.
d.extrahop.com nameserver = ns0.usw.d.extrahop.com.
1. In your browser, type the URL of the ExtraHop Admin UI, https://<extrahop_ip_address>/
admin.
Post-deployment actions
After you deploy the Discover appliance, review the Discover and Command Post-deployment Checklist
and configure additional settings.
5. In the Network Access step, select Use vSwitch0 and then click Next.
4. In the Network Access step, select Create a vSphere standard switch, ensure vmnic1 is selected,
and then click Next.
6. Click Next and then click Finish to exit the Add Network Wizard.
7. The Networking section of the configuration table for the ESX host appears as follows.
4. In the Network Access step, select Create a vSphere standard switch, ensure vmnic2 is selected,
and then click Next.
5. In the Connection Settings step, assign a unique name to the new port group (Remote Port Mirror
2, for example), click the VLAN ID drop-down menu, and select All (VLAN 4095).
6. Click Next and then click Finish to exit the Add Network Wizard.
7. The Networking section of the configuration table for the ESX host appears as follows.
Monitoring both intra-VM and external mirrored traffic to the VM (EDA 2000v or EDA
6100v)
In this scenario, you can monitor a mix of intra-VM and external mirrored traffic on up to three virtual
interfaces.
1. To monitor intra-VM traffic on one or more virtual interfaces, create a VM port group on the default
virtual switch of the ESX host for each interface as described in Monitoring Intra-VM Traffic.
2. To monitor external mirrored traffic on one or more virtual interfaces, create a physical network
interface and corresponding vSwitch for each interface as described in Monitoring External Mirrored
Traffic to the VM.
3. Click Network Adapter x and select an option from the Network label drop-down list for each
interface.
Related documentation
For information about configuring RSPAN, ERSPAN, and RPCAP to monitor remote devices, see the
following topics.
• Configure RSPAN with VMware
• Configure ERSPAN with VMware
• Configure ERSPAN with the Nexus 1000V
• Packet Forwarding with RPCAP