Network
This article provides an overview of the network infrastructure in an Exasol deployment.
The nodes in an Exasol deployment are normally configured with a private network. You can additionally configure a public network on a separate interface to allow direct access to the deployment from outside of the private network.
Exasol 8 does not include any tools for network management. The physical networks must be configured and managed through the network management interfaces on the Linux hosts. You must then specify the private and public IP addresses that will be used by the nodes in the deployment configuration.
For more information about network requirements and configuration, see Installation.
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.
The public IP addresses for the nodes should be consecutive and evenly spaced static IPv4 addresses in the same subnet. DHCP can be used if each node always receives the same IP address.
