Managing Serviceguard Nineteenth Edition, Reprinted June 2011

The Easy Deployment tool consists of three commands: cmpreparecl (1m), cmdeploycl
(1m), and cmpreparestg (1m). These commands allow you to get a cluster up and running
in the minimum amount of time. The commands:
• Configure networking and security (cmpreparecl)
• Create and start the cluster with a cluster lock device (cmdeploycl)
• Create or modify Logical volume groups and VxVM/CVM disk groups and import volume
groups or disk groups as additional shared storage for use by cluster packages
(cmpreparestg)
Advantages of Easy Deployment
• Quick and simple way to create and start a cluster.
• Automates security and networking configuration that must always be done before you configure
nodes into a cluster.
• Simplifies cluster lock configuration.
• Simplifies creation of shared storage for packages.
Limitations of Easy Deployment
• Does not install or verify Serviceguard software
• Requires agile addressing for disks. See “About Device File Names (Device Special Files)”
(page 77).
• cmpreparestg (1m) will fail if cDSFs and persistent DSFs are mixed in a volume group.
See “About Cluster-wide Device Special Files (cDSFs)” (page 99) for more information about
cDSFs.
• Does not configure access control policies.
• Does not install or configure firewall and related software.
• Does not support cross-subnet configurations.
• Does not configure packages.
• Does not discover or configure a quorum server (but can deploy one that is already configured).
• Does not support asymmetric network configurations (in which only a subset of nodes has
access to a given subnet).
For more information and instructions, see “Using Easy Deployment” (page 152).
Heartbeat Subnet and Cluster Re-formation Time
The speed of cluster re-formation depends on the number of heartbeat subnets.
If the cluster has only a single heartbeat network, and a network card on that network fails,
heartbeats will be lost while the failure is being detected and the IP address is being switched to
a standby interface. The cluster may treat these lost heartbeats as a failure and re-form without
one or more nodes. To prevent this, a minimum MEMBER_TIMEOUT value of 14 seconds is required
for clusters with a single heartbeat network.
If there is more than one heartbeat subnet, and there is a failure on one of them, heartbeats will
go through another, so you can configure a smaller MEMBER_TIMEOUT value.
Cluster Configuration Planning 101