Connect the EXA 5300 to the ExtraHop system

After you deploy an EXA 5300 recordstore, you must establish a connection from all ExtraHop sensors and the console to the recordstore nodes before you can query for stored records.

Here are some important considerations about recordstore connections:

  • You cannot connect sensors and consoles to more than one EXA 5300.
  • If a sensor or console is connected to an EXA 5200 or EXA 5100v, you must disconnect from the EXA 5200 or EXA 5100v before you can connect to an EXA 5300.

Recordstore partitions

The EXA 5300 organizes data by table partitions. The Recordstore Status page includes a Partition Summary section that lists all partitions, including the data for a specific table for a selected date.

Older records are deleted automatically when the disk is full, but you can also delete partitions manually from the system, if needed. On the Recordstore Status page, select one or more partitions and click Delete Selected. If you delete a partition, any record searches will not return records from that partition for that date. Partition deletion operations are captured in the audit log.

Generate a token on the EXA 5300

The EXA 5300 recordstore connects to an ExtraHop console with token-based authentication.

Generate a token on the EXA 5300 recordstore before beginning the connection procedure on the console.
  1. Log in to the Administration settings on the ExtraHop system through https://<extrahop-hostname-or-IP-address>/admin.
  2. In the Connected Appliance Administration section, under Recordstore Settings, click Generate Token.
  3. Click Generate Token.
  4. Copy the token and continue to the next procedure.

Connect the EXA 5300 to a console or sensor

Connect the EXA 5300 recordstore to an ExtraHop console or sensor.

Important:EXA 5300 recordstore connections cannot be managed from a console, so you must perform this procedure from both the console and the sensor.
  1. Log in to the Administration settings on the console or sensor through https://<extrahop-hostname-or-IP-address>/admin.
  2. In the Recordstore Settings section, click Connect Recordstores.
  3. Click Add New.
  4. In the Node 1 field, type the hostname or IP address of any recordstore in the recordstore cluster.
  5. Click Save.
  6. In the Token from ExtraHop Recordstore field, type or paste the token that you generated on the EXA 5300.
  7. Click Connect.
  8. When the recordstore settings are saved, click Done.

Configure record ingest on a recordstore

Configure record ingest settings on an ExtraHop recordstore. Record ingest only must be enabled if you have previously disabled these settings.

  1. Log in to the Administration settings on the ExtraHop system through https://<extrahop-hostname-or-IP-address>/admin.
  2. Manage the record ingest setting:
    • For the EXA 5200, in the Recordstore Settings section, click Cluster Data Management.
    • For the EXA 5300, in the Recordstore Settings section, click Data Management.
  3. In the Record Ingest section, click Enable Record Ingest.
  4. Click Save.

Disconnect the recordstore

To halt the ingest of records to the recordstore, disconnect all recordstore nodes from the ExtraHop console and sensors.

  1. Log in to the Administration settings on the ExtraHop system through https://<extrahop-hostname-or-IP-address>/admin.
  2. In the ExtraHop Recordstore Settings section, click Connect Recordstores.
  3. Click the red X next to every node in the recordstore cluster.


  4. Click Save.
Last modified 2024-09-24