Filter
Top Products
415Administering cluster functionality
Cluster initialization and configuration
stopped, volume reconfiguration cannot take place. Other nodes can join the
cluster if the
vxconfigd daemon is not running on the slave nodes.
If the vxconfigd daemon stops, different actions are taken depending on which
node this occurred:
■ If the vxconfigd daemon is stopped on the master node, the vxconfigd
daemons on the slave nodes periodically attempt to rejoin to the master
node. Such attempts do not succeed until the vxconfigd daemon is
restarted on the master. In this case, the
vxconfigd daemons on the slave
nodes have not lost 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.
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