Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Building an HA Cluster Configuration
Managing the Running Cluster
Chapter 5 197
For Red Hat this would be changed from:
server_args = -f /user/local/cmom/log/cmomd.log -r
/user/local/cmom/run
to
server_args = -i -f /user/local/cmom/log/cmomd.log -r
/user/local/cmom/run
3. Restart xinetd: /etc/init.d/xinetd restart
Deleting the Cluster Configuration
You can delete a cluster configuration by issuing the cmdeleteconf
command. The command prompts for a verification before deleting the
files unless you use the -f option. You can only delete the configuration
when the cluster is down. The action removes the binary configuration
file from all the nodes in the cluster and resets all cluster-aware volume
groups to be no longer cluster-aware.
NOTE The cmdeleteconf command removes only the cluster binary file
$SGCONF/cmclconfig. It does not remove any other files from the
$SGCONF directory.
Although the cluster must be halted, all nodes in the cluster should be
powered up and accessible before you use the cmdeleteconf command. If
a node is powered down, power it up and boot. If a node is inaccessible,
you will see a list of inaccessible nodes together with the following
message:
Checking current status
cmdeleteconf: Unable to reach node lptest1.
WARNING: Once the unreachable node is up, cmdeleteconf
should be executed on the node to remove the configuration.
Delete cluster lpcluster anyway (y/[n])?
Reply Yes to remove the configuration. Later, if the inaccessible node
becomes available, you should run the cmdeleteconf command on that
node to remove the configuration file.