Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

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 HP Serviceguard 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.

To restart vxconfigd manually

Use the following command to disable failover on any service groups that

contain VxVM objects:

# hagrp -freeze groupname

Enter the following command to stop and restart the VxVM configuration

daemon on the affected node:

# vxconfigd -k

Use the following command to re-enable failover for the service groups that

you froze in step 1:

# hagrp -unfreeze groupname

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.

Administering cluster functionality (CVM)

CVM initialization and configuration

446