This section describes how to install and set up related software when building a cluster system between guest OSes on multiple host OSes using Host OS failover function.
Figure 3.1 Flow for building a cluster system when using Host OS failover function
Software installation (Host OS)
After installing the PRIMECLUSTER-related software, you need to set up the operating system, hardware, etc. that will be used and administered.
For details, see "3.2.3.1 Installation and Setup of Related Software (Host OS)".
Preparation prior to building a cluster (Host OS)
Before building a cluster, preparation work is required in the host OS, such as starting up the Web-Based Admin View screen. For details, see "Chapter 4 Preparation Prior to Building a Cluster".
Building a cluster (Host OS)
Build a cluster of PRIMECLUSTER on the host OS. For details, see "Chapter 5 Building a Cluster." To build a cluster, perform the procedures described in "5.1.1 Setting Up CF and CIP" and "5.1.2 Setting Up the Shutdown Facility". Also, for the shutdown facility, set shutdown agent in the same way as the setting between natives. See "5.1.2 Setting Up the Shutdown Facility", and check the hardware model/configuration to set up the appropriate shutdown agent.
Note
Set the timeout value of the cluster system on the host OS at the CF setting as follows:
Timeout value: 20 seconds (Change the timout value with the cfset command.)
Share the cluster interconnect LAN of the host OS with other guest OSes, and separate networks for each cluster system with Virtual LAN.
Do not build a cluster application on the host OS in a Xen environment.
Software installation (Guest OS)
After building a cluster on the host OS, install the PRIMECLUSTER-related software, and set up the OS and hardware for installing and operating PRIMECLUSTER.
For details, see "3.2.2 When building a cluster system between guest OSes on multiple host OSes without using Host OS failover function."
Note
In a Xen environment, after a guest OS shuts down due to PANIC (crash), the guest OS is automatically rebooted in the standard settings. In the virtual machine environment, however, after automatic collection of the guest OS memory dump, it is necessary to collect the host OS system information by fjsnap before the guest OS is rebooted. Therefore, modify the settings in the domain configuration file, and make sure not to reboot after a panic occurred.
In a KVM environment, the guest OS is not rebooted after a panic occurred by default. You do not need to make any settings.
Preparation prior to building a cluster (Guest OS)
Before building a cluster, preparation work is required in the host OS, such as starting up the Web-Based Admin View screen. For details, see "Chapter 4 Preparation Prior to Building a Cluster".
Building a cluster (Guest OS)
Build a cluster of PRIMECLUSTER on the guest OS. For details, see "3.2.3.2 Building a Cluster (Guest OS)".
Building cluster applications (Guest OS)
Create cluster applications on the guest OS. For details, see "Chapter 6 Building Cluster Applications".
Note
When creating a cluster application for a guest OS, do not set the ShutdownPriority attribute of RMS.
After installing the PRIMECLUSTER-related software, you need to set up the operating system, hardware, etc. that will be used and administered.
Perform the following as needed.
Host OS setup
In order for the host OS to work as the cluster, set up the network setting.
NTP setup
This setup is for synchronizing the time on each node comprising the cluster system, which is necessary when creating a cluster.
This setup should be performed before installing PRIMECLUSTER.
Installing and setting up related software
Install and set up the software product (ETERNUS Multipath Driver) required for using system disk of the guest OS on the host OS. For how to install and set up the related software, see "Software Information" for ETERNUS Multipath Driver.
Note
For immediate cluster failover if an I/O device where the system volume is placed fails
In the default setting of the ext3 file system, even if an I/O device where the system volume is placed fails, a cluster failover does not occur and the system operation may continue based on the data stored on the memory.
If you want PRIMECLUSTER to trigger a cluster failover immediately in the event that an I/O device where the system volume is placed fails, perform the following setting:
For each partition included in the system volume, specify "errors=panic" to the mount option of ext3.
Example: To set it in /etc/fstab (when /, /var, and /home exist in one system volume)
LABEL=/ / ext3 errors=panic 1 1 LABEL=/boot /boot ext3 errors=panic 1 2 LABEL=/var /var ext3 errors=panic 1 3 LABEL=/home /home ext3 errors=panic 1 4
However, an immediate cluster failover may not become available due to taking time for an I/O error to reach theext3 file system. The regularly writing to the system volume enhances the detection frequency of I/O error.
Setting the guest OS in the host OS (in a KVM environment)
In a KVM environment, perform the following settings to stop the guest OS normally if the host OS is shut down by mistake while the guest OS running.
Define the following two values in /etc/sysconfig/libvirt-guests. When values are already defined, change them to the following values:
ON_SHUTDOWN=shutdown
SHUTDOWN_TIMEOUT=300
Specify the timeout duration (seconds) for shutdown of the guest OS to SHUTDOWN_TIMEOUT. Estimate the length of time for shutting down the guest OS and set the value. When multiple guest OSes are set, set the time whichever is greater. The above is an example when the time is 300 seconds (5 minutes).
Note
When setting /etc/sysconfig/libvirt-guests, do not describe the setting values and comments on the same line.
When changing the settings in /etc/sysconfig/libvirt-guests during operation, make sure to follow the procedure in "8.9.2.3 Changing the Settings in /etc/sysconfig/libvirt-guests."
Installation of PRIMECLUSTER to the host OS
Install PRIMECLUSTER to the host OS. For details on the installation procedures, see the Installation Guide for PRIMECLUSTER.
Cluster High-Speed Failover Function setup
Make various settings for the Cluster High-Speed Failover Function related software and hardware.
Set up the setting after installing OS and PRIMECLUSTER.
For details, see "3.1.4 Setting Up the Cluster High-Speed Failover Function".
Kernel parameter check and setup
To operate the PRIMECLUSTER-related software, you need to edit the values of the kernel parameters based on the environment.
Perform this setup before rebooting the installed PRIMECLUSTER.
For details, see "3.1.5 Checking the Kernel Parameters".
Build a cluster on the guest OS. For details on each item, see " Chapter 5 Building a Cluster".
Note
Share the cluster interconnect LAN of the guest OS with other guest OSes and the host OS, and separate networks for each cluster system with Virtual LAN.
Do not change a timeout value of the guest OS from 10 seconds at the CF setting.
For setup policy for survival priority, see "Survival scenarios" in "5.1.2 Setting Up the Shutdown Facility."
