21.9.1 Initial Cluster Setup

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.

This section describes how to set up the shutdown facility in an AWS environment.

The shutdown agent available in an AWS environment is as follows.

AWS CLI (SA_vmawsAsyncReset)
The shutdown function of a node (instance) using the AWS Command Line Interface 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_vmawsAsyncReset.log
```

For details on the survival priority, refer to "5.1.2.1 Survival Priority" in "PRIMECLUSTER Installation and Administration Guide."

This section describes the setup procedure of the shutdown facility for the asynchronous forcible stop method.

Perform the following procedure.

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_vmawsAsyncReset.cfg file and the rcsd.cfg file of all nodes should be identical. If not, a malfunction will occur.

Set up the shutdown daemon.

Create SA_vmawsAsyncReset.cfg with the following contents on all nodes in the cluster system.

CFNameX,weight=weight,admIP=myadmIP:agent=SA_vmawsAsyncReset,timeout=timeout
CFNameX,weight=weight,admIP=myadmIP:agent=SA_vmawsAsyncReset,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_vmawsAsyncReset  : AWS CLI shutdown agent.
timeout             : Specify the timeout duration (seconds) of the AWS CLI shutdown agent.
                      Specify 15 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.250.1, and the IP address of the administrative LAN of node2 is 192.168.250.2.

# cat /etc/opt/SMAW/SMAWsf/rcsd.cfg
node1,weight=1,admIP=192.168.250.1:agent=SA_vmawsAsyncReset,timeout=15
node2,weight=1,admIP=192.168.250.2:agent=SA_vmawsAsyncReset,timeout=15

Create /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.

Set up the shutdown agent.
Create /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg with the following contents on all nodes in the cluster system.
Information
The template of the SA_vmawsAsyncReset.cfg file can be found at the following location:
```
  /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg.template
```
Delimit each item with a single space.
```
CFNameX InstanceID [ProfileName]
CFNameX InstanceID [ProfileName]
```
```
CFNameX           : Specify the CF node name of the cluster host.
InstanceID        : Specify the instance ID of AWS on which the cluster host is operating.
ProfileName       : Specify the profile name of the credentials used with the AWS Command Line
                    Interface configured in "21.3 Presetting."
                    When this item is omitted, the shutdown agent operates with the default
                    profile.
```
Example) The following is a setup example.
If the CF node names of the cluster host are node1 and node2, the instance IDs of AWS are i-abcdef0123456789a and i-abcdef0123456789b, and the profile name is userprofile1.
```
# cat /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg
node1 i-abcdef0123456789a userprofile1
node2 i-abcdef0123456789b userprofile1
```
Create /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg and then set the owner, group, and access rights as follows.
```
# chown root:root /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg
# chmod 600 /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg
```
Note
- Make sure that the /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg file is set correctly. If the setting is incorrect, the shutdown facility cannot be performed normally.
- Make sure that the instance ID of AWS (InstanceID) and the profile name (ProfileName) corresponding to the CF node name (CFNameX) of the cluster host of the /etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.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 -s
```
On 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 -b
```
Information
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 -s
```
Note
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 3 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, it means that SF has not yet stopped the node. If Unknown is displayed in Init State, it means that SF has not yet initialized SA or tested the route. 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 the servers of GDS and register it to the resource database.

21.9.1 Initial Cluster Setup

21.9.1.1 Initial Setup of CF and CIP

21.9.1.2 Setting up the Shutdown Facility

21.9.1.2.1 Setup Procedure of the Shutdown Facility for the Asynchronous Forcible Stop Method

21.9.1.3 Initial Setup of the Cluster Resource Management Facility