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
In an Azure environment, the virtual machine may pause for up to 30 seconds without a notification for maintenance, and a heartbeat failure may occur. To prevent the heartbeat failure during the maintenance without a notification, 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 30 seconds or more.
This section describes how to set up the shutdown facility in an Azure environment.
The shutdown agent available in an Azure environment is as follows.
Azure CLI
The Azure CLI shutdown agent SA_vmazureReset provides the function of shutting down nodes (virtual machines) using the Azure CLI in an Azure environment.
The storage location of a log file is as follows.
/var/opt/SMAWsf/log/SA_vmazureReset.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_vmazureReset.cfg file and the rcsd.cfg file on 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_vmazureReset,timeout=timeout CFNameX,weight=weight,admIP=myadmIP:agent=SA_vmazureReset,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_vmazureReset: Azure shutdown agent. timeout : Specify the timeout duration (seconds) of the Azure shutdown agent. Specify 45 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_vmazureReset,timeout=45
node2,weight=1,admIP=192.168.250.2:agent=SA_vmazureReset,timeout=45Create /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_vmazureReset.cfg with the following contents on all nodes in the cluster system.
Information
The template of the SA_vmazureReset.cfg file can be found at the following location:
/etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg.template
Delimit each item with a single space.
CFNameX ResourceID AppID TenantID CertPath {cycle | leave-off} CFNameX ResourceID AppID TenantID CertPath {cycle | leave-off}
CFNameX : Specify the CF node name of the cluster host. ResourceID : Specify the resource ID of the Azure virtual machine on which the cluster host is running. AppID : Specify the application ID when registering the service principal (the value recorded in step 3 of "27.3 Presetting"). TenantID : Specify the tenant ID when registering the service principal (the value recorded in step 3 of "27.3 Presetting"). CertPath : Specify the path of the certificate (the value recorded in step 3 of "27.3 Presetting"). cycle : Restart the node after forcibly stopping the node. leave-off : The node is not restarted after it is forcibly stopped.
Example) This is a setting example when the node1 and the node2 are as follows, and the node is forcibly stopped and then restarted.
CFNameX | ResourceID | AppID | TenantID | CertPath |
|---|---|---|---|---|
node1 | /subscriptions/1e234d12-39b8-49db-881a-35aa03b402b9/resourceGroups/pcl/providers/Microsoft.Compute/virtualMachines/node1 | d5b7dac1-718f-448b-8e11-4a8cca6d9004 | 8ff7ddfd-fbcb-4700-ae52-6d071ac8d1b4 | /root/examplecert.pem |
node2 | /subscriptions/1e234d12-39b8-49db-881a-35aa03b402b9/resourceGroups/pcl/providers/Microsoft.Compute/virtualMachines/node2 |
# cat /etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg
node1 /subscriptions/1e234d12-39b8-49db-881a-35aa03b402b9/resourceGroups/pcl/providers/Microsoft.Compute/virtualMachines/node1 d5b7dac1-718f-448b-8e11-4a8cca6d9004 8ff7ddfd-fbcb-4700-ae52-6d071ac8d1b4 /root/examplecert.pem cycle node2 /subscriptions/1e234d12-39b8-49db-881a-35aa03b402b9/resourceGroups/pcl/providers/Microsoft.Compute/virtualMachines/node2 d5b7dac1-718f-448b-8e11-4a8cca6d9004 8ff7ddfd-fbcb-4700-ae52-6d071ac8d1b4 /root/examplecert.pem cycle
Create /etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg and then set the owner, group, and access rights as follows.
# chown root:root /etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg
# chmod 600 /etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg
Note
Make sure that the /etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg file is set correctly. If the setting is incorrect, the shutdown facility cannot be performed normally.
Make sure that the resource ID (ResourceID) of the virtual machine corresponding to the CF node name (CFNameX) of the cluster host in the /etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg file is set. Also, make sure that the application ID (AppID), the tenant ID (TenantID), and the certificate path (CertPath) that were generated when registering the service principal and creating the certificate are set correctly. 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 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 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.