3.4.0 MxFS for CIFS Administration Guide

Chapter 3: Configure CIFS with Virtual CIFS Servers 32

When an event is created, the ClusterPulse process may initiate failover

of the associated Virtual CIFS Server. 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; script failures and DOWN status reports

from the monitor will not cause failover. This is useful when the

DOWN

status or the action performed by the scripts is not critical, but is

important enough that you want to keep a record of it.

Script Ordering

Script ordering determines the order in which the Start and Stop scripts

are run when a Virtual CIFS Server moves from one node to another. If

you do not configure the Virtual File Share monitor with Start and Stop

scripts, the script ordering configuration has no effect. There are two

settings:

SERIAL and PARALLEL.

SERIAL. This is the default setting. When a Virtual CIFS Server moves

from one node to another, the following strict ordering sequence for

running Start and Stop scripts is enforced:

1. The Stop script is run on all nodes where the virtual host should be

inactive.

2. ClusterPulse waits for all Stop scripts to complete.

3. The Start script is run on the node where the virtual host is becoming

active.

PARALLEL. The strict ordering sequence for Stop and Start scripts is not

enforced. The scripts run in parallel across the matrix as a Virtual CIFS

Server is in transition.

The

PARALLEL configuration can speed up failover time for services 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.