Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7348
NOTE If you are using CVM or CFS, you cannot change HEARTBEAT_INTERVAL,
NODE_TIMEOUT, or AUTO_START_TIMEOUT while the cluster is running.
This is because they affect the aggregate failover time, which is only
reported to CVM on cluster startup.
Updating the Cluster Lock Configuration
Use the procedures that follow whenever you need to change the device
file names of the cluster lock physical volumes - for example, when you
are migrating cluster nodes to the agile addressing scheme available as
of HP-UX 11i v3 (see “About Device File Names (Device Special Files)” on
page 111).
Updating the Cluster Lock Disk Configuration Online
You can change the device file names (DSFs) of the cluster lock physical
volumes (that is, the values of the FIRST_CLUSTER_LOCK_PV and
SECOND_CLUSTER_LOCK_PV parameters in the cluster configuration file)
without bringing down the cluster, under the following conditions:
• You are not changing the physical disks themselves
• You are changing values that already exist in the cluster
configuration file, not adding or deleting them
• The node on which you are making the change is not running in the
cluster (that is, you have halted it by means of cmhaltnode, or by
selecting Halt Node in Serviceguard Manager)
• The cluster nodes are running Serviceguard 11.17.01 or later
Failover Optimization to
enable or disable Faster
Failover product
Cluster must not be running.
Table 7-1 Types of Changes to the Cluster Configuration (Continued)
Change to the Cluster
Configuration Required Cluster State