HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)
Table Of Contents
- Contents
- HP Technical Support
- Quick Start Checklist
- Introduction to HP Clustered File System
- Cluster Administration
- Administrative Considerations and Restrictions
- Tested Configuration Limits
- Volume and Filesystem Limits
- User Authentication
- Start the Management Console
- Cluster Management Applications
- The HP CFS Management Console
- View Installed Software
- Start HP Clustered File System
- Stop HP Clustered File System
- Back Up and Restore the Cluster Configuration
- HP Clustered File System Network Port Numbers
- Configure Servers
- Configure Network Interfaces
- Configure the SAN
- Configure Dynamic Volumes
- Configure PSFS Filesystems
- Manage Disk Quotas
- Manage Hardware Snapshots
- Configure Security Features
- Configure Event Notifiers and View Events
- Overview
- Install and Configure the Microsoft SNMP Service
- Cluster Event Viewer
- Configure Event Notifier Services
- Select Events for a Notifier Service
- Configure the SNMP Notifier Service
- Configure the Email Notifier Service
- Configure the Script Notifier Service
- View Configurations from the Command Line
- Test Notifier Services
- Enable or Disable a Notifier Service
- Restore Notifier Event Settings to Default Values
- Import or Export the Notifier Event Settings
- Using Custom Notifier Scripts
- Cluster Operations on the Applications Tab
- Configure Virtual Hosts
- Configure Service Monitors
- Configure Device Monitors
- Advanced Monitor Topics
- SAN Maintenance
- Other Cluster Maintenance
- Management Console Icons
- Index
Chapter 16: Configure Service Monitors 202
Scripts
Service monitors can optionally be configured with scripts that are run at
various points during cluster operation. The script types are as follows:
Recovery script. Runs after a monitor probe failure is detected, in an
attempt to restore the service.
Start script. Runs as a service is becoming active on a server.
Stop script. Runs as a service is becoming inactive on a server.
When a monitor is instantiated for a service (because the ClusterPulse
process is starting or the configuration has changed), HP Clustered File
System chooses the best server to make the service active. The Start script
is run on this server. On all other servers configured for the monitor, the
Stop script is run to ensure that the service is not active.
Start scripts must be robust enough to run when the service is already
started, without considering this to be an error. Similarly, Stop scripts
must be robust enough to run when the service is already stopped,