3.6.0 MxFS for CIFS Administration Guide (5697-7082, December 2007)

Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 32

This behavior is necessary because the Start and Stop scripts are run to

establish the desired start/stop activity, even though the service may

actually have been started by something other than MxFS for CIFS. The

Start and Stop scripts must also handle recovery from events that may

cause them to run unsuccessfully.

For example, if the system encounters a problem, the script will fail and

exit non-zero. The service could then become active on another node,

causing the Stop script to run on the original node even though the Start

script did not complete successfully.

Use Custom Scripts to Modify Start/Stop Activities

The Virtual File Share monitor performs certain starting or stopping

activities. If you need to take an action before or after the starting or

stopping activity, you can create a custom Start or Stop script for the

action and specify it on the Scripts tab for the monitor.

The default order for starting is:

• Run the monitor’s starting activities (if any)

• Run the custom Start script (if any)

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

[pre] on the Scripts tab (for example, [pre] Start_script_path).

The default order for stopping is:

• Run the custom Stop script (if any)

• Run the monitor’s stopping activities (if any)

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

[post] on the Scripts tab (for example, [post] Stop_script_path).

Event Severity

An event is created when a configuration error occurs or a Start/Stop

script times out or fails. An event can cause the ClusterPulse process to

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.