5.1.1 Setting Up CF and CIP

Set up Cluster Foundation (CF) and CIP by using the CF Wizard of Cluster Admin. The designsheets for the CF and CIP setup are "Setup (initial configuration)" of PRIMECLUSTER Designsheets.

For details on the setting, see "1.1.5 Example of creating a cluster" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

Setup item	Description	Described in designsheets
Cluster name	Define the name of the cluster systems. Use up to 31 printable ASCII characters (except space, line feed, and tab characters) for each name. Cluster names are always processed as uppercase characters.	"Cluster name"
Cluster nodes	Select the nodes that will construct a cluster system.	"Node name (uname-n)" for "Node 1", "Node 2", "Node 3" and "Node 4"
CF node names	Set the names of the nodes that construct the cluster. The beginning character of each CF node name must be a lower-case alphabet. The length of each node name must be not more than 11 characters which consist of lower-case alphabets, numbers, or symbols (- and _).	"CF node name" for "Node 1", "Node 2", "Node 3" and "Node 4"
Cluster interconnects	In each node of the cluster, determine the network interface to be used in CF inter-node communication. A representative network interface is the Ethernet device. Set the network interfaces to be used for CF inter-node communication so that they are activated when the system is started. However, it is not necessary to assign the IP address except when the network interface is used as the network for the mirroring among servers of GDS.	"Path 0 NIC name" and "Path 1 NIC name" for "Node 1", "Node 2", "Node 3" and "Node 4"
IP interconnects	Optional. This setup allows you to operate CF over IP.	"IP interconnect setup"
CIP subnets	Set the following items, and set the IP address used by CF: CIP subnet count Host suffix Subnet number Subnet mask	"Number of subnets", "Subnet IP", and "Net mask" for "CIP"
Usage confirmation of CF remote services	Check whether the following functions are to be enabled: Remote file copy (cfcp) Remote command execution (cfsh) With the default settings, these services are "Not selected." To use RMS, you need to select at least one function.	"CF remote service usage"
Cluster Integrity Monitor (CIM) configuration	Set the nodes to be monitored by CIM.	"Node in CF quorum set" for "Node 1", "Node 2", "Node 3" and "Node 4"

Note

Node names of the cluster nodes are automatically input to "CF node names." The CF node name must be within 11characters.
When constructing multiple clusters, and if any of NICs used in different clusters exist on the same network, specify a different name per each cluster, such as including the node name in the cluster name.
If you enable any one of the CF remote services, do not connect the following systems in the same cluster interconnect:
- Systems that have a security problem
- Systems in which cluster interconnects are not secured
Hereinafter, the CF remote services (CFCP and CFSH) must be enabled. To enable this function after configuring CF, add the following definition to the /etc/default/cluster.config file and execute cfset -r.
```
CFCP    "cfcp"
CFSH    "cfsh"
```
If the CF and CIP configuration fails, check the following:
- The cluster interconnect is incorrect.
- The network interface that is used for the cluster interconnect is not activated.
After the CF setup is completed, "SF Wizard Startup Check" pop-up window is displayed. Select [No]. SF Wizard is not available in this version. Set up the SF according to the instructions in "5.1.2 Setting up the Shutdown Facility."
To share a NIC with the administrative LAN and the cluster interconnect, see "1.1 CF, CIP, and CIM configuration" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
When the bonding device is used for the cluster interconnection, only mode=1(active-backup) can be used.
For the cluster interconnect, it is recommended to use the physically independent and dedicated network. If the network is shared with other communications, a heartbeat failure may be detected due to the temporary network overload. Before the actual operation, test the communication status under the actual network overload and make sure that a heartbeat failure is not detected. If the failure is detected, refer to "11.3.1 Changing Time to Detect CF Heartbeat Timeout" and tune the cluster timeout value.
When configuring the cluster system using the extended partitions in PRIMEQUEST 3000 series (except B model), up to 4 nodes can be supported per cluster system.

Note

In the case of the single-node cluster operation

Make sure to set up the cluster interconnect.
For the network interface specified to the cluster interconnect, select a dedicated network interface device listed in the above table.
After the CF setup is completed, "SF Wizard Startup Check" pop-up window is displayed. Select [No] since the setting of the shutdown facility is unnecessary.
Following messages of the shutdown facility and RMS are output, however, this is no problem, since the setting of the shutdown facility is not performed.
- Messages of the shutdown facility:
```
fopen of /etc/opt/SMAW/SMAWsf/rcsd.cfg failed, errno 2
Could not correctly read the rcsd.cfg file
```
- Messages of RMS:
```
(SCR,26): ERROR The sdtool notification script has failed with status 1 after dynamic modification.
```

See

For information on the corrective action to be applied when the setting of the cluster interconnect fails, see "Chapter 8 Diagnostics and troubleshooting" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."