Veritas Volume Manager 4.1 Administrator's Guide (HP-UX 11i v3, February 2007)

Cluster Initialization and Configuration
364 VERITAS Volume Manager Administrator’s Guide
information about the shared configuration. (Neither the kernel view of the shared
configuration nor access to shared disks is affected.) Until the vxconfigd daemon on
the slave node has successfully reconnected to the vxconfigd daemon on the master
node, it has very little information about the shared configuration and any attempts to
display or modify the shared configuration can fail. For example, shared disk groups
listed using the vxdg list command are marked as disabled; when the rejoin
completes successfully, they are marked as enabled.
◆ If the vxconfigd daemon is stopped on both the master and slave nodes, the slave
nodes do not display accurate configuration information until vxconfigd is
restarted on the master and slave nodes, and the daemons have reconnected.
If the CVM agent for VCS determines that the vxconfigd daemon is not running on a
node during a cluster reconfiguration, vxconfigd is restarted automatically.
If it is necessary to restart vxconfigd manually in a VCS controlled cluster to resolve a
VxVM issue, use this procedure:
1. Use the following command to disable failover on any service groups that contain
VxVM objects:
# hagrp -freeze group
2. Enter the following command to stop and restart the VxVM configuration daemon on
the affected node:
# vxconfigd -k
3. Use the following command to re-enable failover for the service groups that you froze
in step 1:
# hagrp -unfreeze group
Note The -r reset option to vxconfigd restarts the vxconfigd daemon and recreates
all states from scratch. This option cannot be used to restart vxconfigd while a
node is joined to a cluster because it causes cluster information to be discarded.
Node Shutdown
Although it is possible to shut down the cluster on a node by invoking the shutdown
procedure of the node’s cluster monitor, this procedure is intended for terminating cluster
components after stopping any applications on the node that have access to shared
storage. VxVM supports clean node shutdown, which allows a node to leave the cluster
gracefully when all access to shared volumes has ceased. The host is still operational, but
cluster applications cannot be run on it.