HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 16: Configure Service Monitors 204
If you want to reverse this order, preface the Stop script with the prefix
[post] on the Scripts tab.
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.
To configure event severity from the command line, use this option:
--eventSeverity consider|ignore
Script Ordering
Script ordering determines the order in which Start and Stop scripts are
run when a virtual host moves from one server to another. If you do not
configure a monitor with Start and Stop scripts, the script ordering
configuration has no effect. There are two settings:
SERIAL. This is the default setting. When a virtual host moves from one
server to another, the following strict ordering sequence for running Start
and Stop scripts is enforced:
1. The Stop script is run on all servers where the virtual host should be
inactive.
2. ClusterPulse waits for all Stop scripts to complete.