4.1 Starting the Cluster and Cluster Nodes

The scadmin startcluster command is used to make a node the first member of the cluster. This node becomes node 0 of the cluster. The other Sun Cluster nodes are started by a single command, scadmin startnode. This command starts the programs required for multinode synchronization, and coordinates integration of the other nodes with the first node (if the Sun Cluster software is already running on the first node). You can remove nodes from the cluster by using the scadmin command with the stopnode option on the node that you are removing from the cluster.

Make the local node the first member node in the cluster. This node must be a configured node of the cluster in order to run the scadmin startcluster command successfully. This command must complete successfully before any other nodes can join the cluster. If the local node aborts for any reason while the subsequent nodes are joining the cluster, the result might be a corrupted CCD. If this scenario occurs, restore the CCD using the procedure "4.11.3 How to Restore the CCD".

To make the local node a configured node of the cluster, see "3.1 Adding and Removing Cluster Nodes".

4.1.1 How to Start the Cluster

It is important that no other nodes are running the cluster software at this time. If this node detects that another cluster node is active, the local node aborts.

1. Start the first node of the cluster by using the scadmin(1M) command.

   # scadmin startcluster localnode clustername

   The startcluster option does not run if localnode does not match the name of the node on which the command runs. See the scadmin(1M) man page for details.

   For example:

   phys-hahost1# scadmin startcluster phys-hahost1 haclust Node specified is phys-hahost1 Cluster specified is haclust =========================== WARNING============================ = Creating a new cluster = =============================================================== You are attempting to start up the cluster node 'phys-hahost1' as the only node in a new cluster. It is important that no other cluster nodes be active at this time. If this node hears from other cluster nodes, this node will abort. Other nodes may only join after this command has completed successfully. Data corruption may occur if more than one cluster is active. Do you want to continue [y,n,?] y

   If you receive a reconfig.4013 error message, then either there is already a node in a cluster, or another node is still in the process of going down. Run the get_node_status(1M) command on the node that might be up to determine that node's status.

2. Add all other nodes to the cluster.

   Run the following command on all other nodes. This command can be run on multiple nodes at the same time.

   # scadmin startnode

   If you receive the following reconfig.4015 error message, there might be no existing cluster. Restart the cluster by using the scadmin startcluster localnode command.

   SUNWcluster.clustd.reconf.4015 "Aborting--no existing or intact cluster to join."

   Alternately, there may be a partition or node failure. (For example, a third node is attempting to join a two-node cluster when one of the two nodes fails.) If this happens, wait until the failures have completed. Fix the problems, if any, and then attempt to rejoin the cluster.

   If any required software packages are missing, the command fails and the console displays a message similar to the following:

   Assuming a default cluster name of haclust Error: Required SC package `SUNWccm' not installed! Aborting cluster startup.

   For information on installing the Sun Cluster software packages, refer to the Sun Cluster 2.2 Software Installation Guide.