5.1.1 Setting Up CF and CIP

Set up Cluster Foundation (CF) and CIP using the CF Wizard of Cluster Admin. Enter the information described in the table below. The worksheet for the CF and CIP setup is the "A.6 Cluster Configuration Worksheet". For details on the setting, see "2.1.4 Example of creating a cluster" in the "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide".

Setup item	Description	Described in worksheet
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" and "Node 2"
CF node names	Set the names of the nodes that construct the cluster. Use up to 11 printable ASCII characters (except space, line feed, and tab characters) for each node name. CF node names are always processed as lowercase characters. In the setup screen, the same names as the "Cluster nodes" above are displayed by default.	"CF node name" for "Node 1" and "Node 2"
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, IP addresses must not be assigned to the interfaces.	"Path 0 NIC name" and "Path 1 NIC name" for "Node 1" and "Node 2"
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.	"Usage status of CF remote services"
Cluster Integrity Monitor (CIM) configuration	Set the nodes to be monitored by CIM.	"Node in the CF quorum set" for "Node 1" and "Node 2"

Note

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
If you used the userApplication Configuration Wizard (GUI), the two remote services, "remote file copy" and "remote command execution," will be enabled automatically. If the cluster interconnects are not secured, comment out the following two lines in the "/etc/default/cluster.config" file for all cluster nodes after you build userApplication:
```
CFCP    "cfcp"
CFSH    "cfsh"
```
The results are as follows:
```
#CFCP    "cfcp"
#CFSH    "cfsh"
```
A CF or CIP setup error can be due to one of the following causes:
- A cluster interconnect is disconnected or incorrectly connected.
- A network interface for a cluster interconnect is not activated.
- An IP address is assigned to a network interface for a cluster interconnect.
The cluster node name will be automatically used for the CF node name. The name string must consist of eleven characters or less. Change it if necessary.
Do not add CIP nodenames manually to the /etc/hosts or /etc/inet/ipnodes file because the CF Wizard automatically updates the /etc/hosts and /etc/inet/ipnodes files on each node in the cluster.

See

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