Environment Management
Manage the environment around the database, such as Cloud, Monitoring, Exaoperation and scalability
cancel
Showing results for 
Search instead for 
Did you mean: 
Background With versions prior to 5.0.15 EXASOL cluster deployments only supported CIDR block 27.1.0.0/16 and subnet 27.1.0.0/16, now it's possible to use custom CIDR blocks but with some restrictions, because the CIDR block will automatically be managed by our cluster operating system. VPC CIDR block netmask must be between /16 (255.255.0.0) and /24 (255.255.255.0)   The first ten IP addresses of the cluster's subnet are reserved and cannot be used Explanation Getting the right VPC / subnet configuration: The subnet used for installation of the EXASOL cluster is calculated according to the VPC CIDR range: 1. For VPCs with 16 to 23 Bit netmasks, the subnet will have a 24 Bit mask. For a 24 Bit VPC, the subnet will have 26 Bit range. VPC CIDR RANGE -> Subnet mask 192.168.20.0/16 -> .../24 192.168.20.0/17 -> .../24 ... -> .../24 192.168.20.0/22 -> .../24 192.168.20.0/23     FORBIDDEN 192.168.20.0/24 -> .../26 192.168.20.0/25     FORBIDDEN   2. For the EXASOL subnet, the VPS's second available subnet is automatically used. Helpful is the tool sipcalc (http://sipcalc.tools.uebi.net/), e.g. Example 1: The VPC is 192.168.20.0/22 (255.255.252.0) -> A .../24 subnet is used (255.255.255.0). `sipcalc 192.168.20.0/24' calculates a network range of 192.168.20.0 - 192.168.20.255 which is the VPC's first subnet. => EXASOL uses the subsequent subnet, which is 192.168.21.0/24 Example 2: The VPC is 192.168.20.0/24 (255.255.255.0) -> A .../26 subnet is used (255.255.255.192). `sipcalc 192.168.20.0/26' calculates a network range of 192.168.20.0 - 192.168.20.63 which is the VPC's first subnet. => EXASOL uses the subsequent subnet, which is 192.168.20.64/26 3. The first 10 IP addresses of the subnet are reserved. The license server, therefore, gets the subnet base + 10, the other nodes follow. This table shows some example configurations: VPC CIDR block Public Subnet Gateway License Server IP address IPMI network host addresses First additional VLAN address 10.0.0.0/16 10.0.1.0/24 10.0.1.1 10.0.1.10 10.0.128.0 10.0.65.0/16 192.168.0.0/24 192.168.1.0/24 192.168.1.1 192.168.1.10 192.168.1.128 192.168.64.0/24 192.168.128.0/24 192.168.129.0/24 192.168.128.1 192.168.129.10 192.168.129.128 192.168.32.0/24 192.168.20.0/22 192.168.21.0/24 192.168.21.1 192.168.21.10 192.168.21.128   192.168.16.0/24 192.168.16.64/26 192.168.16.65 192.168.16.74 192.168.16.96 192.168.128.0/26   Additional References https://docs.exasol.com/administration/aws.htm
View full article
Background That article guides you through the procedure to change the network for a cluster without tagged VLAN. It's strongly recommended to contact EXASOL support if you have tagged VLAN. Prerequisites This task requires a maintenance window of at least 30 minutes The tasks performed in EXAoperation require a user with at least "Administrator" privileges The network requirements are described in system_requirements This guide is only for the case that the subnet mask and the host addresses won't be changed Instructions 1. EXAoperation master node The changes must be applied to the real license server since it is the only node that boots from the local hard drive. Check the following:  Is EXAoperation running on the license server? If not, move it to the license server. 2. Shutdown all databases Navigate to the EXAoperation page Services > EXASolution Review the database list and check if the column "Background Restore" indicates "None" on all instances Select all (running) EXASolution instances Click on the button "Shutdown" Reload the page until all instances change their status from "Running" to "Created" You may follow the procedure in an appropriate logservice:  System marked as stopped. Volume 1 has been deleted. EXASolution exa_test is rejecting connections Controller(0.0): Shutdown called. User 0 requested shutdown of system 3. Shutdown EXAStorage Navigate to the EXAoperation page Services > EXAStorage  Click on the button "Shutdown Storage Service" and confirm your choice when prompted. When the storage service is down, it looks like: 4. Suspend Nodes Open the Configuration > Nodes page in EXAoperation  Select all nodes in the tab "Cluster Nodes" Select "Stop cluster services" from actions dropdown menu Confirm with click on the button "Execute"   Reload the page and until all nodes indicate the State/Op. "Suspended"   ⚠️ The 2nd state of every node must be "Active"! Restarting a node that has the "To Install" state will lead to an unrecoverable data loss! 5. Change network settings Navigate to Configuration -> Network Click on the button "Edit" Fill in the characteristics of the new network in Fields "Public Network", "Gateway", "NTP Server 1", "DNS Server 1". If there are no characteristics for NTP or DNS remove the entries, that the field is clear.   *Click on Button "Apply" to save the new configuration  6. Change IP and reboot license server Log in as maintenance user via the console. ⚠️ Connect via iDRAC, vSphere, or change it locally on the terminal. If you're connected via ssh and confirm the IP with "OK" you will get disconnected instantly. Make sure that you're able to reboot the server after the reconfiguration. confirm on "Configure Network" Change IP of the license, subnet mask, and gateway and confirm with "OK" Reboot the license server with the "Reboot" button . ⚠️  Now you are able to reconfigure your own network (eg. local public switch, VLAN, etc.) Wait for the license server to finish its startup procedure and log into EXAoperation again. 7. Reboot the database nodes Navigate to the Configuration > Nodes page Select all nodes in the tab "Cluster Nodes" Choose "Reboot" from actions dropdown menu and confirm with click on the button "Execute"   Wait for the nodes to finish reboot (about 15 to 25 minutes) Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes You may watch the boot process (of node n11 in this example) in an appropriately configured logservice: Boot process stages 1 to 3 took 121 seconds. Boot process stage 3 finished. Start boot process stage 3. successfully initialized thresholds for node monitoring successfully unpacked package on client node: JDBC_Drivers-2020-01-22.tar.gz successfully unpacked package on client node: EXASolution-7.0.beta1_x86_64.tar.gz successfully synchronized EXAoperation. successfully unpacked package on client node: EXARuntime-7.0.beta1_x86_64.tar.gz successfully unpacked package on client node: EXAClusterOS-7.0.beta1_CentOS-7.5.1804_x86_64.tar.gz Node does not support CPU power management (requested 'performance'). Prepare boot process stage 3. Hard drives mounted. Mount hard drives. client mac address of public0 matches the expected value (9E:F9:82:38:43:69) client mac address of private0 matches the expected value (2A:A9:8E:89:2F:10) Initialize boot process. client mac adress is '2A:A9:8E:89:2F:10' client version is '7.0.beta1' client ID is '10.17.1.11'Additional Notes 8. Startup EXAStorage Navigate to the EXAoperation page Services > EXAStorage Ensure that all database nodes indicates the state "Running" Click on the button "Startup Storage Service" and confirm your choice when prompted After the EXAStorage page has been reloaded, check the status of all nodes, disks, and volumes 9. Start the database Select all  EXASolution instances Click on the button "Start" Reload the page until all instances change their status from "Created" to "Running" You may follow the procedure in an appropriate logservice: EXASolution exa_test is accepting connections System is ready to receive client connections. System started successfully in partition 44. User 0 requests startup of system. User 0 requests new system setup.  
View full article
Background The tables below list the default ports of network services and DBMSs with which the EXASOL database may communicate. Notes 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). Explanation   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 sub connection ports (for EXA-to-EXA loading)     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 22 EXASOL database nodes SFTP server SFTP 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 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)   Additional References https://docs.exasol.com/administration/on-premise/installation/prepareenvironment/cluster_networking_infrastructure.htm?Highlight=network
View full article
Certified Hardware List
The hardware certified by Exasol can be found in the link below:

Certified Hardware List

If your preferred hardware is not certified, refer to our Certification Process for more information on this process.
Top Contributors