Managing Serviceguard 13th Edition, February 2007

Cluster and Package Maintenance
Reconfiguring a Cluster
Chapter 7324
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 115).
Updating the 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
Change
NETWORK_FAILURE_DETECTION
parameter (see “Monitoring
LAN Interfaces and Detecting
Failure” on page 104)
Cluster can be running.
Change Access Control Policy
(Serviceguard A.11.16 or later)
Cluster and package can be running
or halted.
Failover Optimization to enable
or disable Faster Failover
product
Cluster must not be running.
Table 7-1 Types of Changes to Permanent Cluster Configuration
Change to the Cluster
Configuration Required Cluster State