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. | "Cluster name" for "Cluster Foundation (CF)" |
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. | "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. | "Interconnect" - "Device name" for "Node 1" and "Node 2" |
IP interconnects | Optional. This setup allows you to operate CF over IP. | "IP interconnect" for "Cluster Foundation (CF)" |
CIP subnets | Set the following items, and set the IP address used by CF: CIP subnet count Host suffix Subnet number Subnet mask | "Subnets," "Subnet number," and "Subnet mask" for "Cluster Foundation (CF)", and "Interconnect" - "Subnet mask" for "Node 1" and "Node 2" |
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". Make sure to select them for the following cases: - To use RMS - To use the Migration function in Oracle VM Server for SPARC Environment | "Usage of CF remote services" for "Cluster Foundation (CF)" |
Cluster Integrity Monitor (CIM) configuration | Set the nodes to be monitored by CIM. | "Node in 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 the 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 node names manually to the /etc/inet/hosts file because the CF Wizard automatically updates the /etc/inet/hosts files on each node in the cluster.
Check that CIP node names are not set to the /etc/inet/hosts file for each node in a cluster before executing the CF wizard. When the CIP node names are set, delete the entry of CIP node names.
In Oracle Solaris VM for SPARC environment, the physical NIC of the cluster interconnects can be shared between the multiple cluster systems. In this case, separating network segments is unnecessary. In the same network segment, the physical NIC to be used as the cluster interconnects can be shared. However, note the following points for designing:
The IP address to be assigned for the cluster interconnects should not be duplicated between each cluster system.
The different cluster name needs to be created for each cluster system.
A tagged VLAN interface cannot be used for the cluster interconnect.
See
For information on the corrective action to be applied when the setting of the cluster interconnect fails, see "10 Diagnostics and troubleshooting" in the "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
