VCS system states in the state of ADMIN_WAIT
If you name the cluster name cluster while running VCW, then system states of all VCS nodes are going to the state of ADMIN_WAIT. If you try to start VCS with the "hastart -onenode" command after run "hastop -all", then hastatus will display "STALE_ADMIN_WAIT".
Check the main.cf, you will see the cluster name is cluster.
include "types.cf"
cluster Cluster(
UserNames = { admin = gJHkHEfFGjISjGFqJJeRJoJSiRJj }
Administrators = { admin }
)
system symantecha1(
)
system symantecha2(
)
This is because "cluster" is a reserved keyword that you cannot use - see the VCS admin guide:
About VCS keywords and reserved wordsThe following list includes the current keywords reserved for the VCSconfiguration language. Note they are case-sensitive.action false keylist remotecluster staticafter firm local requires stopArgListValues global offline resource strbefore group online set systemboolean Group MonitorOnly Signaled Systemcluster hard Name soft tempCluster heartbeat NameRule start typecondition HostMonitor Path Start TypeConfidenceLevel int Probed state VCShmevent IState remote State VCShmgYou would think the VCW wizard would prevent you using keywords, so perhaps engineering should enhance this wizard.Mike
