H.2.3 Building a Cluster

This section describes procedures for setting up a cluster with PRIMECLUSTER in a VMware environment.

Refer to "5.1.1 Setting Up CF and CIP" to set up CF and CIP on the guest OS.

For details on survival priority, see "5.1.2.2 Survival priority."

In VMware environments, only the SA_icmp shutdown agent is available for setup.

This section explains the method for setting up the SA_icmp shutdown agent as the shutdown facility.

Note

Be sure to perform the following operations on all guest OSes (nodes).

Setting up the shutdown facility
Specify the shutdown agent.
Create /etc/opt/SMAW/SMAWsf/SA_icmp.cfg with the following contents on all guest OSes (nodes) of the cluster:
```
TIME_OUT=value
cfname:ip-address-of-node:NIC-name1,NIC-name2
```
value
Specify the interval (in seconds) for checking whether the node is alive. The recommended value is "5" (s).
cfname
Specify the name of the CF node.
ip-address-of-node
Specify one of the IP addresses below for cfname.
- Administrative LAN (Required)
- Public LAN
- Cluster interconnect (IP address of CIP)
Available IP addresses are IPv4 and IPv6 address. IPv6 link local addresses are not available. When specifying the IPv6 address, enclose it in blankets "[ ]".
(Example: [1080:2090:30a0:40b0:50c0:60d0:70e0:80f0])
Enter at least one for every node in the cluster system. Add a line each for specifying multiple LAN paths. To check LAN paths, we recommend that you use multiple ones.
NIC-nameX
Specify the network interface of the local guest OS (node) utilized for checking whether the node defined by ip-address-of-node is alive. If there is more than one, delimit them with commas (",").
Note
Registering network interfaces
- For duplicating by GLS, define all redundant network interfaces. (Example: eth0,eth1)
- If you are bonding NICs, define the bonding device behind the IP address. (Example: bond0)
- For registering the cluster interconnect, define all network interfaces that are used on all paths of the cluster interconnect. (Example: eth2,eth3)
- Do not use the takeover IP address (takeover virtual Interface).
Example
In a cluster between guest OSes on multiple ESX hosts, the following example shows settings for the public LAN (duplicated by GLS (eth0,eth1)) and the administrative LAN (eth2) in a two-node configuration.
```
TIME_OUT=5
node1:10.20.30.100:eth0,eth1
node1:10.20.40.200:eth2
node2:10.20.30.101:eth0,eth1
node2:10.20.40.201:eth2
```

Setting up the shutdown daemon

Create /etc/opt/SMAW/SMAWsf/rcsd.cfg with the following contents on all guest OSes (nodes) of the cluster:

CFNameX,weight=weight,admIP=myadmIP: agent=SA_icmp,timeout=timeout
CFNameX,weight=weight,admIP=myadmIP: agent=SA_icmp,timeout=timeout

CFNameX        : CF node name of the cluster host. 
weight         : Weight of the SF node. 
myadmIP        : Specify the IP address of the administrative LAN for CFNameX. 
                 Available IP addresses are IPv4 and IPv6 address.
                 IPv6 link local addresses are not available.
                 When specifying the IPv6 address, enclose it in blankets "[ ]".
                 (Example: [1080:2090:30a0:40b0:50c0:60d0:70e0:80f0])
timeout        : Specify the timeout duration (seconds) of the Shutdown Agent.
                 Set the value determined by below calculation.
                 A) From the LAN path information provided in SA_icmp.cfg, extract lines 
                    from each CF node. 
                 B) Determine the times required for checking LAN path for each CF node.
                    ((TIME_OUT value in SA_icmp.cfg) + 2 [s]) x (number of lines extracted 
                       in step A))
                 C) Perform steps A) and B) for all CF nodes described in SA_icmp.cfg, 
                    and set the largest value as the timeout value. 
                    However, if the value determined in step C) is smaller than 20 seconds, 
                    set the timeout value to "20."

Note

The rcsd.cfg file must be the same on all guest OSes (nodes). Otherwise, operation errors might occur.

Starting the shutdown facility
Check that the shutdown facility has started.
```
# sdtool -s
```
If the shutdown facility has already started, execute the following command to restart the shutdown facility.
```
# sdtool -r
```
If the shutdown facility is not started, execute the following command to start the shutdown facility.
```
# sdtool -b
```
Checking the status of the shutdown facility
Check that the status of the shutdown facility is either "InitWorked" or "TestWorked." If the displayed status is "TestFailed" or "InitFailed," check the shutdown daemon settings for any mistakes.
```
# sdtool -s
```

Refer to "5.1.3 Initial Setup of the Cluster Resource Management Facility" to set up the resource database managed by the cluster resource management facility (hereafter referred to as "CRM") on the guest OS.

Refer to "5.2 Setting Up Fault Resource Identification and Operator Intervention Request" to make the settings for identifying fault resources and for requesting operator intervention.

H.2.3 Building a Cluster

H.2.3.1 Initial Setup of CF and CIP

H.2.3.2 Setting Up the Shutdown Facility

H.2.3.3 Initial Setup of the Cluster Resource Management Facility

H.2.3.4 Setting Up Fault Resource Identification and Operator Intervention Request