This chapter describes how to install and set up software products related to PRIMECLUSTER for the following cases:
When not using the virtual machine function
When using the virtual machine function
Note
For the security, set "No Firewall" when a Red Hat Enterprise Linux is installed or when the setup command is executed. If Firewall has already been set for the security, change the setting to "No Firewall." If the "Firewall" setting is left as is, the clsetup (setting of the resource database) command will operate abnormally.
PRIMECLUSTER guarantees the performance of any required software when the umask value is set to 022. Do not modify the umask value.
For immediate cluster failover if an I/O device where the system volume is placed fails
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 by panicking a node in the event that an I/O device where the system volume is placed fails, set the ext3 or the ext4 file system to the system volume and perform the following setting.
Specify "errors=panic" to the mount option of each partition (the ext3 or the ext4 file system) included in the system volume.
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 the file system. The regularly writing to the system volume enhances the detection frequency of I/O error.
