This section describes the initial cluster setup for PRIMECLUSTER.
Refer to "5.1.1 Setting Up CF and CIP" in "PRIMECLUSTER Installation and Administration Guide" to set up CF and CIP.
Note
With the private bridge function of NIFCLOUD, a loss of communication may occur for about 15 seconds after an instantaneous loss of communication during maintenance and equipment failure accompanied by a loss of communication, and a heartbeat failure may occur.
To prevent a heartbeat failure during maintenance and equipment failure accompanied by a loss of communication, after setting CF, refer to "11.3.1 Changing Time to Detect CF Heartbeat Timeout" in "PRIMECLUSTER Installation and Administration Guide", and tune the cluster timeout value to 20 seconds or more.
This section describes how to set up the shutdown facility in a NIFCLOUD environment.
The shutdown agent available in a NIFCLOUD environment is as follows.
NIFCLOUD API (SA_vmnifclAsyncReset)
The shutdown function of a node (server) using the NIFCLOUD API is provided.
This setting is not necessary in a single-node cluster.
The storage location of a log file is as follows.
/var/opt/SMAWsf/log/SA_vmnifclAsyncReset.log
For details on the survival priority, refer to "5.1.2.1 Survival Priority" in "PRIMECLUSTER Installation and Administration Guide."
Note
After setting up the shutdown agent, conduct a test for the forced stop of cluster nodes to make sure that the correct nodes can be forcibly stopped. For details of the test for the forced stop of cluster nodes, refer to "1.4 Test" in "PRIMECLUSTER Installation and Administration Guide."
The contents of the SA_vmnifclAsyncReset.cfg file and the rcsd.cfg file of all nodes should be identical. If not, a malfunction will occur.
This setting is not necessary in a single-node cluster.
Set up the shutdown daemon.
Create /etc/opt/SMAW/SMAWsf/rcsd.cfg with the following contents on all nodes in the cluster system.
CFNameX,weight=weight,admIP=myadmIP:agent=SA_vmnifclAsyncReset,timeout=timeout CFNameX,weight=weight,admIP=myadmIP:agent=SA_vmnifclAsyncReset,timeout=timeout
CFNameX : Specify the CF node name of the cluster host. weight : Specify the weight of the SF node. myadmIP : Specify the IP address of the administrative LAN used in the shutdown facility of the cluster host. Available IP addresses are IPv4. When specifying a host name, make sure it is described in /etc/hosts. SA_vmnifclAsyncReset: NIFCLOUD API shutdown agent. timeout : Specify the timeout duration (seconds) of the NIFCLOUD API shutdown agent. Specify 30 seconds.
Example) The following is a setup example.
If the CF node names of the cluster host are node1 and node2, the weight of two nodes is 1, the IP address of the administrative LAN of node1 is 192.168.1.1, and the IP address of the administrative LAN of node2 is 192.168.1.2.
# cat /etc/opt/SMAW/SMAWsf/rcsd.cfg
node1,weight=1,admIP=192.168.1.1:agent=SA_vmnifclAsyncReset,timeout=30
node2,weight=1,admIP=192.168.1.2:agent=SA_vmnifclAsyncReset,timeout=30Create /etc/opt/SMAW/SMAWsf/rcsd.cfg and then set the owner, group, and access rights as follows.
# chown root:root /etc/opt/SMAW/SMAWsf/rcsd.cfg # chmod 600 /etc/opt/SMAW/SMAWsf/rcsd.cfg
Information
When creating the /etc/opt/SMAW/SMAWsf/rcsd.cfg file, the /etc/opt/SMAW/SMAWsf/rcsd.cfg.template file can be used as a template.
Encrypt the SecretAccessKey.
Execute the sfcipher command to encrypt a SecretAccessKey used for authenticating the NIFCLOUD API. For details on how to use the sfcipher command, refer to the manual page of "sfcipher."
# sfcipher -cExample) The following is a setup example.
If the SecretAccessKey is "123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ12345".
# sfcipher -c
Enter Password: <- Enter 123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ12345
Re-Enter Password: <- Enter 123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ12345
PIJgi9wm4sYJlfWShOxWP6fpz0Xb6t9KmRc4sPDsRBIGfm6gT5m0xH2H2xf1r38GSet the shutdown agent.
Create /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg with the following contents on all nodes in the cluster system.
Information
The template of the SA_vmnifclAsyncReset.cfg file can be found at the following location:
/etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg.template
Delimit each item with a single space.
CFNameX ServerName Region Accesskey SecretAccesskey
CFNameX ServerName Region Accesskey SecretAccesskey
CFNameX : Specify the CF node name of the cluster host. ServerName : Specify the server name of NIFCLOUD on which the cluster host is operating. Region : Specify a region of the endpoint used in a NIFCLOUD environment. Specify the "jp-east-X" format for the East Japan region and the "jp-west-X" format for the West Japan region. Accesskey : Specify the AccessKey used for authenticating the NIFCLOUD API. SecretAccesskey : Specify the SecretAccessKey encrypted in step 2.
Example) The following is a setup example.
If the CF node names of the cluster host are node1 and node2, the server names are pclserver1 and pclserver2, and the region is east-1.
# cat /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg node1 pclserver1 jp-east-1 123456789ABCDEFGHIJK PIJgi9wm4sYJlfWShOxWP6fpz0Xb6t9KmRc4sPDsRBIGfm6gT5m0xH2H2xf1r38G node2 pclserver2 jp-east-1 123456789ABCDEFGHIJK PIJgi9wm4sYJlfWShOxWP6fpz0Xb6t9KmRc4sPDsRBIGfm6gT5m0xH2H2xf1r38G
Create /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg and then set the owner, group, and access rights as follows.
# chown root:root /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg # chmod 600 /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg
Note
Make sure that the /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg file is set correctly. If the setting is incorrect, the shutdown facility cannot be performed normally.
Make sure that the server name (ServerName) and the region of the endpoint (Region) of NIFCLOUD corresponding to the CF node name (CFNameX) of the cluster host of the /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg file are set. If the setting is incorrect, an incorrect node will be forcibly stopped.
Start the shutdown facility.
Check if the shutdown facility has been started on all nodes in the cluster system.
# sdtool -sOn a node where the shutdown facility has already been started, execute the following commands to restart the shutdown facility.
# sdtool -e # sdtool -b
On a node where the shutdown facility has not been started, execute the following command to start the shutdown facility.
# sdtool -bInformation
You can check if the shutdown facility has already been started with the sdtool -s command. If "The RCSD is not running" is displayed, the shutdown facility is not started.
Check the status of the shutdown facility.
Execute the following command on all nodes in the cluster system to check the status of the shutdown facility.
# sdtool -sNote
If "The RCSD is not running" is displayed, the setting of the shutdown daemon or the setting of the shutdown agent is not correct. Perform the procedure from step 1 to 4 again.
Information
Display results of the sdtool -s command
If Unknown or Init-ing is displayed in Init State, wait for about one minute, and then check the status again.
If Unknown is displayed in Shut State or Init State, it means that SF has not yet stopped the node, tested the route, or initialized the shutdown agent. Unknown is displayed temporarily in Test State or Init State until the actual state can be confirmed.
If TestFailed is displayed in Test State, it means that a problem occurred while the agent was testing whether or not the node displayed in the Cluster Host field could be stopped. Some sort of problem probably occurred in the software, hardware, or network resources being used by that agent.
Refer to "5.1.3 Initial Setup of the Cluster Resource Management Facility" in "PRIMECLUSTER Installation and Administration Guide" to set up the resource database managed by the cluster resource management facility. In this setting, set the iSCSI device used in the mirroring among servers of GDS and register it to the resource database.