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 18: Advanced Monitor Topics 232
Built-In Monitor or User-Defined Monitor?
To decide whether to use a built-in monitor or a user-defined monitor,
first determine whether a built-in monitor is available for the service you
want to monitor and then consider the degree of content verification that
you need. If you are monitoring a custom application for which a built-in
monitor is not available but the application provides network services
through certain ports, you may consider it sufficient to use built-in TCP
monitors on each of those ports.
However, if you want to verify that the application is still accepting
connections to the port and is also producing reasonable output, you
should use a user-defined service monitor. You will need to write a probe
script that connects to the port and then uses an operating system utility
to test how the script responds to various commands.
NOTE: The custom monitor dialog prompts you for a service monitor
name and not a port because you may be writing a monitor for an
application that does not provide network services and therefore
needs no port.
Example of Using Monitors with Applications
In this example, we will use service monitors with a custom application
called myservice. This application provides some facilities to clients who
connect to port 2468 and speak a protocol. You have already set up a
virtual host called vh1 for the IP address to which external clients are
going to connect. How do you make a service monitor for this
application?
The simplest way is to use a generic built-in TCP monitor on port 2468.
This monitor verifies that it is possible to connect to port 2468, which
probably indicates most of the time that the application is functioning.
However, a problem might occur that causes the application to continue
accepting connections but not produce meaningful output. To detect this
situation, you will need a more complex and robust monitor involving a
custom script.