Prepare Cluster Network Access
This section describes the cluster network access preparation required for the installation of an Exasol cluster.
Firewall (Client Side Communication Network CSCN)
Installation
Allow the following for installation of Exasol:
- SSH access to the license node (TCP port 20 + 22)
- LOM access to the license node (KVM, Exasol installation ISO mounted)
- LOM access to the data nodes (KVM)
- HTTP/S access to all cluster nodes (EXAoperation web UI ,TCP 80/443). The web UI is running as a cluster service and can be accessed from any cluster node
Operating
Allow the following for EXAoperation:
- Database port clients use to connect to the database (default TCP 8563)
- HTTP/S access to all cluster nodes (EXAoperation web UI, TCP 80/443)
- SSH access to all cluster members (TCP port 20 + 22)
- To get most out of the web UI each cluster node should be able to access the LOM of each other (ipmitool is used for providing basic hardware vitality information)
- NTP (TCP/UDP 123)
- DNS (TCP/UDP 53)
- Optional: LDAP (TCP/UDP 389)
Default Ports
The tables below list the default ports of network services and DBMSs with which Exasol database may communicate.
Many of the following protocols and DBMSs can be manually configured to use different ports.
The File Transfer Protocol (FTP) data connections require additional ports to be available (depending on the transfer mode).
Incoming Connections
Protocol | Port | Source | Destination | Description |
---|---|---|---|---|
TCP | 8563 | Exasol Client | Exasol database nodes | Exasol server port |
TCP | Range from 20000 to 21000 | Exasol database nodes (source) | Exasol database nodes (target) | Exasol subconnection ports (for EXA-to-EXA loading) |
TCP | 443 | Customer network / Exasol support VPN | EXAoperation | Web front-end |
TCP | 22 | Customer network / Exasol support VPN | Exasol Operating System | Shell access |
TCP | 2580 | Exasol Client | Exasol database nodes |
Default BucketFS service For each BucketFS service you create, a port (HTTP or HTTPs) must be assigned to access it. |
Outgoing Connections
Protocol | Port | Source | Destination | Description |
---|---|---|---|---|
TCP | 8563 | Exasol database nodes | Exasol database client | Exasol database client connection port |
TCP | Range from 20000 to 21000 | Exasol database nodes (source) | Exasol database nodes (target) | Exasol subconnection ports (for EXA-to-EXA loading) |
TCP | 20 | Exasol database nodes | FTP server | FTP data port for IMPORT/EXPORT |
TCP | 21 | Exasol database nodes | FTP server | FTP command port for IMPORT/EXPORT |
TCP | 80 | Exasol database nodes | HTTP server | HTTP port for IMPORT/EXPORT |
TCP | 443 | Exasol database nodes | HTTPS server | HTTPS port for IMPORT/EXPORT |
TCP | 990 | Exasol database nodes | FTPS server | FTPS port for IMPORT/EXPORT |
TCP | 389 | Exasol nodes | LDAP server | LDAP port |
TCP | 636 | Exasol nodes | LDAPS server | LDAPS port |
TCP | 1521 | Exasol database nodes | Oracle database | Oracle server port (JDBC/ORA connection) |
TCP | 1433 | Exasol database nodes | SQL Server database | SQL server port (JDBC connection) |
TCP | 3306 | Exasol database nodes | MySQL database | MySQL server port (JDBC connection) |
TCP | 50000 | Exasol database nodes | DB2 database | DB2 server port (JDBC connection) |
TCP | 5432 | Exasol database nodes | PostgreSQL database | PostgreSQL server port (JDBC connection) |
TCP | 5000 | Exasol database nodes | Sybase ASE database | Sybase ASE server port (JDBC connection) |