Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-295

How to change public IP subnet

    XMLWordPrintable

    Details

    • Type: How To
    • Status: Published
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Solution:
      Hide

      Synopsis

      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.

      Please note that

      1. This task requires a maintenance window of at least 30 minutes
      2. The tasks performed in EXAoperation require a user with at least "Administrator" privileges
      3. The network requirements are described in SOL-132 (https://www.exasol.com/support/browse/SOL-132)
      4. This guide is only for the case that the subnet mask and the host adresses won't be changed

      Instructions

      1. 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
      2. EXAoperation master node
      • The changes must be applied to a real license server since it is the only node that boots from the local hard drive.
      • Check the following things:
        • In EXAoperation, please navigate to Configuration > Network
        • Open the tab "System"
        • Ensure that the license server (usually node n0010) is listed as "License Server Node"
      • Move EXAoperation if the license server is not the "License Server Node":
        • Open the Page Services > EXAoperation
        • Select "n0010" from dropdown list
        • Confirm with click on the button "Move to specified Node"
        • Return to the Configuration > Network page and examine if the license server is now the EXAoperation master
      3. Check database operation
      • Navigate to the EXAoperation page Services > EXASolution
      • Review the database list and check if the column "Background Restore" indicates "None" on all instances
      4. Shutdown all databases
      • Open the Services > EXASolution page
      • Select all (running) EXASolution instances
      • Click on the button "Shutdown"
      • Reload the page until all instances change their status from "Running" to "Created"
      • Again, you may follow the procedure in an appropriate logservice:

        System marked as stopped.
        Successfully send retry shutdown event to system partition 64.
        EXASolution DEMO is rejecting connections
        controller-st(0.0): Shutdown called.
        User 0 requests shutdown of system.

      5. 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:
      6. 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 which is on "To Install" state will lead into an unrecoverable data loss!

      7. Change IP and reboot license server
      • Log in as maintenance user via 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 license, subnetmask and gateway and confirm with "OK"
      • Log out user maintenance with "Exit"
      • Reboot license server according to your login (iDRAC, vSphere, local, etc.)

        Now you are able to reconfigure your own network (eg. local public switch, VLAN, etc.)

      • Wait for the license server to finish it's startup procedure and log into EXAoperation again.
      9. 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 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:
        client ID is '27.1.0.16'
        Client version is '5.0.11'
        Client mac adress is '00:11:22:33:44:55'
        Initialize boot process.
        Client mac address of eth0 matches the expected value (00:11:22:33:44:55)
        Client mac address of eth1 matches the expected value (00:12:34:56:78:9A)
        Mount hard drives.
        Hard drives mounted.
        Prepare boot process stage 3.
        Node does not support CPU power management (requested 'performance').
        Successfully unpacked package on client node: EXAClusterOS-5.0.11_CentOS-6.5_x86_64.tar.gz
        Successfully unpacked package on client node: EXARuntime-5.0.11_x86_64.tar.gz
        Successfully updated kernel packages.
        Successfully synchronized EXAoperation.
        Successfully updated EXAStorage metadata.
        Successfully unpacked package on client node: EXASolution-5.0.11_x86_64.tar.gz
        Successfully unpacked package on client node: EXASolution-5.0.11-COS-5.0.11_x86_64.tar.gz
        Successfully unpacked package on client node: Oracle-InstantClient-11.2_x86_64.tar.gz
        Successfully unpacked package on client node: JDBC_Drivers-2014-03-05.tar.gz
        Successfully unpacked package on client node: java-package-2014-04-29.tar.gz
        Successfully unpacked package on client node: Plugin.RAID.tw_cli-10.1.tar.gz
        Successfully initialized thresholds for node monitoring
        Start boot process stage 3.
        Boot process stage 3 finished.
        Boot process stages 1 to 3 took 147 seconds.
      10. 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
      11. Start the databases
      • Open the Services > EXASolution page and repeat the following steps for all instances:
      • Click on an EXASolution instance name to open the properties page
      • From the "Actions" dropdown menu please select "Startup" and confirm with click on the button "Submit".
      • Navigate back to the Services > EXASolution page and reload until the database indicates the status "Running"
      • You may follow the procedure in an appropriate logservice:
        EXASolution exa_demo 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.
      12. Start EXAoperation plugins

      If required, you may start services delivered through EXAoperaton plugins (XML-RPC) now.

      Show
      Synopsis 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. Please note that 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 SOL-132 ( https://www.exasol.com/support/browse/SOL-132 ) This guide is only for the case that the subnet mask and the host adresses won't be changed Instructions 1. 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 2. EXAoperation master node The changes must be applied to a real license server since it is the only node that boots from the local hard drive. Check the following things: In EXAoperation, please navigate to Configuration > Network Open the tab "System" Ensure that the license server (usually node n0010) is listed as "License Server Node" Move EXAoperation if the license server is not the "License Server Node": Open the Page Services > EXAoperation Select "n0010" from dropdown list Confirm with click on the button "Move to specified Node" Return to the Configuration > Network page and examine if the license server is now the EXAoperation master 3. Check database operation Navigate to the EXAoperation page Services > EXASolution Review the database list and check if the column "Background Restore" indicates "None" on all instances 4. Shutdown all databases Open the Services > EXASolution page Select all (running) EXASolution instances Click on the button "Shutdown" Reload the page until all instances change their status from "Running" to "Created" Again, you may follow the procedure in an appropriate logservice: System marked as stopped. Successfully send retry shutdown event to system partition 64. EXASolution DEMO is rejecting connections controller-st(0.0): Shutdown called. User 0 requests shutdown of system. 5. 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: 6. 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 which is on "To Install" state will lead into an unrecoverable data loss! 7. Change IP and reboot license server Log in as maintenance user via 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 license, subnetmask and gateway and confirm with "OK" Log out user maintenance with "Exit" Reboot license server according to your login (iDRAC, vSphere, local, etc.) Now you are able to reconfigure your own network (eg. local public switch, VLAN, etc.) Wait for the license server to finish it's startup procedure and log into EXAoperation again. 9. 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 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: client ID is '27.1.0.16' Client version is '5.0.11' Client mac adress is '00:11:22:33:44:55' Initialize boot process. Client mac address of eth0 matches the expected value (00:11:22:33:44:55) Client mac address of eth1 matches the expected value (00:12:34:56:78:9A) Mount hard drives. Hard drives mounted. Prepare boot process stage 3. Node does not support CPU power management (requested 'performance'). Successfully unpacked package on client node: EXAClusterOS-5.0.11_CentOS-6.5_x86_64.tar.gz Successfully unpacked package on client node: EXARuntime-5.0.11_x86_64.tar.gz Successfully updated kernel packages. Successfully synchronized EXAoperation. Successfully updated EXAStorage metadata. Successfully unpacked package on client node: EXASolution-5.0.11_x86_64.tar.gz Successfully unpacked package on client node: EXASolution-5.0.11-COS-5.0.11_x86_64.tar.gz Successfully unpacked package on client node: Oracle-InstantClient-11.2_x86_64.tar.gz Successfully unpacked package on client node: JDBC_Drivers-2014-03-05.tar.gz Successfully unpacked package on client node: java-package-2014-04-29.tar.gz Successfully unpacked package on client node: Plugin.RAID.tw_cli-10.1.tar.gz Successfully initialized thresholds for node monitoring Start boot process stage 3. Boot process stage 3 finished. Boot process stages 1 to 3 took 147 seconds. 10. 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 11. Start the databases Open the Services > EXASolution page and repeat the following steps for all instances: Click on an EXASolution instance name to open the properties page From the "Actions" dropdown menu please select "Startup" and confirm with click on the button "Submit". Navigate back to the Services > EXASolution page and reload until the database indicates the status "Running" You may follow the procedure in an appropriate logservice: EXASolution exa_demo 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. 12. Start EXAoperation plugins If required, you may start services delivered through EXAoperaton plugins (XML-RPC) now.
    • Category 1:
      Cluster Administration - Network

      Attachments

        Issue Links

        1. 1_edit_system_properties_2.png
          1_edit_system_properties_2.png
          72 kB
        2. 1_edit_system_properties.png
          1_edit_system_properties.png
          75 kB
        3. 11_start_database-1.png
          11_start_database-1.png
          53 kB
        4. 11_start_database-2.png
          11_start_database-2.png
          30 kB
        5. 12_start_database-1.png
          12_start_database-1.png
          53 kB
        6. 12_start_database-2.png
          12_start_database-2.png
          30 kB
        7. 2_check_exaoperation_master.png
          2_check_exaoperation_master.png
          72 kB
        8. 2_move_exaoperation_master.png
          2_move_exaoperation_master.png
          46 kB
        9. 3_check_database_operation.png
          3_check_database_operation.png
          58 kB
        10. 4_shutdown_all_databases-1.png
          4_shutdown_all_databases-1.png
          62 kB
        11. 4_shutdown_all_databases-2.png
          4_shutdown_all_databases-2.png
          54 kB
        12. 5_shutdown_exastorage-1.png
          5_shutdown_exastorage-1.png
          104 kB
        13. 5_shutdown_exastorage-2.png
          5_shutdown_exastorage-2.png
          58 kB
        14. 6_suspend_nodes-1.png
          6_suspend_nodes-1.png
          94 kB
        15. 6_suspend_nodes-2.png
          6_suspend_nodes-2.png
          129 kB
        16. 7_change_license_ip_2.png
          7_change_license_ip_2.png
          26 kB
        17. 7_change_license_ip_3.png
          7_change_license_ip_3.png
          28 kB
        18. 7_change_license_ip.png
          7_change_license_ip.png
          28 kB
        19. 9_reboot_database_nodes.png
          9_reboot_database_nodes.png
          125 kB

          Activity

            People

            • Assignee:
              CaptainEXA Captain EXASOL
              Reporter:
              CaptainEXA Captain EXASOL
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: