3.4.0 MxFS for CIFS Administration Guide

Chapter 3: Configure CIFS with Virtual CIFS Servers 31

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 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.

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.

Event Severity

If a Start or Stop script fails or times out, a monitor event is created on the

the node where the failure or timeout occurred. An event is also created

when a Virtual File Share monitor probe reports a status of DOWN.

Configuration errors can also cause this behavior. You can view these

events on the PolyServe Management Console and clear them from the

Console after you have fixed the problems that caused them.