Managing Serviceguard Sixteenth Edition, March 2009

It is not necessary to halt the single node in this scenario, since the application is still
running, and no other node is currently available for package switching.
However, you should not try to restart Serviceguard, since data corruption might occur
if the node were to attempt to start up a new instance of the application that is still
running on the 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 Serviceguard to restart the cluster after rebooting.
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. Disabling identd removes an important security
layer from Serviceguard. See the white paper Securing Serviceguard at
http://docs.hp.com -> High Availability -> Serviceguard -> White
Papers for more information.
If you must disable identd, you can do so by adding the -i option to the tcp
hacl-cfg and hacl-probe commands in /etc/inetd.conf.
For example:
1. Change the cmclconfd entry in /etc/inetd.conf to:
hacl-cfg stream tcp nowait root /usr/lbin/cmclconfd cmclconfd -c -i
2. Change the cmomd entry in /etc/inetd.conf to (all on one line):
hacl-probe stream tcp nowait root /opt/cmom/lbin/cmomd /opt/cmom/lbin/cmomd -i -f
/var/opt/cmom/cmomd.log -r /var/opt/cmom
3. Restart inetd:
/etc/init.d/inetd restart
Deleting the Cluster Configuration
As root user, you can delete a cluster configuration from all cluster nodes by using
Serviceguard Manager or the command line. The cmdeleteconf 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.
250 Building an HA Cluster Configuration