Managing Serviceguard A.11.20, March 2013

Removing a Node from a cDSF Group
When you remove a node from a cluster that uses cDSFs, you should also remove the node from
the cDSF group. For example, to remove node3 from the existing cDSF group, run the following
command from one of the existing members of the group:
cmsetdsfgroup –r –n node3
Displaying the cDSF Configuration
• To see the members of a cDSF group, log in on one of the members and run cmsetdsfgroup
-q
• To display all the information about the configuration stored in the configuration file /etc/
cmcluster/cdsf/cdsf_config, log in on one of the cDSF group members and run
cmsetdsfgroup -v -q
CAUTION: Do not modify cdsf_config.
• To report information (in line output format only) about DSFs, cDSFs, and volume groups for
one or more nodes, use cmquerystg (1m).
• You can also use the HP-UX command io_cdsf_config (1m) to display information about
cDSFs.
See the manpages for more information.
Migrating Existing LVM Cluster Storage to cDSFs
You can migrate existing LVM cluster storage to cDSFs using the HP-UX command vgcdsf (1m).
See the manpage for more information. See also “LVM Commands and cDSFs” (page 110).
IMPORTANT: If you change the cluster lock volume or volumes to cDSFs, you need to change
the cluster lock information in the cluster configuration file and re-apply the configuration; follow
one of the procedures under “Updating the Cluster Lock Configuration” (page 300).
Using Easy Deployment
Easy Deployment commands enable you to get a cluster up and running in the minimum amount
of time. Instructions follow. For an overview, see “About Easy Deployment” (page 110).
Before You Start
IMPORTANT: Before you start, you should have done the planning and preparation outlined in
Chapter 4 (page 97). You must also do the following.
• Install Serviceguard on each node that is to be configured into the cluster; see “Installing and
Updating Serviceguard ” (page 163).
You must have superuser capability on each node.
• Make sure all the nodes have access to at least one fully configured network.
• 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 114), 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.
166 Building an HA Cluster Configuration