Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Building an HA Cluster Configuration
Managing the Running Cluster
Chapter 5 189
currently available for package switching. However, you should not try
to restart HP Serviceguard, since data corruption might occur if another
node were to attempt to start up a new instance of the application that is
still running on the single node. Instead of restarting the cluster, choose
an appropriate time to shutdown and reboot the node, which will allow
the applications to shut down and then permit HP Serviceguard to
restart the cluster after rebooting.
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.