Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

information about the shared configuration, so that any displayed configuration
information is correct.
■ If the vxconfigd daemon is stopped on a slave node, the master node takes no
action. When the vxconfigd daemon is restarted on the slave, the slave
vxconfigd daemon attempts to reconnect to the master daemon and to
re-acquire the 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.
Warning: 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.
In an HP Serviceguard cluster, use the equivalent Serviceguard functionality to
stop and restart the appropriate package.
It may sometimes be necessary to restart vxconfigd manually in a VCS controlled
cluster to resolve a VxVM issue.
469Administering cluster functionality
Cluster initialization and configuration