This chapter describes notes you should be well aware of when building a PRIMECLUSTER system. Be sure to read through this before you start operation.
Synchronize time on all nodes to configure a cluster system
Connect to the NTP server and synchronize time on all nodes.
If the time is not synchronized on all nodes, a cluster may not operate properly.
Do no set Spanning Tree Protocol to cluster interconnects
If you set Spanning Tree Protocol to cluster interconnects, the access between them is suspended. Thus, a heartbeat communication may fail.
Do not set a filtering function in routes of cluster interconnects
The cluster interconnects in PRIMECLUSTER bundle multiple lines to perform communication with PRIMECLUSTER's own protocol (ICF protocol). Therefore, they cannot communicate with devices other than cluster nodes connected to the cluster interconnects. Thus, do not set the filtering function in routes of the cluster interconnects.
Set up kernel parameters necessary in a cluster
PRIMECLUSTER is operated by using a system resource. If this resource is insufficient, PRIMECLUSTER may not operate properly.
The volume of resources used in a system is set as a kernel parameter.
It varies depending on an environment on which your system is running. Estimate the volume of applicable resources based on the operation environment.
Moreover, change kernel parameters before building PRIMECLUSTER.
In addition to that, when you change kernel parameters, be sure to restart your system.
See
For details on a parameter value, see "A.6 Kernel Parameter Worksheet."
Enable system to collect a system dump or a clash dump
If either a system dump or a clash dump cannot be collected, it may take time to investigate the cause when a problem occurs. Moreover, it may not be able to identify its root cause.
Check that you can collect a system dump and a clash dump before building PRIMECLUSTER.
Synchronize time in the slew mode
To synchronize time on each node with NTP, the step mode (synchronizing time fast) is set due to the default setting. However, instead of using it, select the slew mode (synchronizing time slow) for the operation. For details on the method of setting the mode, see manual of Oracle, Solaris, and so on.
If you set the step mode to synchronize time with NTP or with the date command running on the system, the times between nodes cannot be synchronized. Thus, the cluster system does not operate correctly.
For example, the following messages are output and a switchover is performed, or a switchover due to a heartbeat failure occurs.
(WRP, 34) Cluster host host is no longer in time sync with local node. Sane operation of RMS can no longer be guaranteed. Further out-of-sync messages will appear in the syslog.
(WRP, 35) Cluster host host is no longer in time sync with local node. Sane operation of RMS can no longer be guaranteed.
Configure the required Shutdown Facility depending on a server to be used
The required Shutdown Facility varies depending on a server to be used. See "5.1.2 Setting Up the Shutdown Facility" to check the required Shutdown Facility according to a server that is to be used. After that, configure it.
Set the time to detect CF heartbeat timeout as necessary
For the time to detect CF heartbeat timeout, you should consider operational volumes at a peak hour, and then set it based on your customer's environment. The value should be about 10 seconds to 1 minute. The default value is 10 seconds.
See
For the method of setting the time to detect CF heartbeat timeout, see "2.1.2 cfset" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
Make sure to set the environment variable: RELIANT_SHUT_MIN_WAIT specifying the RMS shutdown wait time
The required time to stop RMS and cluster applications varies depending on an environment. Be sure to estimate its value corresponding to the configuration setup, and then set it.
See
For details on RELIANT_SHUT_MIN_WAIT, see "13.2 Global environment variables" in "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide."
For the method of referring to and changing RMS environment variables, see "13.1 Setting environment variables" "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide."
Do not use DHCP when configuring CF
A node may be panicked if configuring CF while DHCP is set in the network interface.
Before configuring CF, unset DHCP in all network interfaces on nodes.
Example
<Contents of /etc/sysconfig/network-scripts/ifcfg-ethX>
DEVICE=ethX
BOOTPROTO=dhcp
HWADDR=xx:xx:xx:xx:xx:xx
ONBOOT=yes
TYPE=Ethernet
DHCP_HOSTNAME=Node1<Contents of /etc/sysconfig/network-scripts/ifcfg-ethX>
DEVICE=ethX
BOOTPROTO=static
HWADDR=xx:xx:xx:xx:xx:xx
ONBOOT=yes
IPADDR=xxx.xxx.xxx.xxx
NETMASK=xxx.xxx.xxx.x
TYPE=EthernetTo use iptables or ip6tables as Firewall in a cluster node, see "Appendix I Using Firewall."
If Firewall is not set correctly, PRIMECLUSTER may not operate properly.
Do not disable an IPv6 function of the operating system.
Even if you do not use an IPv6 address, set the IPv6 module of the operating system to be loaded.