
Chapter 3: mx Commands 115
Used when ClusterPulse fails over Virtual CIFS Servers. Service priorities are
natural numbers, with 0 (zero) representing the highest priority and higher
numbers representing lower priorities. If multiple failures prevent
ClusterPulse from placing a Virtual CIFS Server on a node where all of its
associated services are available, ClusterPulse next looks for a node where the
associated service with the highest priority is available. The default priority is
0.
[--ordering SERIAL|PARALLEL]
When a Virtual CIFS Server is moved from one node to another, this setting
determines whether a strict ordering sequence is used to run Start or Stop
scripts. The default is SERIAL, the strict ordering sequence.
[--recoveryScript <script>]
Runs after a monitor probe failure is detected, in an attempt to restore access
to the Virtual File Share.
[--recoveryTimeout <seconds>]
The amount of time to wait for the Recovery script to complete.
[--startScript <script>]
Runs as the Virtual File Share is becoming active on a server.
[--startTimeout <seconds>]
The amount of time to wait for the Start script to complete.
[--stopScript <script>]
Runs as the Virtual File Share is becoming inactive on a server.
[--stopTimeout <seconds>]
The amount of time to wait for the Stop script to complete.
[--eventSeverity consider|ignore]
Whether ClusterPulse takes monitor events (such as a failure or timeout of a
Start or Stop script) into consideration when it makes failover decisions. The
default is consider.
Comentarios a estos manuales