Deploy the ETA 9350 packetstore
This guide explains how to install the rack-mounted ETA 9350 packetstore.
Installation prerequisites
Important: | For maximum performance and compatibility, deploy sensors and packetstores in the same datacenter. |
- Packetstore
- 1U of rack space and electrical connections for 2 x 800 W power supplies.
- Management
- One 10/100/1000BASE-T network port or one 10GBASE-SR port for packetstore management.
- Monitoring (capture)
- Traffic feeds must be compatible with the port options on the packetstore, such as two 25GBASE-SR connections. For more information about these ports, see Rear panel ports.
- Network Access
- TCP 443 must be open between the packetstore and any connected console or sensors, including any system that connects to the ExtraHop system for administration.
For more information about the interfaces on the ExtraHop system, see the ExtraHop Hardware FAQ.
To install the Extended Storage Unit (ESU) for this packetstore, your environment must meet the following requirements:
- MD2412 ESU
- 2U of rack space and electrical connections for 2 x 800 W AC power supply units.
- MD2460 ESU
- 4U of rack space and electrical connections for 2 x 1500 W AC power supply units; requires high line 200-240 VAC.
For more information about ESUs, see Hardware specifications and compatibility.
Rear panel ports
ETA 9350
- Power supply unit (PSU1) to connect the packetstore to an AC power source.
- Two 25 GbE-capable ports on one network adapter. Ports 5 and 6 are the high-performance monitoring (capture) interfaces.
- Four SAS ports to connect extended storage units (ESU).
Note: You cannot connect older ESUs to this packetstore. For more information about ESU compatibility, see Hardware specifications and compatibility. - One RS-232 serial port to connect a console device.
- Power supply unit (PSU2) to connect the packetstore 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.
- Two 10 GbE ports. Ports 3 and 4 can be configured as a management port or as a
management and RPCAP/ERSPAN/VXLAN/GENEVE target.
Note: These ports also function as high-performance monitoring (capture) interfaces. Processing RPCAP, ERSPAN, VXLAN, and GENEVE traffic is limited to 1 Gbps per interface in "Management + RPCAP/ERSPAN/VXLAN/GENEVE" modes, but the ports support up to 10 Gbps per interface in Monitoring and High-Performance ERSPAN/VXLAN/GENEVE target modes. - Two 10/100/1000BASE-T network ports. Port 1 is the primary management port. Both ports can be configured as a monitoring port, management port, or as a management and RPCAP/ERSPAN/VXLAN/GENEVE target.
For more information about the high-performance capture interfaces on the ExtraHop system, see the ExtraHop Hardware FAQ.
Supported packet source connectivity
Connector | Peer Connector for Packet Source | Customer-Supplied Cabling | Supported Operating Speeds |
---|---|---|---|
Transceiver-based Connectivity | |||
25 GbE SFP28 SR transceiver | 25 GbE SFP28 SR transceiver | Multi-mode fiber LC connectors |
25 Gbps, 10 Gbps |
10 GbE SFP+ SR transceiver | Multi-mode fiber LC connectors |
10 Gbps | |
10 GbE SFP+ SR transceiver | 10 GbE SFP+ SR transceiver | Multi-mode fiber LC connectors |
10 Gbps |
10 GbE SFP+ SR transceiver | 10 GbE SFP+ SR transceiver | Multi-mode fiber LC connectors |
10 Gbps |
Direct Attach Connectivity | |||
Customer-supplied SFP28 DAC cable, such as the Mellanox MCP2M00-Axxx series | 25 Gbps | ||
Customer-supplied RJ45 Ethernet cable | 1 Gbps |
Packetstore throughput
The ETA 9350 packetstore supports a maximum of four standard density (MD2412) ESUs or one high density (MD2460) ESU. You can increase the number of standard density ESUs connected to the ETA 9350 packetstore to increase the available throughput.
Number of ESUs | ETA 9350 with MD2412 | ETA 9350 with MD2460 |
---|---|---|
1 | 10 Gbps | 50 Gbps |
2 | 25 Gbps | x |
4 | 50 Gbps | x |
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 a static IP address through the LCD
Configure an IP address through the CLI
Before you begin
You can access the CLI by connecting a USB keyboard and SVGA monitor to the 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.You can manually configure an IP address from the CLI.
(Optional) Configure the 10 GbE management interface
You can configure a 10 GbE port (port 1 or port 2) to manage the system. The commands below move the settings from port 3 to port 1 and then disables port 3. Alternatively, you can configure the 10 GbE management interface in the Administration settings.
Configure the packetstore
Open a web browser and log in to the Administration settings on the ExtraHop system through https://<extrahop-hostname-or-IP-address>/admin with the setup user account. The password is the system serial number that appears in the Info section of the LCD display and on the label on the back of the packetstore.
- Register your ExtraHop system
- Connect sensors and console to the packetstore
- Review the ExtraHop Post-deployment Checklist and configure additional packetstore settings.
Verify the configuration
After you have deployed and configured the packetstore, verify that packets are being collected.
Before you begin
You must have a minimum user privilege of view and download packets to perform this procedure.
Thank you for your feedback. Can we contact you to ask follow up questions?