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.
Is EXAoperation running on the license server? If not, move it to the license server.
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
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:
⚠️ 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!
*Click on Button "Apply" to save the new configuration
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.
⚠️ 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.
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
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.