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 13: Configure Event Notifiers and View Events 165
• Event details are placed into a set of environment variables for access
by the custom script or program.
• Event details, formatted in XML, are passed to the standard input
(stdin) of the script or program.
Script Requirements
For the script to work properly, the following requirements must be met:
• The script or program must be accessible from each node in the
cluster. It is recommended that an identical copy of the script or
program be placed on local storage on each node to ensure that it will
always be available.
• The script must be able to be executed on each node. For example, if
perl or Powershell is used, the appropriate interpreter must be
installed on each node and the appropriate extension must be
associated with the interpreter on each node.
• The script or program must either use full path names to any external
commands or set a PATH variable appropriate to each language. (A
system PATH variable is not passed to the script.)
Script Variables
Variables are accessed in a manner consistent with the language. For
example, the VA R variable is accessed in Batch as %VAR%; Powershell
uses $env:VAR; C uses getenv("VAR"); perl uses $ENV{VAR}; and so on.