Setup guide

Chapter 2: mx Commands 63
Copyright © 1999-2005 PolyServe, Inc. All rights reserved.
[--parameters <parameters>]
For an HTTP monitor, the parameter is the URL for the service. For an
NFS monitor, the parameters are proto (either udp or tcp), rpcname
(typically nfs), and rpcvers (either 2 or 3). For an NIS monitor, the
parameters are proto (either udp or tcp), rpcname (typically ypserv),
rpcvers (either 1 or 2), and domain (the NIS domain to be monitored). For
a custom monitor, the parameter is a probe script.
[--ordering serial|parallel]
Whether HP Clustered File System enforces a strict ordering sequence
when it runs 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 the
service.
[--recoveryTimeout <seconds>]
The amount of time to wait for the script to complete.
[--startScript <script>]
When HP Clustered File System selects the active server for a monitored
service, the Start script runs on that server.
[--stopScript <script>]
A script that runs on all other servers configured for the service monitor
to ensure that the service is not active on those servers.
[--startTimeout <seconds>]
The amount of time to wait for the Start script to complete.
[--stopTimeout <seconds>]
The amount of time to wait for the Stop script to complete.
[--scriptSeverity consider|ignore]
Whether HP Clustered File System takes service 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.
[--priority <priority>]