3.5.1 Matrix Server Administration Guide

Chapter 14: Configure Device Monitors 247

If you want to reverse this order, preface the Stop script with the prefix

[post] on the Scripts tab.

Event Severity

By default, Matrix Server treats the failure or timeout of a Start or Stop

script as a failure of the associated monitored device and may initiate

failover of the associated virtual hosts. Configuration errors can also

cause this behavior.

Such a failure or timeout creates an event associated with the monitor on

the server where the failure or timeout occurred. You can view these

events in the Management Console and clear them using the Console or

mx device clear command after you have fixed the problems that caused

them.

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

Matrix Server 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:

--scriptSeverity consider|ignore

Script Ordering

Script ordering determines the order in which Matrix Server runs Start

and Stop scripts 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, Matrix Server enforces the following

strict ordering sequence for running Start and Stop scripts.