3. Site Preparation

In order for the events to be properly logged and reported, the HAWK Support team requires a list of all the devices that are reporting events to HAWK eyeCon.

3.1. Detailed Device List

The following information must be supplied to HAWK:

  • Device Type

  • Device IP address

  • Number of each type of device

  • Operating System of the device

3.2. Host Preparation Requirements

All servers and desktop operating systems must be up-to-date on all Service Packs and releases. This includes all Windows, LINUX/UNIX, and MacOSX host devices.

3.3. Network Infrastructure Requirements

The network infrastructure must be capable of maintaining a minimum of 1GBPS for all associated ports. With network latency under 100ms.

3.4. Network Configuration

Since all clients have Firewalls in place, the Firewall rules must allow traffic to and from the following ports and services:

3.4.1. External Ports

  • Port 80 (TCP) - Redirects to Port 443

  • Port 443 (TCP) – Information Event Konsole (User Interface)

  • Port 514 (TCP/UDP) – Collectors and Engines

  • Port 8514 (TCP SSL) – Collectors and Engines

  • Port 8080 (TCP) – HAWK API

3.4.2. Internal Ports

  • Port 27001 (TCP) – Data Shard Service

  • Port 27017 (TCP) – Aggregation Service

  • Port 27019 (TCP) – Configuration Service

  • Port 3306 (TCP) – MySQL Service

  • Port 2888-3888 (TCP) – vStream (Distributed Coordination) Client Service

  • Port 2181 (TCP) – vStream (Distributed Coordination) Server Service

  • Port 9092 (TCP) – vStream (Distributed Commit Log) Service

  • Port 40010 (TCP) – HAWK Balancerd Service

  • Port 8082 (TCP) – HAWK Streamd service

  • Port 8081 (TCP) – PHP-FPM service

  • Port 8080 (TCP) – Reverse proxy for HAWK Streamd and PHP-FPM

Note

Additional firewall rules may be required during deployment due to flexibility of the data grid.