Deploy the EDA 8320 sensor
This guide explains how to install the rack-mounted EDA 8320 sensor.
This installation enables you to run network performance monitoring, network detection and response, and intrusion detection on a single sensor.
Note: | If you have enabled the IDS module on this sensor, and your ExtraHop system does not have direct access to the Internet and access to ExtraHop Cloud Services, you will need to upload IDS rules manually. For more information, see Upload IDS rules to the ExtraHop system through the REST API. |
Installation prerequisites
To install the sensor, your environment must meet the
following requirements:
- Sensor
- 1U of rack space and electrical connections for 2 x 800 W power supplies.
- Management
- One 10/100/1000 BASE-T network port or one 10G BASE-SR port for sensor management.
- Network Access
- Ensure that administrators can access the Administration settings on the sensor over TCP port 443.
- Configure your firewall rules to allow outbound access over port 443 to ExtraHop Cloud Services.
For more information about the interfaces on the ExtraHop system, see the ExtraHop Hardware FAQ.
Rear panel ports
EDA 8320
- Power supply unit (PSU1) to connect the sensor to an AC power source
- Two 25 GbE-capable ports on two network adapters
- One RS-232 serial port to connect a console device
- Power supply unit (PSU2) to connect the sensor to an AC power source
- One VGA port to connect an external display
- Two USB 3.0 ports to connect input devices such as a keyboard and mouse
- One iDRAC interface port
- Four 10/100/1000 BASE-T network ports. Ports 1 and 2 can be configured as a
management port or a management and RPCAP/ERSPAN/VXLAN/GENEVE target.
Tip: In environments with asymmetric routing adjacent to the high-performance interfaces, ping replies might not get back to the sender.
Supported packet source connectivity
The sensor accepts packets through ports 1 to 6. Connect the ports according to the
table below.
Traffic distribution guidelines
- Packets from the same flow should be received on the same interface, or on interfaces of the same network interface card (NIC).
- The ingest on each NIC should not exceed 75% of the rated analysis throughput for the sensor to ensure that traffic is balanced across system resources.
- If your data feed does not require both interfaces on the NIC, disable the unconfigured interfaces in the Administration settings. For example, configure the sensor with a single interface to ingest 50 Gbps on each NIC. Disable the extraneous ports on each NIC. This configuration optimizes performance for 100 Gbps.
- A single high-performance ERSPAN target is expected to process 20 to 30 Gbps. On larger sensors, distribute ERSPAN traffic to more interfaces to scale traffic ingest.
Management IP address configuration
DHCP is enabled by default on the ExtraHop system. When you power on the system, the primary management interface attempts to acquire an IP address through DHCP. If successful, the IP address appears on the home screen of the LCD.
If your network does not support DHCP, you can configure a static IP address through the LCD menu on the front panel or through the command-line interface (CLI).
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. |
Configure the sensor
Next steps
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?