Network requirements

Anton Vasilev

Overview

The network requirements for ADB ES installation are listed below:

  • All cluster hosts should have IP addresses and the ability to communicate with each other at required speeds.

  • ping access to any cluster host (ICMP) should be provided.

  • If firewall software is not disabled, you should configure it to allow communication between the ADB cluster hosts and the ADB ES cluster hosts.

  • From the outside, the cluster hosts should be available on the 22 port for SSH connections.

  • To send cluster component statuses to Arenadata Cluster Manager (ADCM), ADB ES hosts should be allowed to connect to it (by default, via the 8000/tcp port).

  • If monitoring is used, the ports listed in Monitoring should be open on the host where the monitoring service is installed. The monitoring service installation is described in Install monitoring.

  • For offline installation of ADB ES, access to Arenadata Enterprise Tools repositories deployed on a dedicated host is required (by default, via the 81/tcp port). The ET cluster installation is described in Install Enterprise Tools cluster.

  • All ports that are listed below should be open on the respective hosts. If you use a firewall, add ports to the exception list.

Ports

ADB Control

NOTE

For more information on the ADB Control architecture, see Arenadata DB Control overview.
Component Port Protocol Note

ADB Control UI

6566

gRPC (HTTP 2.0)

 — 

8890

HTTP

Access to the ADB Control UI

ADB Control Server

6565

gRPC (HTTP 2.0)

 — 

8081

HTTP

 — 

ADB Control Scheduler

6570

gRPC (HTTP 2.0)

 — 

ADB Control Migration

8899

HTTP

 — 

For the requirements to the ADB Control agents, refer to ADB documentation.

ADBM

NOTE

For more information on the ADBM architecture, see Arenadata DB Backup Manager overview.
Port Protocol Note

6570

TCP

API port for agent-server interaction

8870

TCP

API port for binary backups

8970

TCP

API port for logical backups

For the requirements to the ADBM agents, refer to ADB documentation.

AD Eureka (Service Registry)

Port Protocol Note

6567

gRPC (HTTP 2.0)

gRPC endpoint of Service Registry instances

8761

HTTP

Eureka Server port. You can use <Eureka IP address>:8761 to access the Eureka UI

Database

Port Protocol Note

5433

TCP

Port of the internal PostgreSQL instance (used by both ADB Control and ADBM). If an external PostgreSQL instance is used, the port can be configured in the Database service configuration parameters

Clickhouse

Port Protocol Note

8123

HTTP

API port for HTTP requests. Used by JDBC, ODBC, and web interfaces

8443

HTTPS

API port for HTTPS requests. Used by JDBC, ODBC, and web interfaces

9000

TCP

Native protocol port (also referred to as ClickHouse TCP protocol). Used by ClickHouse applications and processes like clickhouse-server, clickhouse-client, and native ClickHouse tools. Used for distributed queries via inter-server communication

Arenadata Enterprise Tools

Port Protocol Note

81

TCP

Port that is used to access repositories during offline installation

Monitoring

Port Protocol Note

11210

HTTP

Port to access the Grafana web interface. You can change the default value in the Monitoring service configuration parameters in the Grafana settings section

11200

HTTP

Port to access the Prometheus web interface. You can change the default value in the Monitoring service configuration parameters in the Prometheus settings section

11203

HTTP

Port to access Node Exporter. You can change the default value in the Monitoring service configuration parameters in the Node Exporter settings section

9256

HTTP

Port to access Process Exporter. You can change the default value in the Monitoring service configuration parameters in the Process exporter settings section
Found a mistake? Seleсt text and press Ctrl+Enter to report it