HP StorageWorks Clustered File System 3.2.1 Windows Storage Server Edition Administration Guide (February 2006)

Chapter 11: Configure Service Monitors 115
without considering this to be an error. In both of these cases, the script
should exit with a zero exit status.
This behavior is necessary because HP Clustered File System runs the
Start and Stop scripts to establish the desired start/stop activity, even
though the service may actually have been started by something other
than HP Clustered File System before ClusterPulse was started. The Start
and Stop scripts must also handle recovery from events that may cause
them to run unsuccessfully.
For example, if the system runs out of swap space while running a Start
script, the script will fail and exit non-zero. The service could then
become active on another server, causing the Stop script to run on the
original server even though the Start script did not complete successfully.
To configure scripts from the command line, use these options:
--recoveryScript <script>
--startScript <script>
--stopScript <script>
Event Severity
If a Start or Stop script fails or times out, a monitor event is created on the
the node where the failure or timeout occurred. Configuration errors can
also cause this behavior. You can view these events on the HP CFS
Management Console and clear them from the Console or command line
after you have fixed the problems that caused them.
When an event is created, the ClusterPulse process may initiate failover
of the associated virtual host. You can configure the failover behavior
with the Event Severity attribute. There are two settings:
CONSIDER and
IGNORE.
CONSIDER. This is the default value. Events are considered when the
ClusterPulse process makes failover decisions.
IGNORE. Events are ignored and Start or Stop script failures will not
cause failover. This is useful when the action performed by the Start and
Stop scripts is not critical, but is important enough that you want to keep
a record of it.