Operational state of the Service. The possible states are: standalone(1) The node is not configured to provide clustering services. active(2) The system is operational and the node is providing clustering services. passive(3) The system is operational and the node is active as a passive standby for the cluster. stopped(4) The service is stopped either intentionally (i.e.: the service is not supposed to run on this node) or unintentionally (a problem has occurred). This state might apply to both standalong and clustered nodes. stopping(5) The service is in the process of stopping. Stopping a service might be necessary after a configuration change. becomingActive (6) The node is becoming active, either as a result of a switchover or by initial start. becomingPassive (7) The node is failing over. Another node is taking charge of the services. fault(8) An error has been detected and the state is undefined.