If the "vxconfigd -k" command is issued in a cluster environment, will the node go down and attempt to failover?
| Article:TECH17330 | | | Created: 2006-01-22 | | | Updated: 2006-01-22 | | | Article URL http://www.symantec.com/docs/TECH17330 |
Problem
If the "vxconfigd -k" command is issued in a cluster environment, will the node go down and attempt to failover?
Solution
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:
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:
#
hagrp -freeze <service_group> -sys <system>
2. Kill and restart the vxconfigd process to resolve the Volume Manager issue:
#
vxconfigd -k
3. After vxconfigd
returns, verify that Volume Manager commands work:
# vxdg list
NAME
STATE ID
rootdg
enabled 1000193718.1025.boing
...
4. Re-enable Cluster Server control of the service groups with Volume Manager objects that were frozen in step 1:
#
hagrp -unfreeze <service_group> -sys <system>
|
|
Legacy ID
242526
Article URL http://www.symantec.com/docs/TECH17330
Terms of use for this information are found in Legal Notices
Thank you.