Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 18 Current »

You will receive the following 2 OVA files from the GYTPOL team to set up your environment:

  1. PostgreSQL (Database) Server OVA:

    • This virtual appliance contains the pre-configured PostgreSQL database server required for storing and managing GYTPOL data.

  2. GYTPOL Services (Application) Server OVA:

    • This virtual appliance contains the core GYTPOL services and application required to manage and monitor your environment.

There’s no need to create the machines manually, as they will be automatically created during the OVA import.

Requirements for PostgreSQL (Database) Server OVA

To host the PostgreSQL database for self-hosted GYTPOL, ensure the virtual machine meets the following specifications.

Device Count

CPU (Cores)

Memory (GB)

SSD Storage (GB)

Up to 25,000 (+ PoV)

2

8

2 * 100

25,000 to 35,000

2

10

2 * 100

35,000 to 55,000

4

16

2 * 100

55,000 to 150,000

8

64

2 * 100

For deployments over 150K devices, please contact GYTPOL support at support@gytpol.com

Requirements for GYTPOL Services (Application) Server OVA

For hosting the core services of self-hosted GYTPOL, ensure the virtual machine meets the following specifications regardless of the device count:

CPU (Cores)

Memory (GB)

SSD Storage (GB)

6

12

100 + 50

Firewall Port Requirements

Below are the required firewall ports for self-hosted GYTPOL, including their purpose and connectivity:

Port

From

To

Purpose

12222

Management / UI (GYTPOL Admins)

Services Server, PostgreSQL Server

SSH and SCP for secure management

9093

Management / UI (GYTPOL Admins)

Services Server

UI access for administrators

9093

Devices

Services Server

Sensors tasks communication

8443

Devices

Services Server

Reporting from devices

32432

Services Server

PostgreSQL Server

Database connection

389

Services Server

Domain Controllers

LDAP integration for AD user authentication

636

Services Server

Domain Controllers

(Optional) LDAPS integration for AD user authentication

  • No labels