HP Serviceguard manual Using Easy Deployment Commands to Configure the Cluster, For example

•Make sure all the subnets used by the prospective nodes are accessible to all the nodes.

Easy Deployment commands will fail if they detect an asymmetric network configuration, in which only a subset of nodes has access to a given subnet.

•Make sure that the LAN or LANs that will be used for the cluster heartbeat meet high-availability requirements.

See the requirements for HEARTBEAT_IP listed under “Cluster Configuration Parameters ” (page 109), and the networking “Rules and Restrictions” (page 28). In addition, HP recommends that you do not rely only on the site LAN, or any busy LAN, for the cluster heartbeat.

For a discussion of cluster networking topology, see “Redundant Ethernet Configuration ” (page 29).

NOTE: You cannot use the Easy Deployment commands to create a cross-subnet configuration, as described under “Cross-Subnet Configurations” (page 30).

•If you have not already done so, set up ssh public/private key pairs on each node.

This will allow the Easy Deployment commands to operate on all the prospective nodes before cluster is formed. If you need to set up the keys, you can use DSAU to simplify the task. For more information about setting up ssh keys, see the HP-UX Secure Shell Getting Started Guide at http://www.hp.com/go/hpux-core-docs.

•If you will be using a lock LUN (as opposed to an LVM lock disk or a quorum server) set up the LUN partition before running cmdeploycl; see “Setting Up a Lock LUN” (page 174).

•If you will be using a quorum server, it must be running and reachable from all the configured nodes through all the quorum server IP addresses before running cmdeploycl; see “Specifying a Quorum Server” (page 190).

•If you will be using individual disks (as opposed to RAID) for package data, and you will be mirroring them with MirrorDisk/UX as HP recommends, make sure the hardware is configured so as to allow PVG-strict mirroring.

For more information, see “Using Mirrored Individual Data Disks” (page 179) — and it is good idea to read the entire section on “Creating a Storage Infrastructure with LVM” (page 177) so that you understand what cmpreparestg is doing.

•Make sure you have read and understood the additional limitations spelled out under “About Easy Deployment” (page 105); and it is a good idea to read the Easy Deployment manpages (cmpreparecl (1m), cmdeploycl (1m), and cmpreparestg (1m)) as well.

Using Easy Deployment Commands to Configure the Cluster

The examples that follow configure a two-node cluster with an LVM lock disk and a logical volume (with PVG-strict mirroring) for use by packages. For more information, and other options, see the manpages for cmpreparecl (1m), cmdeploycl (1m), and cmpreparestg (1m). You can also use easy deployment commands to deploy a VxVM/CVM disk group. The following example illustrates its use with LVM storage.

NOTE: The actions taken by the commands you will be using are logged to /var/adm/ cmcluster/sgeasy/easy_deployment.log, providing a useful record of the changes to system files.

1.Obtain networking information for the nodes on which you want the cluster heartbeat: cmquerycl –N <network_template_file> –n<node1> –n<node2>

For example:

cmquerycl –N $SGCONF/mynetwork

162 Building an HA Cluster Configuration