4.0.0 HP PolyServe Software for Windows File Serving administration guide (T5392-96047, March 2010)

For example, if the system encounters a problem, the script will fail and exit non-zero.
The service could then become active on another node, causing the Stop script to
run on the original node even though the Start script did not complete successfully.
Use custom scripts to modify start/stop activities
The Virtual File Share monitor performs certain starting or stopping activities. If you
need to take an action before or after the starting or stopping activity, you can create
a custom Start or Stop script for the action and specify it on the Scripts tab for the
monitor.
The default order for starting is:
• Run the monitor’s starting activities (if any)
• Run the custom Start script (if any)
If you want to reverse this order, preface the Start script with the prefix [pre] on
the Scripts tab (for example, [pre] Start_script_path).
The default order for stopping is:
• Run the custom Stop script (if any)
• Run the monitor’s stopping activities (if any)
If you want to reverse this order, preface the Stop script with the prefix [post] on
the Scripts tab (for example, [post] Stop_script_path).
Event severity
An event is created when a configuration error occurs or a Start/Stop script times
out or fails. An event can cause the ClusterPulse process to initiate failover of the
associated Virtual CIFS Server. 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; script failures and DOWN status reports from the
monitor will not cause failover. This is useful when the DOWN status or the action
performed by the scripts is not critical, but is important enough that you want to keep
a record of it.
HP PolyServe Software for Windows File Serving administration guide 31