Managing HP Serviceguard A.12.00.00 for Linux, June 2014

5.3.5 Disabling identd
Ignore this section unless you have a particular need to disable identd.
You can configure Serviceguard not to use identd.
CAUTION: This is not recommended. Consult the white paper Securing Serviceguard at http://
www.hp.com/go/linux-serviceguard-docs (Select HP Serviceguard -> White Papers) for more
information.
If you must disable identd, do the following on each node after installing Serviceguard but before
each node rejoins the cluster (For example, before issuing a cmrunnode or cmruncl).
For Red Hat and SUSE:
1. Change the value of the server_args parameter in the file /etc/xinetd.d/hacl-cfg
from -c to -c -i
2. Restart xinetd:
/etc/init.d/xinetd restart
5.3.6 Deleting the Cluster Configuration
You can delete a cluster configuration by means of the cmdeleteconf command. The command
prompts for a verification before deleting the files unless you use the -f option. You can delete
the configuration only 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 allow
it to boot. If a node is inaccessible, you will see a list of inaccessible nodes and 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, run
cmdeleteconf on that node to remove the configuration file.
178 Building an HA Cluster Configuration