Network

An Exasol cluster is normally configured with two networks using separate physical interfaces on the nodes: a private network for internal communication between the nodes in the cluster, and a public network that allows connections to the database from outside of the cluster.

The physical networks must be configured using network management tools on the Linux hosts. You can then specify the private and public IP addresses for the nodes in the Exasol deployment configuration. By design, you cannot manage the network infrastructure directly from Exasol.

Private network

The nodes in a cluster communicate over the private network. The private network is used to boot and configure nodes, to constantly exchange vitality and configuration information, and to synchronize the database payload.

The nodes must be assigned consecutive and evenly spaced static IPv4 addresses in the same subnet. DHCP can be used if each node always receives the same IP address.

Each private network must be fully separated from other networks. No traffic must pass in or out, and only the dedicated interfaces of the cluster nodes must be wired to this network. A cluster must never exchange traffic with private networks of other clusters.

The nodes must be directly connected to the layer 2 network (VLAN) and traffic must not be filtered.

Public network

You can additionally configure public IP addresses for the nodes in order to allows clients outside of the private network to connect directly to the database instances and the administration interfaces without being routed through the private network. A public network is optional and not required for installation.