Managing Serviceguard Eighteenth Edition, September 2010

3. Create the cDSFs.
NOTE: cDSFs apply only to shared storage; they will not be generated for local
storage, such as root, boot, and swap devices.
• If the cluster does not exist yet, specify the name of each prospective node,
for example:
cmsetdsfgroup -n node1 -n node2 -n node3 -n node4
• If the cluster does exist, you can simply run:
cmsetdsfgroup -c
NOTE: You must be logged in as superuser on one of the cluster nodes. You
do not need to provide the cluster name.
The cDSFs created by cmsetdsfgroup reside in /dev/cdisk for block device files
and /dev/rcdisk for character devicefiles. You should use these new device files
exclusively when you configure the cluster lock (if any) and package storage; see
“Specifying a Lock Disk” (page 246), “Specifying a Lock LUN” (page 247), and “Creating
the Storage Infrastructure and Filesystems with LVM, VxVM and CVM” (page 230).
Adding a Node to a cDSF Group
When you add a new node to a cluster that uses cDSFs, you also need to add the node
to the cDSF group. For example, to add the new cluster node node5 to the existing
cDSF group, run the following command from one of the existing members of the
group:
cmsetdsfgroup –a –n node5
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
Preparing Your Systems 209