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

Chapter 12: Configure Device Monitors 130
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 shared device or 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 for script ordering:
SERIAL and PARALLEL.
SERIAL. This is the default setting. When a shared device or 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 shared device or virtual
host should be inactive.
2. ClusterPulse waits for all Stop scripts to complete.
3. The Start script is run on the server where the virtual host or shared
device is becoming active.
PARALLEL. The strict ordering sequence for Stop and Start scripts is not
enforced. The scripts run in parallel across the cluster as a shared device
or virtual host is in transition.
The
PARALLEL configuration can speed up failover time for services and
devices that do not depend on strict ordering of Start and Stop scripts.
Assuming that it is safe to run the scripts in parallel (which depends on
your application), this setting can also increase the chances of a successful
failover because ClusterPulse does not have to wait for the failing node to
finish running its Stop script.
To configure script ordering from the command line, use this option:
--ordering serial|parallel