Prior to installing LifeKeeper, configure the OS for the three virtual machines that you have created.

Logging In to a Virtual Machine

Perform the following steps on both cluster nodes and clients.

  1. Select Azure Portal > Virtual machines > Overview > Connect and review the information required for the connection.
  1. Using terminal software (Tera Term etc.) on the local PC, SSH to the public IP of the virtual machine with the account created when creating the virtual machine.

  1. Log in to the virtual machine.

  1. Set it up for subsequent use by root. Change to root privileges.

  1. Set the root password.

  1. Allow root login.

  1. Launch another window with the terminal software and confirm that you can log in as root (do not close the terminal window that you have been using).
  1. After successfully logging in, perform all subsequent tasks as root.

Fixing NIC Addresses

The NIC address is fixed to prevent it from being updated when the Azure infrastructure is updated. Make the following settings on both cluster nodes.

  1. Display the NIC information of the virtual machine and take a note of each interface name and MAC address.

  1. By default, there is only a network configuration file for eth0, so create a network configuration file for eth1.

  1. Edit the eth0 and eth1 configuration files. For HWADDR, use the value you took a note in the previous step.

SELinux

Disable SELinux. Make the following settings on both cluster nodes.

  1. Open the following file.

  1. Change the following parameters from “enforcing” to “disabled” and save.

  1. Reboot the virtual machine for the settings to take effect.
  1. Confirm that SELinux is disabled.

Firewall

Since LifeKeeper uses a specific port, refer to Running LifeKeeper with a Firewall to change the OS firewall configuration.

Disable the firewall. Configure the following settings on both cluster nodes.

  • Execute the following commands.

Address Conversion

Configure the following settings at the same time.

  • To enable communication to the VIP, the destination address of the packet for port 1521 where the load is balanced by ILB is converted to [VIP protected with IP resources].
  • Convert the source address of the ICMP packet to [Private IP address of Azure] so that the monitoring process of IP resources can be performed successfully.

Make the following settings on both cluster nodes.

  1. Install the IP tables package.

  1. Enable IP tables.

  1. Make sure the IP tables are enabled.

  1. Configure the IP tables.

Execute the following command on the active node (lk4lnode1):

Execute the following command on the standby node (lk4lnode02):

  1. Confirm that the ip table settings have been added. The following is an example of the active node.

  1. Reboot the virtual machine for the settings to take effect.

GUI Connection Settings

By default, Azure virtual machines do not have a GUI environment installed. We need to set up an X11 environment on the cluster nodes and a GUI environment on the client to use the LifeKeeper GUI.

Make the following settings on both cluster nodes.

  1. Install the GUI package. Execute the following command.

  1. After installing the package, execute the following command.

  1. Next, set the permission for intra-subnet communication. Edit the following file and add an entry before [REJECT].

  1. Reboot the virtual machine for the settings to take effect.

  1. Configure the local PC. Install the X Server software (such as Xming) on your local PC and start it.
  1. Next, configure the X 1 1 forwarding in the local PC terminal software (such as TeraTerm).

The setting method varies depending on the terminal software you are using. The following is an example of the configuration in TeraTerm.

Name Resolution

Configure the following settings on both cluster nodes and clients.

  1. Register the information of the cluster node (active) and cluster node (standby) clients and three Witness servers in /etc/hosts.

  1. Verify that each of them can communicate with each other with host name.

Checking the Kernel Version

Check the kernel version of RHEL.

For each distribution that supports LifeKeeper, refer to the SIOS Protection Suite for Linux Support Matrix.

Now you are ready to install LifeKeeper.

フィードバック

フィードバックありがとうございました

このトピックへフィードバック

送信