27.9 Building the Cluster Application

For details on how to build the cluster application, refer to "Chapter 6 Building Cluster Applications" in "PRIMECLUSTER Installation and Administration Guide."

During this configuration, set the mirroring among servers of GDS (creating netmirror volume).

Also, network takeover must be registered to the cluster application. To build a cluster application for network takeover, refer to "27.9.1 Building the Cluster Application for Network Takeover."

Note

Among the tuning parameters to be set in "Disk Setting for Performing Mirroring among Servers" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide," set the following values for the following tuning parameters.
Tuning parameter name
Value after change
ED_CMD_RETRY_COUNT
100
ED_DRV_RETRY_COUNT
100
Example:
```
ED_CMD_RETRY_COUNT=100
ED_DRV_RETRY_COUNT=100
```
To extend the timeout period (CLUSTER_TIMEOUT) of the CF heartbeat, change the above parameter values according to the following formula. Round up the values after the decimal point.
Calculation formula:
```
<Increased CLUSTER_TIMEOUT> / 3 + 100
```
If the icmp communication between cluster nodes is not allowed in the security group configuration, the following message is displayed when the clchkcluster command is executed.
```
Admin IP <IP address> used by SF is not alive.
```
If this message is output, refer to "26.3.2.1 Security Rules Applied to the Administrative LAN", and set the icmp protocol rule to allow the icmp communication between cluster nodes. After that, execute the clchkcluster command again.

Tuning parameter name	Value after change
ED_CMD_RETRY_COUNT	100
ED_DRV_RETRY_COUNT	100

When executing the clchkcluster command, the following warning message is displayed. Ignore it.

Example) When LC_ALL is C

[warning]
The Shutdown Agent configuration is not redundant. 
[action]
Add another agent so that a failed node can be eliminated even if the first agent fails to eliminate the node. 

SA configuration: Passed

When using the Symfoware Server (Native) Hot Standby feature, the standby and scalable userApplication configurations are required.
Set the standby userApplication attribute to the following value.
Attribute
Setup value
StandbyTransitions
ClearFaultRequest | SwitchRequest
Refer to "6) Scalable operation" in "6.7 Setting Up Cluster Applications" in the "PRIMECLUSTER Installation and Administration Guide" for detailed build instructions.

Attribute	Setup value
StandbyTransitions	ClearFaultRequest \| SwitchRequest