Since VERITAS Cluster Server (tm) requires vxconfigd to monitor VERITAS Volume Manager (tm) resources, issuing the vxconfigd -k command to kill and restart the Volume Manager daemon can cause Cluster Server to attempt to failover to another node in the cluster.  

If it has been determined that this command is absolutely necessary to resolve a Volume Manager issue, the following steps should be performed on the node in question:

1.  Prevent Cluster Server from taking action if a Volume Manager resource does fault due to vxconfigd not being available. This should be done for all service groups that contain Volume Manager objects:
 

2. Kill and restart the vxconfigd process to resolve the Volume Manager issue:
 

 

3. After vxconfigd returns, verify that Volume Manager commands work:
 

# vxdg list

4. Re-enable Cluster Server control of the service groups with Volume Manager objects that were frozen in step 1: