HP Serviceguard manual Configuring the Cluster, Clearimport at System Reboot Time

NOTE: Unlike LVM volume groups, VxVM disk groups are not entered in the cluster configuration file, nor in the package configuration file.

Clearimport at System Reboot Time

At system reboot time, the cmcluster RC script does a vxdisk clearimport on all disks formerly imported by the system, provided they have the noautoimport flag set, and provided they are not currently imported by another running node. The clearimport clears the host ID on the disk group, to allow any node that is connected to the disk group to import it when the package moves from one node to another.

Using the clearimport at reboot time allows Serviceguard to clean up following a node failure, for example, a system crash during a power failure. Disks that were imported at the time of the failure still have the node’s ID written on them, and this ID must be cleared before the rebooting node or any other node can import them with a package control script.

Note that the clearimport is done for disks previously imported with noautoimport set on any system that has Serviceguard installed, whether it is configured in a cluster or not.

Configuring the Cluster

This section describes how to define the basic cluster configuration using traditional Serviceguard commands. This must be done on a system that is not part of a Serviceguard cluster (that is, on which Serviceguard is installed but not configured).

NOTE: You can use Serviceguard Manager to configure a cluster: open the System Management Homepage (SMH) and choose Tools-> Serviceguard Manager. See “Using Serviceguard Manager” (page 24) for more information.

You can also use Easy Deployment commands; see“About Easy Deployment” (page 105) and “Using Easy Deployment Commands to Configure the Cluster” (page 162).

To use traditional Serviceguard commands to configure the cluster, follow directions in the remainder of this section.

Use the cmquerycl (1m) command to specify a set of nodes to be included in the cluster and to generate a template for the cluster configuration file.

IMPORTANT: See the entry for NODE_NAME under “Cluster Configuration Parameters ” (page 109) for important information about restrictions on the node name.

Here is an example of the command (enter it all one line):

cmquerycl -v -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10

This creates a template file, by default /etc/cmcluster/clust1.conf. In this output file, keywords are separated from definitions by white space. Comments are permitted, and must be preceded by a pound sign (#) in the far left column.

NOTE: HP strongly recommends that you modify the file so as to send the heartbeat over all possible networks. See also HEARTBEAT_IP under “Cluster Configuration Parameters ” (page 109), and “Specifying the Address Family for the Heartbeat ” (page 187).

The cmquerycl(1m) manpage further explains the calling parameters as well as those that appear in the template file. See also “Cluster Configuration Parameters ” (page 109). Modify your /etc/ cmcluster/clust1.conf file as needed.

186 Building an HA Cluster Configuration